Hi Burak, On 2 août 2011, at 13:19, Burak Arslan wrote:
> On 08/02/11 13:51, Burak Arslan wrote: >> >>> 4. Is soaplib supposed to generate wsdl which validates using the WS-I >>> tools? >>> >> >> no but that'd be nice :) >> > > i've actually taken a look at the wsdl files generated by both versions of > soaplib. > > https://github.com/soaplib/soaplib/blob/soaplib-1.0.0/src/soaplib/test/wsdl.xml > https://github.com/soaplib/soaplib/blob/master/src/soaplib/core/test/wsdl.xml > > i guess the important difference is that in 1.0 we have just one service tag > like so: > > [...] > > whereas in trunk we have multiple service tags for each service class, like > so: > > [...] > > according to the commit history, that's where this was introduced: > > https://github.com/rbarrois/soaplib/commit/8530a70b4a43773cf2d3d6997991ec8187e0a3ba > > So maybe the original author can chime in? Passing the wsi tests should be an > important goal of soaplib. any help on this subject would be appreciated. I'm responsible for this change. When defining an "application" with several services (i.e DefinitionBase subclasses), the previous behaviour did put all methods of all services into a single WSDL "service". This commit splits them in various WSDL services, which is imho the expected behaviour. Another difference between those versions, maybe related to the current error, is that the new WSDL add this import at the toplevel schema: <xs:import namespace="http://www.w3.org/2001/XMLSchema"; /> I couldn't find the WS-I validation tool, but WSDLs generated with the current version of soaplib can be used correctly with at least : suds, soapUI and some Microsoft Web Service Client (I don't know which exact version is being used by the people I'm working with). Let me know if this specific patch introduces non-validating changes, I'd be happy to contribute fixes. -- Raphaël Barrois _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
