-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Namespace not defined in soap response #17
Comments
Still have the same same problem after modifying the namespace :-( |
I have the same error with mono and C#....I am cheking the module that generates the response in the API. Thank for the feedback. Stay in contact. Rodrigo. De: morsupil [email protected] Still have the same same problem after modifying the namespace :-( |
Thanks rodrigo... Michael 2012/10/17 Rodrigo Ancavil del Pino [email protected]
|
Hello all,
It seems that there is a problem with a .net client with the response done by tornado.
After some test it seems that the problem is that .net expect a reference to the namespace in the soap response like:
xmlns:ns1="http://1.1.1.1:8080/WolService
Any idea for doing this with tornadows?
Michael
The text was updated successfully, but these errors were encountered: