Next in thread →
Next in month →
Re: [sca-bindings] Issue-19: different proposal for resolution...
Excellent point. The rules for specification and calculation of URIs should be defined in section 2.1, not here. Minor correction: this issue relates to lines 81-83 of the Web Service Binding spec (not JCA) at http://www.oasis-open.org/apps/org/workgroup/sca-bindings/download.php/26326/sca-wsbinding-1.1-spec-WD-01.pdf Simon Simon C. Nash, IBM Distinguished Engineer Member of the IBM Academy of Technology Tel. +44-1962-815156 Fax +44-1962-818999 Eric Johnson <> 27/02/2008 22:42 To OASIS Bindings <> cc Subject [sca-bindings] Issue-19: different proposal for resolution... We've taken issue with lines 81-83 of http://www.oasis-open.org/committees/download.php/26837/sca-jcabinding-1.1-spec-WD-01.pdf, which currently read: "In this case, the identified WSDL binding must have an equivalent PortType with the SCA service or reference. In this case the endpoint address URI for the SCA service or reference must be provided via the URI attribute on the binding." I'm confused. Why bother with the second sentence at all? When the @wsdlElement isn't present at all, we currently don't feel it necessary to highlight that the service or reference URI might be derived, or specified with the @uri attribute. Why do we need to state this again here? Especially since section 2.1 immediately follows, and pretty much tells you how to get a URI if one isn't available from the referenced WSDL information, I think this extra "clarification" doesn't help matters. -Eric. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Next in thread →
Next in month →