[OPENJPA-2542] Using custom openjpa.BrokerFactory not working in OSGi due to ClassLoader

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0, 2.4.0
• Fix Version/s: 2.4.0
• Component/s: osgi
• Environment: JBoss Fuse 6.1, Apache Aries JPA 1.0.1.redhat-610379
• Assignee: Richard G. Curtis
• Reporter: Jörn Gersdorf
• Created: 11/Nov/14 14:51
• Updated: 06/Jun/15 14:25
• Resolved: 10/Dec/14 14:12

Description

For reasons discussed on the openjpa-user MailingList I need to use a custom BrokerFactory in an OSGi environment.

My custom BrokerFactory is obviously in my own OSGi bundle, not in the official OpenJPA bundle. Now, due to OPENJPA-1491 org.apache.openjpa.kernel.Bootstrap (in connection with {{org.apache.openjpa.persistence.PersistenceProviderImpl.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) and org.apache.openjpa.persistence.osgi.PersistenceActivator.getBundleClassLoader()), my BrokerFactories can only live in the official OpenJPA bundle, so that my custom BrokerFactory is not found.

In my opinion it would be better if org.apache.openjpa.persistence.osgi.PersistenceActivator.getBundleClassLoader() would return a ClassLoader not only delegating to openjpa´s bundle but in addition (as a fallback) to the PersistenceUnitInfo´s bundle.

That way one would be able to use arbitrary BrokerFactories by importing them if required to the bundle where persistence.xml is defined.

Issue Links

• is related to: OPENJPA-2543 Add possibility to disable QueryCache by default (new config property)
• relates to: OPENJPA-1491 org.apache.openjpa.kernel.Bootstrap uses the application classloader to load OpenJPA internals
• relates to: OPENJPA-2057 Rethinking ClassLoading architecture