With all of the good stuff in Spring 3.0, it's hard to imagine what could possibly follow in Spring 3.1.
I just got this news from Spring2GX event side that they are introducing a number of often-requested configuration features. Need a standalone datasource in dev, but one from JNDI in production? Environment-Specific Bean Definitions are a first-class approach to solving this very common kind of problem. Love code-based configuration, but need the power and concision of Spring XML namespaces?
I'm guessing they will have support or integration for other languages like Scala, Groovy etc....well this event is one week away and will update more as i get more info about this...
Just to see what we have so far from spring, here are some points from Spring 3.0 enhancements
Full-scale REST support in Spring MVC, including Spring MVC controllers that respond to REST-style URLs with XML, JSON, RSS, or any other appropriate response. We'll look into Spring 3's new REST support in chapter 12.
A new expression language that brings Spring dependency injection to a new level by enabling injection of values from a variety of sources, including other beans and system properties. We'll dig into Spring's expression language in the next chapter.
New annotations for Spring MVC, including @CookieValue and @RequestHeader, to pull values from cookies and request headers, respectively. We'll see how to use these annotations as we look at Spring MVC in chapter 7.
A new XML namespace for easing configuration of Spring MVC.
Support for declarative validation with JSR-303 (Bean Validation) annotations.
Support for the new JSR-330 dependency injection specification.
Annotation-oriented declaration of asynchronous and scheduled methods.
A new annotation-based configuration model that allows for nearly XML-free Spring configuration. We'll see this new configuration style in the next chapter.
The Object-to-XML (OXM) mapping functionality from the Spring Web Services project has been moved into the core Spring Framework.