On 08/02/11 00:27, Zander Lichstein wrote: > We're trying to expose a set of soap services to a 3rd party who is > using the MS toolset. The net effect of the problem is that his tools > throw a bunch of errors when trying to read my wsdl, and I can also > confirm that the WS-I validator in soapUI fails as well with a bunch > of cryptic errors - though the services seem to work if I don't worry > about validation. I don't expect the group to solve all my problems > for me, but I have a few questions which might help: > > 1. The namespace defined by http://www.w3.org/2001/XMLSchema is > referenced in the namespace.py constants, but that particular URL is > not an xsd at all, so validation fails. Why is that URL included and > not the .xsd version? Is that supposed to work?
Hi Zander, When we include the url, the popular schema parsers start recursively retrieving relavant xml schema files online. This behaviour will get you banned from those services eventually. no consensus was reached about whether/how to include these files, so i guess everybody patches the relevant part of the code to suit their needs. > 2. That same namespace ends up nested as imports within most "types" > nodes with Primitives. For example: > > <wsdl:definitions ...xmlns:xs="http://www.w3.org/2001/XMLSchema"; <-- > This causes problems > ... > <wsdl:types> > ... > <xs:schema targetNamespace="pim_ipsapi" elementFormDefault="qualified"> > <xs:import namespace="http://www.w3.org/2001/XMLSchema"/> <-- > Why is this namespaces being imported again... under itself?!? > my comments above apply to this point as well. > 3. Is soaplib and the wsdl generation supposed to interoperate with > the Microsoft Web Services tools? Any tips? I don't have access to any Microsoft boxes, so I personally can't help you with the latest rpclib/soaplib. Nobody contributed tests, so I can't test my changes against MS toolbox either. However, I was told that soaplib 1.0 interoperates fine with ms toolbox. It is actually passing all WS-I tests. You can just use it. The WS-I test infrastructure is still there, and it's going to be your starting point if you're willing to contribute to the latest versions. see: https://github.com/soaplib/soaplib/blob/master/src/soaplib/core/test/interop/test_wsi.py https://github.com/soaplib/soaplib/blob/master/src/soaplib/core/test/README > 4. Is soaplib supposed to generate wsdl which validates using the WS-I > tools? > no but that'd be nice :) i hope that helps, burak
_______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
