[
https://issues.apache.org/jira/browse/TUSCANY-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717222#action_12717222
]
Simon Laws commented on TUSCANY-3081:
-------------------------------------
You spotted a couple of things that go caught in the patch that I didn't intend
to check in. Good job I didn't press the button on Friday. I've gone ahead now
and committed the relevant changes. You can now ignore 3081-1.patch.
Still quite a bit of commented out code which will hopefully be tidied away
this wee as we get the EnpointReference2 and Endpoint2 serialization story
sorted out and we can finally remove all of the "2" extensions from these
classes.
> 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.
