[snip]
Raymond Feng wrote:
Hi, Ant.
I agree with you that we should generalize the service binding URI. I
think I have a proposal here.
When the CompositeBuidler builds the composite, we should calculate
the service binding URI based on various pieces of the information as
defined by the spec and save the effective URI in the service binding
so that Binding.getURI() will return the good URI. This way, the
binding providers doesn't have to deal with the calculation.
If you guys think it's the right way to go, I can try to add the
function to the CompositeBuilder.
This is also related to how a binding is mapped to a protocol (scheme)
and baseURI. The topic is being discussed on the ML under "SCA Binding
and Distribution".
Thanks,
Raymond
This initially sounds reasonable to me, but how are you going to handle
protocol/binding specific URIs in CompositeBuilder? not all binding URIs
start with http://...
Would it be possible to let the Binding extension decide what form the
URI should take?
Maybe we could have have another field on the base Binding named
computedURI (computed by CompositeBuilder), which the binding extension
could use to compose the value of the actual URI field?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
