aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giuseppe Gerla (JIRA)" <>
Subject [jira] [Commented] (ARIES-1642) Aries JPA container cannot be used without Configuration Admin
Date Fri, 06 Jan 2017 15:49:58 GMT


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:
>             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!
> Having a running Configuration Admin should not be a hard requirement for Aries JPA.

This message was sent by Atlassian JIRA

View raw message