< bean id = "id" class = "com.foo.TestScope" scope = “request" />
Spring 2.0 : Scopes Scopes a single bean definition to the lifecycle of a HTTP Session . Only valid in the context of a web-aware Spring ApplicationContext . session Scopes a single bean definition to the lifecycle of a single HTTP request; i.e. each and every HTTP request will have its own instance of a bean created off the back of a single bean definition. Only valid in the context of a web-aware Spring ApplicationContext . request Scopes a single bean definition to any number of object instances. prototype Scopes a single bean definition to a single object instance per Spring IoC container . singleton Description Scope
Spring 2.0 : Scopes Scopes a single bean definition to the lifecycle of a global HTTP Session . Typically only valid when used in a portlet context . Only valid in the context of a web-aware Spring ApplicationContext . Global Session
Spring 2.0 : Scopes – request & session
Minor initial configuration is required before you can set about defining definitions request and session
If you are using a Servlet 2.4+ web container, add the following ContextListener to the XML declarations in your web application's 'web.xml' file.
Prior to Spring 2.0, Spring's JMS offering was limited to sending messages and the synchronous receiving of messages. Spring 2.0 now ships with full support for the reception of messages in an asynchronous fashion using MDP
JPA (Java Persistence API) Integration
Spring Portlet MVC
Spring 2.0 : Deprecated classes and methods
Previously were marked as @deprecated classed and methods have been removed from the Spring 2.0 codebase.
The following classes/interfaces have been removed from the Spring 2.0 codebase:
• ResultReader : Use the RowMapper interface instead.
• BeanFactoryBootstrap : Consider using a BeanFactoryLocator
Spring 2.0 : 1.2 to 2.0 migration steps
Download latest spring.jar from
( Spring Framework 2.0.2 is the current production release )
The packaging of the Spring Framework jars has changed quite substantially
between the 1.2.x and 2.0 releases. In particular, there are now dedicated jars for
the JDO, Hibernate 2/3, TopLink ORM integration classes: they are no longer