[
https://issues.apache.org/jira/browse/TUSCANY-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567578#action_12567578
]
Kelvin Goodson commented on TUSCANY-1831:
-----------------------------------------
I guess we could parallel the way that the default HelperProvider
implementation is made pluggable in the SDO API project's HelperProvider class,
where the default impl is looked up by PROPERTY_NAME.
> 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]
