You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Jeremy Bauer (Commented) (JIRA)" <ji...@apache.org> on 2011/09/29 17:12:45 UTC
[jira] [Commented] (OPENJPA-2053) OpenJPA service is not properly
registered for tracking by OSGi persistence tracker
[ https://issues.apache.org/jira/browse/OPENJPA-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117357#comment-13117357 ]
Jeremy Bauer commented on OPENJPA-2053:
---------------------------------------
Committed fix to trunk under revision 1177327.
> OpenJPA service is not properly registered for tracking by OSGi persistence tracker
> -----------------------------------------------------------------------------------
>
> Key: OPENJPA-2053
> URL: https://issues.apache.org/jira/browse/OPENJPA-2053
> Project: OpenJPA
> Issue Type: Bug
> Components: osgi
> Affects Versions: 2.0.0
> Environment: OpenJPA + OSGi
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Priority: Minor
> Labels: openjpa, osgi,
>
> The Geronimo JPA spec api bundle provides a mechanism that allows JPA providers that register as an OSGi service to be tracked. The provider services can then be enumerated through an OSGi-enabled persistence resolver (also in the spec bundle). This works fine (sort of) if only OpenJPA is the only provider registered, but breaks as soon another provider bundle registers in the environment.
> The issue is that the OpenJPA service registration mechanism does not specify a property required by the persistence tracker to distinguish one provider from another.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira