Apache Aries Blog Sample

Editor's Notes

• #6: Aries is one of 36 Apache Incubator projects
• #13: The Aries JPA container context bundle provides a blueprint namespace for dependency injection of managed JPA resources. Managed persistence units (EntityManagerFactory objects) can be injected with or without a JTA Transaction Services implementation. Managed persistence contexts (EntityManager objects) are only available with a JTA Transaction Services implementation. Both managed persistence units and managed persistence contexts behave as per the JPA specification.
• #14: NamespaceHandlers registered with a property whose value is the target nameapce: props.put("osgi.service.blueprint.namespace", "http://aries.apache.org/xmlns/transactions/v1.0.0"); A DI container standardizing established Spring conventions XML Blueprint definition describes component configuration and scope Optionally publish and consume components to/from OSGi service registry. Simplifies unit test outside either Java EE or OSGi r/t. The Aries BP container implementation is highly extensible: Namespace handlers supported to extend the Blueprint definitions Bean interceptors can be registered by handlers Other Aries components contribute handlers – “jpa” and “jta” handlers. Some other Aries components are implemented as Blueprint bundles themselves e.g. JPA container
• #15: jndi-url bundle registers a JNDI ObjectFactory for “osgi:services” Contexts in the service registry (“OsgiURLContextFactory“) jndi-core bundle registers an InitialContextFactoryBuilder and ObjectFactoryBuilder with JVM. The ICFB creates a Context which looks in the SR for an ObjectFactories which can process the URI scheme. If it delegates to the osgi:services ObjectFactory then this returns the service in the SR.
• #17: The Aries JPA container context bundle provides a blueprint namespace for dependency injection of managed JPA resources. Managed persistence units (EntityManagerFactory objects) can be injected with or without a JTA Transaction Services implementation. Managed persistence contexts (EntityManager objects) are only available with a JTA Transaction Services implementation. Both managed persistence units and managed persistence contexts behave as per the JPA specification.
• #18: The Aries JPA container context bundle provides a blueprint namespace for dependency injection of managed JPA resources. Managed persistence units (EntityManagerFactory objects) can be injected with or without a JTA Transaction Services implementation. Managed persistence contexts (EntityManager objects) are only available with a JTA Transaction Services implementation. Both managed persistence units and managed persistence contexts behave as per the JPA specification.
• #19: Application managed JPA Need Java code to look up the EMF service From that, create EM object Surround with try...finally, need to close. Container managed BP container – uses JPA context NS handler Injects EM object into Bean, all the Programmer does is call em.persist JTA – again BP container understands the Tx and ensures that changes to the DB are Managed as transactions
• #20: Application managed JPA Need Java code to look up the EMF service From that, create EM object Surround with try...finally, need to close. Container managed BP container – uses JPA context NS handler Injects EM object into Bean, all the Programmer does is call em.persist JTA – again BP container understands the Tx and ensures that changes to the DB are Managed as transactions
• #27: Provides support for “Application managed” JPA . Each persistence bundle has its standard JPA metadata located through the Meta-Persistence bundle header. JPA Container locates a JPA Provider which can service the PU and registers a Provider-created EntityManagerFactory service for each PU in each persistence bundle EMF service lifecyce follows the persistence bundle lifecycle JPA Provider gets persistence bundle classloader from PUInfo.
• #28: Provides support for “Application managed” JPA . Each persistence bundle has its standard JPA metadata located through the Meta-Persistence bundle header. JPA Container locates a JPA Provider which can service the PU and registers a Provider-created EntityManagerFactory service for each PU in each persistence bundle EMF service lifecyce follows the persistence bundle lifecycle JPA Provider gets persistence bundle classloader from PUInfo.
• #29: Provides support for “Application managed” JPA . Each persistence bundle has its standard JPA metadata located through the Meta-Persistence bundle header. JPA Container locates a JPA Provider which can service the PU and registers a Provider-created EntityManagerFactory service for each PU in each persistence bundle EMF service lifecyce follows the persistence bundle lifecycle JPA Provider gets persistence bundle classloader from PUInfo.