Improve mechanism for determining locality of endpoints to endpoint references
------------------------------------------------------------------------------
Key: TUSCANY-3441
URL: https://issues.apache.org/jira/browse/TUSCANY-3441
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-2.0
Environment: All
Reporter: Simon Laws
See this thread
(http://www.mail-archive.com/dev%40tuscany.apache.org/msg11294.html)
Within a single domain where a reference is wired to a service there are a
number of scenarios that we need to take account of:
1 - target service component and reference component are running in separate
nodes in separate JVMs
a remote sca binding must we used
2 - target service component and reference component are running in separate
nodes in the same JVM
a mechanism for crossing classloader boundaries is required
3 - target service component and reference component are running in the same
node (and hence the same JVM)
3a - the service and reference are in the same composite andhence
contribution.
local optimization is possible
3b - the service and reference are in different composites and possible
contributions
a mechanism for crossing classloader boundaries is required
We could use explicit information on the endpoint/endpoint reference to
determine which of the above is true. The following has been proposed.
domain uri
node uri
would also be useful to have the containing composite name for autowire
matching purposes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
