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.
Sent from my iPod
On Jan 23, 2010, at 3:57 AM, ant elder <[email protected]> wrote:
On Fri, Jan 22, 2010 at 5:47 PM, Raymond Feng <[email protected]>
wrote:
Hi,
I came across a scenario where multiple Nodes are created from the
same
NodeFactory. For example, in an OSGi framework, we have a singleton
of
NodeFactory which internally maintains the ExtensionPointRegistry.
Two Nodes
(A and B) with the same domain URI are created from the
NodeFactory. These
two Nodes will share the same EndpointRegistry as they have the same
domainURI and domainRegistryURI. Node A publishes an endpoint to the
EndpointRegistry and it will be seen by Node B. In this case, we
cannot tell
if the endpoint from A is local or remote to B. As a result,
binding.sca
cannot decide if it should handle the invocation from B to A as a
local or
remote one.
What do we expect should actually be happening in that case? AFAICT
right now the code will treat all the endpoints from either node A or
B as local to both nodes A and B. That doesn't seem unreasonable to me
and its why some of the one-JVM multi-node tests we have pass, but is
it what we want? From the comment above it sounds like that isn't
expected?
...ant
