[ 
https://issues.apache.org/jira/browse/OPENJPA-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783259#action_12783259
 ] 

Craig Russell commented on OPENJPA-1403:
----------------------------------------

I'm not an OSGi expert, but it's not clear to me that OpenJPA should have 
"support to replace central class load[er]" to load classes that it doesn't 
statically know about. User-defined classes are by definition supposed to be 
loaded dynamically (as far as OpenJPA is concerned). 

So why is Dynamic-Imports not "OSGi best practice" for service providers such 
as OpenJPA? 

> 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.

Reply via email to