I'm wondering if we can combine the Endpoint and RRB efforts together. Here are some ideas:

1) An SCA service has a list of Endpoints representing the end point for each binding protocol.

2) An SCA reference has 0..N Endpoints depending on the multiplicity of the reference.

3) Each endpoint has a binding interface contract. If it's not known before the operation selector, then it's an "Any" interface with an "Any" operation.

4) There is one invocation chain for each endpoint (based on the binding interface contract) and one for the SCA service or reference. The two invocation chains are connected as we described on the wiki page. For a SCA service configured with multiple bindings, there will be multiple endpoint invocation chains connecting to the same service invocation chain. It's similar for SCA references.

Thanks,
Raymond

Reply via email to