[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE - ws binding - Rules for WSDL generation create invalidWSDL by using "/" where it is not allowed.
TARGET: Web Services Binding, draft 20070925 DESCRIPTION: In section 4.5 (20070925 draft), the specification discusses WSDL generation, and appears to use "/" characters in elements of WSDL that do not allow the "/" <definitions name="componentName/serviceName" targetNamespace="HTTP Base URI/componentName/serviceName".... The trouble is that in WSDL 1.1, /definitions/@name is an NMTOKEN, so "/" is not allowed to appear. http://www.w3.org/TR/wsdl#A4.1 http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-Nmtoken Likewise, with: <binding name="/service/binding.ws[n]/@name+[/soapVersionPrefix]+'Binding'" type="SCA service interface portType name"> the binding/@name attribute is likewise an NCNAME, so slashes are again not allowed. http://www.w3.org/TR/wsdl#A4.1 http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName PROPOSAL: Replace "/" character in the "/definitions/@name" examples with "-". The definitions/@name attribute should look like "componentName-serviceName". It appears that the binding/@name attribute is really written as if it were some kind of XPath expression. In which case, the only error is that the "[/soapVersionPrefix]" implies the use of a non-existent root element, or it is intended as a "/" plus the ${soapVersionPrefix} value (written here as an Ant variable reference). If that is the intent, then the "/" should be replaced with "-".
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]