On 07/08/11 01:34, Tres Seaver wrote: > 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]). >
well, it's The Right Thing(tm) to do anyway. so here's my take at it: https://github.com/arskom/rpclib/commit/5b18c648885e45e47e37c09e93b44877da18fc2c best, burak _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
