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? 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?!? 3. Is soaplib and the wsdl generation supposed to interoperate with the Microsoft Web Services tools? Any tips? 4. Is soaplib supposed to generate wsdl which validates using the WS-I tools? -- Zander
_______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
