A service with two operations exposed over a WS binding is not handling the
incoming SOAP requests correctly
------------------------------------------------------------------------------------------------------------
Key: TUSCANY-1090
URL: https://issues.apache.org/jira/browse/TUSCANY-1090
Project: Tuscany
Issue Type: Bug
Components: Java SCA Axis Binding
Affects Versions: Java-M2
Reporter: Johny Mathew
Priority: Critical
A service with two operations exposed over a WS binding is not handling the
incoming SOAP requests correctly. I am running the helloworld-ws-asynch sample.
I am calling the getGreetings operation but the getGreetingsWithCallback is
being executed. In the wsdl file both the SOAPActions are set to "" and looks
like it is using the last operation added to the table. The Axis2 runtime picks
a MessageReceiver to dispatch the incoming request on. It picks this based on
the AxisOperation it calculates. It's calculating the wrong operation. For some
reason the org.apache.axis2.engine.SOAPActionBasedDispatcher's findOperation()
is doing the calculation and it's just looking up the soapAction in a
hashtable. I don't know whether this is an issue for the axis2 runtime or a
java2wsdl tool issue (the tool should not leave the SOAPAction as "")
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
