[ 
https://issues.apache.org/jira/browse/TUSCANY-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566995#action_12566995
 ] 

Amita Vadhavkar commented on TUSCANY-1831:
------------------------------------------

I am not very sure, but there was some design discussion in Tuscany-1459 and 
the requirement in current JIRA and the topic of Tuscany-1459 can be having some
conflicts. I guess it will be better, if we can discuss this more on ML and 
come up with some exact code level suggestions about what can be done and what
can be the implications etc.  Let me start a ML thread and let us get some 
inputs from those involved in Tuscany-1459 and others.

> Make SDOPackageRegistryDelegator pluggable
> ------------------------------------------
>
>                 Key: TUSCANY-1831
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1831
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SDO Implementation
>    Affects Versions: Java-SDO-Next
>            Reporter: Ron Gavlin
>             Fix For: Java-SDO-Next
>
>
> The current SDOPackageRegistryDelegator implementation assumes that a 
> standard, hierarchical classloader structure is present in the "hosting 
> environment". BEA WebLogic, for example, uses an unusual "change aware" 
> classloading scheme which does not meet the expectations of the 
> SDOPackageRegistryDelegator. Prior to Tuscany SDO 1.0, I was able to 
> work-around this former EMF problem by setting the EMF JVM property 
> "org.eclipse.emf.ecore.EPackage.Registry.INSTANCE". In Tuscany SDO 1.0, this 
> setting is no longer relevant. I would like to be able to plugin my own 
> SDOPackageRegistryDelegator implementation that provides a 
> non-classloader-aware registry, knowing full well the limitations of of this 
> implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to