[
https://issues.apache.org/jira/browse/ARIES-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842490#comment-15842490
]
Timothy Ward commented on ARIES-1672:
-------------------------------------
> I don't think embedding the jpa spec packages makes sense.
I wasn't suggesting embedding the JPA API into the container bundle, just
stating that the specification requires a bundle which provides the JPA API
contract. My expectation is that Aries JPA will create a new bundle which does
just that, rather than changing the container. The Aries JPA container bundle
can choose to use the contract, or not, when importing the API if that is what
the community wants.
> The jpa container is open to be used with spec version 2.0 or 2.1
This is fine, but only 2.1 is required by the specification. It's therefore up
to you whether you choose to create one or two spec api bundles
> JPA API contract is required
> ----------------------------
>
> Key: ARIES-1672
> URL: https://issues.apache.org/jira/browse/ARIES-1672
> Project: Aries
> Issue Type: Bug
> Reporter: Timothy Ward
> Assignee: Christian Schneider
>
> The OSGi JPA service spec requires the presence of an OSGi contract for the
> JPA API. This will probably require Aries JPA to package up its own version
> of the JPA API. Note that this will only be necessary to function as the
> official RI, and we can still support using other public API bundles.
> Provide-Capability: osgi.contract;osgi.contract=JavaJPA;
> version:List<Version>="2.1,2,1";uses:="javax.persistence,javax.persistence.criteria,javax.persistence.metamodel,javax.persistence.spi"
> We could optionally choose not to support versions 2 or 1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
