[
https://issues.apache.org/jira/browse/ARIES-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804837#comment-15804837
]
Giuseppe Gerla commented on ARIES-1642:
---------------------------------------
theoretically I would agree with this issue.
My remark is that at startup Config Admin could not be registered and we can
not know if Config Admin will be registered or not.
So the only solution is to call createAndPublishEMF on start with default
properties and then destroy EMF and call another time createAndPublishEMF with
custom properties.
I'm not sure if this behaviour is right one.
> Aries JPA container cannot be used without Configuration Admin
> --------------------------------------------------------------
>
> Key: ARIES-1642
> URL: https://issues.apache.org/jira/browse/ARIES-1642
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: jpa-2.5.0
> Reporter: Timothy Ward
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
