[
https://issues.apache.org/jira/browse/TUSCANY-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-3081:
--------------------------------
Attachment: 3081-1.patch
This patch enables an in-JVM endpoint registry so that the
itest/'nodes/two-nodes-test runs successfully. It's not particularly tidy and
also not very scientific. The approach I've taken is to delay the reference
resolution until chain creation time and this causes all sorts of problems
across the runtime.
A simple example, if you set a callback object that hasn't been used then the
runtime sends unititialized callable references across the wire as part of the
callback information. This is because the callback object won't have been
callIed, the chains won't have been created and hence the endpoint references
won't have been resolved. Easy to say here but you can imagine the difficulty
in chasing this kind of problem down.
I've gone in and fixed all of the issues to get a clean build but I'd like to
take a step back and take what I know now and make sure that the design of this
change is based on some consistent model.
If you'd like me to commit what I have anyhow I can do that but just giving
this heads up first.
> Implement a local endpoint registry mechanism to allow multiple in-JVM nodes
> to resolve endpoints. Stepping stone to more dynamic remote resolution.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3081
> URL: https://issues.apache.org/jira/browse/TUSCANY-3081
> Project: Tuscany
> Issue Type: Improvement
> Affects Versions: Java-SCA-2.0-M3
> Environment: All
> Reporter: Simon Laws
> Fix For: Java-SCA-2.0-M3
>
> Attachments: 3081-1.patch
>
>
> Currently our endpoint resolution is static and, when more than one node is
> running in a domain in 1.x, relies on a domain manager to create the
> composite configuration necessary for components to commnicate across node
> boundaries. As a way to allowing greater flexiblity of deployment an endpoint
> registry should give us the opportunity to monitor endpoints as they are
> created and resolve endpoint references at the point of use.
> This JIRA is an umberella for the work to build out the endpoint registry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
