The Spring team are happy to announce the first release candidate of
New features and enhancements in Spring
container supports Method
Injection: the overriding of concrete or abstract methods, typically to
look up a dependency managed by the container. This means even less
need to implement Spring-specific interfaces such as BeanFactoryAware.
IoC container can now obtain
objects from static factory methods as well as constructors. This
enhancement allows excellent AspectJ integration: it is now possible to
configure AspectJ aspects using Spring Dependency Injection, like any
object. We plan to provide examples of AspectJ integration before 1.1
for sending and receiving
for Apache OJB as an ORM
alternative, within Spring's consistent data access abstraction
improved JDO support
flexibility in translating
SQLExceptions, and other JDBC enhancements
for nested transactions and
savepoints when working with JDBC. Declarative transaction management
can support nested transactions.
proxies are now serializable if
all Advisors and target are serializable
Velocity and FreeMarker
definition concept: a child can now override any inherited settings.
This can be used to simplify configuration.
Spring 1.1 final is scheduled for release in mid August, and will be
100% backward compatible with Spring 1.0.2. As Spring aims to minimize
dependency of application code on the framework, and because changes
are backward compatible, we do not expect that existing applications
will require any code changes to migrate to Spring 1.1.
The main focus between now and the 1.1 final release will be on
documentation and examples.
See the changelog
The release can be downloaded here