-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm working on implementing a standard service (WSRP 1.0), where the WSDL for types / interfaces / messages is already mandated by the specification[1][2][3]. I have a version which works with suds, but which is rejected by the Java clients because the generated WSDL doesn't match the spec.
I tried overriding the application to hard-wire the returned WSDL: the Java clients would then fail in executing the first method, because the messages it returns don't match the spec: they contain an extra wrapper element for the response type. Has anyone run into similar issues trying to implement a "fixed" WSDL specification with soaplib? I know that ZSI had support for generating both client and server stubs from a given WSDL document -- perhaps I need to use ZSI instead. [1] http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_types.xsd [2] http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl [3] http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [email protected] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkz2O7UACgkQ+gerLs4ltQ4jdwCgxxYGfyOX+EdgVrWRvIWS6RuI dnsAoKnZzdxBeF1094QHX4mzU7xKMQl1 =TTaw -----END PGP SIGNATURE----- _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
