|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
@Gunnar exactly. JPA is a spec too
And the JPA spec lays down the rules for bootstrapping a "container managed" persistence provided as well as for bootstrapping an "application managed" persistence provider.
So either Enterprise OSGi is honoring the JPA spec in terms of the only JPA defined bootstrapping approaches, or it isn't. If it is expecting the JPA persistence provider to read some additional manifests and configure itself based on those, then Enterprise OSGi is in fact not honoring the JPA spec defined boostrapping.