To Amritendu De: I have around 6 years of experience in Java and related technologies(grails, groovy, Enterprise Beans et al). Recently, I started a Spring MVC project with Hibernate as a self study project. However, if you refer to the Spring website for documentation, there is a lot of reference to design pattern terminologies. Therefore, sometimes I have to refer to my J2EE design patterns book to understand the concepts in the said documents. Does your book address these concepts?
Also it seems like I am dealing with a many tentacled beast while coding in Spring. There are so many ways of doing the same thing. For instance, the configurations. There are annotations, programmatic configurations and maybe others . None of the tutorials mention the "why" of one methodology over another. Can your book enlighten us in this field?
Yes the book has a section on the design patterns followed by the architecture. I have solved the real life business requirement using an architecture of my choice. The same concept can be developed in a variety of other technologies. The book has an architecture chapter which enlightens the other technologies which can be used. This book will allow you to master the art of designing a relational database web application. The concepts that you take away can be applied to other architectures such as Java EE 7. Also the book is totally on the latest technical styles followed like annotations and component scanning.
Lets say you are currently working on a Java EE 7 project. The code for the service and data access written using Spring can be easily migrated to an EJB. Similarly Hibernate entities can be replaced with Toplink entities pretty easily because it follows the JPA 2 spec. Like that I wanted to emphasize that the concepts are important and the technology use is a matter of choice given the business requirements and other factors.