Jboss registers all spring application context instances which will allow management of the scope of individual beans, allowing for session or request based bean lifecycles. It also enables the sharing of beans between different WARs.
This can be managed by either a Jboss specific bean factory locator or via the JBOSS deployer.
Using the BeanFactoryLocator ends up being a list of bean factories contained within a static singleton lookup table.
The Jboss Deployer recognizes the spring.xml in your root WEB-INF directory, bootstrapping the application context & loading it into you JNDI registry.
This allows beans in other application contexts to access beans outside of their servlet space.
The application context is enabled in the servlet space by referencing either the VFSClassPathApplicationContext within the web.xml.
Shared JPA & JTA require a SharedEnitityManagerFactory wiring to be added in either the ApplicationContext or the JBOSS deployer.
Autowiring is still functional, but requires the JBOSS-Deployer if context/lifecycle management is required.
One of the biggest benefits touted was the ability for the application to utilize JBOSS's underlying ThreadPoolManager for Asyncronous calls via spring intialization.
Injection into SEAM managed projects is enabled.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment