Monday, December 11, 2006

Book:Agile Java Development

I've just finished reading the book Agile Java Development with Spring, Hibernate and Eclipse. I wasn't looking, but there it was in the book shop. I keep hearing good things about spring and hibernate. That together with Agile and Eclipse and it just about hits all of the areas that I'm curious about, so I bought the book.

The books takes you through a small project to create a timesheet application from requirements to finished product using the Agile methods. The author also described other necessary parts of the development process not just Agile, Spring and Hibernate. He covered UML, and setting up ANT and JUNIT. He also includes his personal opinions on things like "Why Agile Modelling and Extreme Programming?". I was very please to see that he thought setting up code directory structure, ant and junit upfront was vital to a projects success. All of which resonates with my own personal opinion that this builds the foundations for a smoother project.

The reasons for my interest in Spring and Hibernate, stems from my Domino and Notes roots. One of the important areas that keeps Notes and Domino in demand is that it has an easy to use database implementation and easy to program environment. Historically, in J2EE projects storing of data somewhere has been the area that required lots of effort. As a result there has been a proliferation of persistence frameworks, such as Hibernate, Ibatis, JDO and Toplink that have been designed and written to simply J2EE persistence. The other area is the general MVC framework for web application development. Spring is one of the leading (or most talked about) modular frameworks for web application development, which includes a flexible MVC web application framework, AOP, JDBC abstraction layer and integration with Hibernate, Ibatis, JDO and Toplink.

I've used Struts and Ibatis in other projects and they are not exactly easy to use and so I was keen to read about spring and hibernate. It seems that everyday J2EE is becoming easier and quicker. The net impact is these frameworks, which speed up development, have the potential to make J2EE applications another option for projects where Domino has been traditionally chosen.

No comments:

Post a Comment