On Sat, Jan 23, 2010 at 4:35 PM, Raymond Feng <[email protected]> wrote: > That's not expected in three common use cases where the nodes are running > under different classloading spaces in the same VM that shares the Tuscany > runtime. > > 1. OSGi bundles > 2. Web applications > 3. JEE apps > > Invocations across such nodes have to be handled as remote ones even though > bindings can choose to optimize in this colocation case. >
Every invocation across contributions is likely to be using different class loaders, its not specific to just those environments. Some of the tests and runtimes we have do do this and its working ok and correctly using the remote sca binding, could you add a simple testcase for your specific scenario to help understand and debug it? ...ant
