On Wed, Jun 9, 2010 at 5:25 PM, Raymond Feng <[email protected]> wrote: > Per the assembly spec, <binding.sca> cannot have @uri at the service side. > First of all, there is already a structural URI for the binding, such as > component1/Service1/scaBinding. This is what is needed by the reference > binding side as the "target". When we map binding.sca to a concrete binding > such as binding.ws, the deployed URI (endpoint address) should be derived > from the structural URI. The physical endpoint address will be propagated > through the endpoint registry so that the reference side can access the > service using that. IIRC, we set the deployed URI onto the @uri of the > binding for the purpose of serialization. > Thanks, > Raymond > ________________________________________________________________ > Raymond Feng > [email protected] > Apache Tuscany PMC member and committer: tuscany.apache.org > Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com > Personal Web Site: www.enjoyjava.com > ________________________________________________________________ > On Jun 9, 2010, at 3:19 AM, Simon Laws wrote: >
Thanks Raymond. I think that means you're agreeing with me that the current tests for delegation to binding.ws and binding.rmi are in error. Simon
