snip... > > >>The value from the reference target is currently set to the target when > > the reference is matched to a target service. > > > I don't quite follow the above. Are you saying that the service URI > is copied into the reference binding URI at the matching stage? Is this > the fully resolved absolute service URI rather than the relative URI > that a client target attribute would specify? >
Yes. It's the binding uri that the component service holds. For a local SCA binding this will be the same as the target name that the user entered into the composite file except where the shortened form of the service name is used. In the case where a remote binding is in use it should be the fully resolved URI. The domain does this for us at the moment at run time. As I said earlier in this thread there is a case for changing this calculation to happen at deployment time so instead of the domain providing updates to nodes telling the node when service URIs change the deployment stage would be expected to provide a fully resolved composite at the point at which the composite is started. The result would though be the same in that the binding URI would correctly represent the endpoint details of the referenced service. The point in time at which that information is know though is different. Simon
