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: > In our binding.sca support (and tests [1]) we allow/expect a uri in > the binding to determine the location of the protocol endpoint. > ASM90005 means that we can't do this and the tests report errors. I > couldn't find a JIRA with a quick look but I haven't worked recently > on the binding.sca delegation code. If there is one, or if someone is > already working this, please shout. > > Generally I'd hope that this URI could be determined using defaults, > i.e. I wouldn't expect the application developer to be specifying it. > > If it were really required, for example, for convenience of tests, I > guess we could exploit binding extensibility and support a sub element > of <binding.ws/>. > > Simon > > [1] > http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/itest/nodes/binding-sca-hazelcast/src/test/resources/ws/simpleService/HelloWorld.composite > > -- > Apache Tuscany committer: tuscany.apache.org > Co-author of a book about Tuscany and SCA: tuscanyinaction.com
