[
https://issues.apache.org/jira/browse/OPENJPA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784861#action_12784861
]
Kevin Sutter commented on OPENJPA-1403:
---------------------------------------
I just talked with my OSGi contacts and it's my understanding that RFC 143 is
very close to publishing. This RFC should outline the specific requirements
for a JPA provider in a non-managed environment. I think it would be best to
wait until that RFC becomes public before incorporating an OSGi-enablement
patch into OpenJPA. Feel free to continue working the issues outlined in my
initial review, but my position at this time would be to wait before
integrating any code changes.
Thanks,
Kevin
> OSGi Aware Persistence Provider Implementation
> ----------------------------------------------
>
> Key: OPENJPA-1403
> URL: https://issues.apache.org/jira/browse/OPENJPA-1403
> Project: OpenJPA
> Issue Type: New Feature
> Reporter: Milinda Lakmal Pathirage
> Attachments: osgi.patch
>
>
> Current OpenJPA trunk implementation doesn't have full support for using
> OpenJPA in OSGi containers. For example when OSGi bundle which use OpenJPA
> deployed, OpenJPA persistence provider cannot locate the persistence.xml in
> that bundle due to class loading differences in OSGi environment. EclipseLink
> has resolved this by using bundle listeners and JPA specific OSGi bundle
> header. Patch provided in this JIRA solve issues in OpenJPA in OSGi
> environment by following method used in EclipseLink. But there is a problem
> with current OpenJPA implementation which caused me to add Dynamic-Imports
> header to OpenJPA OSGi bundle to allow loading classes from bundles that use
> OpenJPA. I think current OpenJPA implementation doesn't provide support to
> replace central class load to support loading classes from bundles which use
> OpenJPA. If we have that support we'll be able to remove Dynamic-Imports and
> make OpenJPA OSGi bundle follow OSGi best practices .
> Please review the path and provide your ideas about this patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
