[
https://issues.apache.org/jira/browse/ARIES-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091721#comment-13091721
]
Christoph Läubrich commented on ARIES-735:
------------------------------------------
> The Aries JPA container is not actually an implementation of the OSGi JPA
> Service specification.
You might want to make this a little more clear on the project page, I was not
aware about this fact.
Beside this, I'm not sure how this would break anything, because it only allows
the creation of custom configured EntityManagerFactory instances, but you are
probably right that it won't help much. Thanks for you comment anyways :)
> Aries should support the org.osgi.service.jpa.EntityManagerFactoryBuilder
> service
> ---------------------------------------------------------------------------------
>
> Key: ARIES-735
> URL: https://issues.apache.org/jira/browse/ARIES-735
> Project: Aries
> Issue Type: Improvement
> Components: JPA
> Affects Versions: 0.3
> Reporter: Christoph Läubrich
>
> The OSGi Specification describes the service as follows:
> This service interface offers JPA clients the ability to create instances of
> EntityManagerFactory for a
> given named persistence unit.
> located in org.osgi.service.jpa / JPA Package Version 1.0.
> Bundles wishing to use this package must list the package in the
> Import-Package header of the bundle's
> manifest. For example:
> Import-Package: org.osgi.service.jpa; version="[1.0,2.0)"
> Aries seems not using this package, nor registering any service against this
> interface.
> Preffered solution:
> Either include this interface in the base jpa bundle or provide a seperate
> one and import it to register EntityManagerFactoryBuilder as described in the
> specification
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
