You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Ron Gavlin (JIRA)" <tu...@ws.apache.org> on 2007/10/04 14:34:51 UTC
[jira] Created: (TUSCANY-1831) Make SDOPackageRegistryDelegator
pluggable
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
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1831) Make SDOPackageRegistryDelegator
pluggable
Posted by "Amita Vadhavkar (JIRA)" <tu...@ws.apache.org>.
[ 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1831) Make SDOPackageRegistryDelegator
pluggable
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1831) Make SDOPackageRegistryDelegator
pluggable
Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ant elder updated TUSCANY-1831:
-------------------------------
Fix Version/s: Java-SDO-Next
> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org