On 02/27/12 19:21, Benjamin Cardon wrote:
On line 77 you can see that a partial class is generated that contains
the parameters of the function in question. On line 34, you can see
that a function is created that takes this 'say_hello' object as a
parameter. This is unfortunately not a pleasant way for this to be
handled :( As a point of reference, in Soaplib 0.8.2 this is not the
functionality that existed.
ah. that's because of rpclib's wrapping of function arguments. somebody
had started a "bare" branch and did some work there, but didn't finish
it. it's still in the project's repository.
normally, soap clients (e.g. suds) use some heuristics to detect this
and 'sanitize' the soap api.
I also tried to test with this new URL and got the same error message
as it tried to post with the ?wsdl tacked on the end.
[27/Feb/2012 11:14:34] "POST /hello_world/?wsdl HTTP/1.1" 403 2326
I'm not sure of a resolution to this as the functionality that .NET
usually has is that you don't provide a link to the wsdl and it
discovers it from the webservice automatically.
I downloaded your fork, run it and got the actual error message for you:
http://pastie.org/3474534
Here's the gist of the error:
No CSRF or session cookie.
does this ring any bells?
I guess I've also fixed the relative/absolute import mess.
https://github.com/plq/rpclib/commit/ea9ff9e7db77ef5ea74e8798eb102a03feee1c0d
best,
burak
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
