-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/07/2011 05:21 AM, Burak Arslan wrote:
> it's not a soaplib issue per se, it's the client's decision to fetch > & store remote schema imports (or not). but it's not necessary to > include it either, as soap clients tested with soaplib don't complain > about the missing import. > > this was introduced here: > > https://github.com/soaplib/soaplib/commit/f88dca6671083a54dad7cb00b9d034cdb8dd0e73#L1L84 > > As this change had no apparent benefit at all, i reverted it for > rpclib here: The point of the change was to make it possible to emit WSDL which conforms to standards (WSRP[1] was the motivating example) which mandate mapping some portions of a request / response as attributes, rather than sub-elements, Without that option, one cannot use soaplib to implement an interoperable WSRP server; with it, one can (see wsrplib[2]). [1] http://en.wikipedia.org/wiki/Web_Services_for_Remote_Portlets [2] https://github.com/soaplib/wsrplib 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/ iEYEARECAAYFAk4WNGwACgkQ+gerLs4ltQ4haQCfaHjaWn1bN8zLGE6dZYiDti2O tn8An1MrM2O1B5UQPvdyHA0iMplHVE0h =fn+c -----END PGP SIGNATURE----- _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
