[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-bindings] Re: Proposed resolution to issue 54, attempt #5
Mike raises a question which I don't know how to resolve: Mike Edwards wrote: [snip] [snip] I really don't know what to suggest here, in that I agree that it is vague. I had thought that Assembly had some tighter language around some notion of a deployment URI, but after just reviewing, I don't see it. I'm left with a few options, and the last one I felt like I should add, just because specifying a URI for a service at the time you're composing a composite is rife with issues. Options:
I'm almost ready to throw in the towel, because I don't see that we can tightly define this in a sensible way. For services, I'd suggest adding text on the order of this: In determining the URI for a service, implementations are encouraged to attempt to honor the value(s) of @uri attribute, the URI in a wsa:Address element from an endpointReference, the URI indicated by WSDL port via a @wsdlElement attribute references, and the structural URI for the binding. Comments? -Eric. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]