Spring is a powerful Java application framework, used in a wide range of Java applications. It provides enterprise services to Plain Old Java Objects (POJOs). Spring uses dependency injection to achieve simplification and increase testability. Spring beans, dependencies, and the services needed by beans are specified in configuration files, which are typically in an XML format. The XML configuration files, however, are verbose and unwieldy. They can become hard to read and manage when you are working on a large project where many Spring beans are defined. Spring’s another advantage that it gives more and more support to the other frameworks.Nowadays so many Projects are building on this powerful framework. Although Spring is basically using many Best Practices as well as Design patterns, I think the best way of use of this framework is also necessary for getting all its features and also to get a good performance.
Through this post series I am tried to collect some points which will be good to follow in Spring handling applications. Most of them are used by expert Spring Programmers and came through their experience. The ways I got these points are, through Searching Internet, Referring Spring Official Documentation, Going through Spring Forums, Referring books like Pro Spring from Apress, Spring In Action from Manning and some of them from my own experience. This Series have five posts excluding this. Please note the Spring MVC related points are not included now and will be updated later. Hope this will help you to find Spring Best Practices in one area.