Also Tres, Do you think that just dropping the sequence from the response will give you a working solution to your issue? If so, I can try and get that done this afternoon and not hold things up with finishing re-working the wsdl ans schema code and the 40+ test cases that I've seemed to find along with those changes :)
Let me know and if you like we can discuss this further off-list. On Fri, Dec 10, 2010 at 7:20 AM, Tres Seaver <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/09/2010 05:14 PM, Brad Allen wrote: > > On Thu, Dec 9, 2010 at 2:48 PM, Chris Austin <[email protected]> > wrote: > >> On Thu, Dec 9, 2010 at 2:14 PM, Tres Seaver <[email protected]> > wrote: > >>> 3. I want some way to suppress the wrapping of returned objects in > >>> sequences (see issue 4, > >>> https://github.com/soaplib/soaplib/issues#issue/4). I'm thinking > >>> of maybe spelling that as a '_returns_direct' argument to 'rpc()'. > >>> > >>> For my enlightenment: does anybody know the rationale for adding the > >>> sequence wrapper? > > > > Like Chris Austin I have no idea where this came from. Chris checked > > the SOAP spec and only one return value is expected...a sequence is > > not called for. > > > > Maybe someone was thinking about how Python functions support multiple > > return values? > > > > If it's not in the spec I don't see why soaplib should do it at all. > > If multiple return values are ever needed then a sequence can always > > be specified as the return type, right? > > Perhaps the sequence wrappers are implemented with the "rpc" operation > style in mind? See: http://www.w3.org/TR/wsdl#_soap:operation and > http://www.w3.org/TR/wsdl#_soap:body, which then refer > tohttp://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383533, which > says (about the response): > > - - A method response is modelled as a struct. > > - - The method response is viewed as a single struct containing an > accessor for the return value and each [out] or [in/out] parameter. > The first accessor is the return value followed by the parameters in > the same order as in the method signature. > > However, soaplib emits WSDP for bindings and operations as > 'style="document"', which doesn't need any of that. > > Perhaps I should add a '@document' decorator, which causes the WSDL for > return types to be what I need, and have the '@rpc' decorator cause the > biniding to be marked with 'style="rpc"'? > > > 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/ > > iEYEARECAAYFAk0CKQoACgkQ+gerLs4ltQ4cKACeMo+XfkGk+P9WH6Kx79VKnZP2 > rk0AoNFTgspA/AYHddKjMYFkQpt/xkpf > =THPo > -----END PGP SIGNATURE----- > > _______________________________________________ > Soap mailing list > [email protected] > http://mail.python.org/mailman/listinfo/soap >
_______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
