Skip to content
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

Open
morsupil opened this issue Oct 15, 2012 · 3 comments
Open

Namespace not defined in soap response #17

morsupil opened this issue Oct 15, 2012 · 3 comments
Assignees

Comments

@morsupil
Copy link

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

@ghost ghost assigned rancavil Oct 17, 2012
@morsupil
Copy link
Author

Still have the same same problem after modifying the namespace :-(
I've done some debug with mono C# implementation under linux and have the same error.
The return of my webservice is ok BUT it seems that the .net client receive null in the response object...
Here is the mono error:
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
at Testwol.Main (System.String[] args) [0x00000] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
at Testwol.Main (System.String[] args) [0x00000] in :0

@rancavil
Copy link
Owner

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]
Para: rancavil/tornado-webservices [email protected]
CC: Rodrigo Ancavil del Pino [email protected]
Enviado: Miércoles, 17 de octubre, 2012 12:39 P.M.
Asunto: Re: [tornado-webservices] Namespace not defined in soap response (#17)

Still have the same same problem after modifying the namespace :-(
I've done some debug with mono C# implementation under linux and have the same error.
The return of my webservice is ok BUT it seems that the .net client receive null in the response object...
Here is the mono error:
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
at Testwol.Main (System.String[] args) [0x00000] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
at Testwol.Main (System.String[] args) [0x00000] in :0

Reply to this email directly or view it on GitHub.

@morsupil
Copy link
Author

Thanks rodrigo...
Let me know if i could help you with this case...

Michael

2012/10/17 Rodrigo Ancavil del Pino [email protected]

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]
Para: rancavil/tornado-webservices [email protected]

CC: Rodrigo Ancavil del Pino [email protected]
Enviado: Miércoles, 17 de octubre, 2012 12:39 P.M.
Asunto: Re: [tornado-webservices] Namespace not defined in soap response
(#17)

Still have the same same problem after modifying the namespace :-(
I've done some debug with mono C# implementation under linux and have the
same error.
The return of my webservice is ok BUT it seems that the .net client
receive null in the response object...
Here is the mono error:
Unhandled Exception: System.NullReferenceException: Object reference not
set to an instance of an object
at Testwol.Main (System.String[] args) [0x00000] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object
reference not set to an instance of an object
at Testwol.Main (System.String[] args) [0x00000] in :0

Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-9535927.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants