Trailing slash for HTTP binding

Thanks for your input Dmitri and Javier ! Since the spec says not to have a trailing space i suppose we can safely remove it. Would it cause problems for people here ? Or did you just all hack the constant to make it work ? I'll apply Michele patch for WSDL caching and will roll a RC1 release later this week. Arnaud. > Hi .* > Some words about http namespace in WSDL... > > in W3C Note (15 March 2001) for WSDL > (http://www.w3.org/TR/wsdl) you'll find > the following namespace prefixes: http -> > http://schemas.xmlsoap.org/wsdl/http/ : WSDL namespace for > WSDL HTTP GET & > POST binding (1.2 Notational Conventions) ... but in all > samples in the > same document we see : ... <soap:binding style="document" > transport=http://schemas.xmlsoap.org/soap/http /> ... In > the section 3.3 > soap:binding we read: ... The value of the required transport > attribute > indicates which transport of SOAP this binding corresponds > to. The URI value > http://schemas.xmlsoap.org/soap/http corresponds to the HTTP > binding in the > SOAP specification. Other URIs may be used here to indicate > other transports > (such as SMTP, FTP, etc.). > > I have never seen any WSDL documents using > http://schemas.xmlsoap.org/wsdl/http/ (with trailing slash) > namespace... So > i think the possible reason for this confusion either just typo in W3C > Recomendation (!?!?) or some of the implementations (.NET?) > do not really > understand the clause "... The keywords "MUST", "MUST NOT", > "REQUIRED", > "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", > "RECOMMENDED", > "MAY", and > "OPTIONAL" in this document are to be interpreted as > described in RFC-2119 > [2]." ;) > > > Me vote for removing this trailing slash from http namespace...