[ARIES-1642] Aries JPA container cannot be used without Configuration Admin

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: jpa-2.5.0
• Component/s: JPA
• Assignee: Unassigned
• Reporter: Timothy James Ward
• Created: 20/Dec/16 09:35
• Updated: 09/Jan/17 14:40

Description

The Aries JPA ManagedEMF registers a managed service factory for each "complete" EntityManagerFactory service. This isn't part of the JPA service specification, but does provide a nice way to fix up clients which don't use the EMFBuilder.

The problem is that if no Config Admin is available in the framework then no EMF service is ever registered!

The only call to createAndPublishEMF is from the updated method, and the updated method is only called if Config Admin is running!

https://github.com/apache/aries/blob/d85be2b8f8a026cb1959c83ceb4ed812cd9d1279/jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/impl/ManagedEMF.java#L128

Having a running Configuration Admin should not be a hard requirement for Aries JPA.