Greetings, I am passing SDO's as parameters between two tiers of my application using RMI-IIOP. The server code is running within an application server that uses a complex classloading schema which the Tuscany SDO DefaultHelperContextImpl.SDOPackageRegistryDelegator class does not handle well. Specifically, I end up 7 classloaders with different registeries in different classloaders which totally breaks my application. In pre-SDO 1.0 days, I got around this problem by setting the following EMF system property org.eclipse.emf.ecore.EPackage.Registry.INSTANCE='org.eclipse.emf.ecore.impl.EPackageRegistryImpl'. This no longer appears to work. I would like to use SDOUtil.createHelperContext() and manage references to the HelperContext myself. However, the HelperContext created using this technique does not seem to be available/referenced when CORBA attempts to marshall my DataGraphs between tiers.
1. Any thoughts for a quick work-around to get me up and running in short order? 2. Any ideas on a longer-term solution to the problem which doesn't rely on single shared registry for the entire VM but might work better than the existing classloader-based scheme? Thanks in advance for your assistance. - Ron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
