search

falc410 / pysimplesoap

Automatically exported from code.google.com/p/pysimplesoap
0 stars 0 forks source link

SOAPAction issue on automatically generated WSDL #144

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a simple SOAP Server as indicated in pysimplesoap documentation
2. Let the WSDL be generated by pysimplesoap
3. Display WSDL content through command-line or through webpage

What is the expected output? What do you see instead?
We should see this line "SOAPAction: 
http://127.0.0.1:8000/webservices/sample/call/soap" as explained in 
documentation (https://code.google.com/p/pysimplesoap/wiki/WsdlSupport).
But here is the value generated : "SOAPAction: 
http://127.0.0.1:8000/webservices/sample/call/soapSubIntegers" (concatenation 
of soap + method name)

What version of the product are you using? On what operating system?
Using v1.11 with web2py but seems to be the same on latest version 1.14 (in 
regards with the code)

Please attach the related WSDL (if any), a small code fragment to reproduce
and provide any additional information below.
I found in code of "server.py" (line 409) : soapop['soapAction'] = self.action 
+ method
By removing "+ method" or adding a "/" (like "self.action + '/' + method") is 
working fine.

Don't hesitate to tell me if you need further information.
Thanks for your help !

Baptiste

Original issue reported on code.google.com by baptiste...@gmail.com on 28 May 2014 at 8:50

GoogleCodeExporter commented 9 years ago 
Hello Baptiste, thanks for your contribution!

Do you have any test that could be added to the project about this issue?

Is any tool or library complaining about this issue (for example, SoapUI)?

Just to know what will the implications of this issue and how document it 
better.

Original comment by reingart@gmail.com on 30 May 2014 at 2:19

GoogleCodeExporter commented 9 years ago 
Hello !

On my side I've tested with SoapUI and pysimplesoap and didn't get any error.

The user who raised me this error was using Java WebServices with Apache CXF 
(based on Eclipse platform).
That's why we've checked what was happening with the WSDL file and found out 
that the URI generated in SOAPAction field was returning an HTTP 404 Error due 
to this concatenation of soap + method name.

So, even if there is no issue on some tools, the fact that an incorrect URI can 
be generated should perhaps be avoided ? What do you think ?
I'm not sure about what the best solution is (removing method name or 
concatenate it by adding a '/').

Thanks for your help !

Original comment by baptiste...@gmail.com on 2 Jun 2014 at 9:38