[ http://issues.apache.org/jira/browse/AXIS-2288?page=comments#action_12356811 ]
Tom Jordahl commented on AXIS-2288: ----------------------------------- You are correct, the dispatching of the operations is based on the child element of the SOAP body. How would you expect this to work? SOAPAction is usually used for this kind of 'same message' problem. You would have to write your own handler to do this dispatching (I don't think we have one lying around in Axis). You would also have to add the SOAPAction values to the WSDL binding. I think you cna do this in the WSDD file on a per-operation basis (if you, can't it should be added). > Bad document style request processing > ------------------------------------- > > Key: AXIS-2288 > URL: http://issues.apache.org/jira/browse/AXIS-2288 > Project: Apache Axis > Type: Bug > Components: WSDL processing > Versions: 1.3 > Environment: Windows XP, Jakarta Tomcat > Reporter: Inma Marín > Priority: Critical > > I generate code from WSDL using WSDL2Java for a service which uses Document > style. This service consists of 2 methods ( method1 and method2), both of > them has an input argument of type "base64Binary" called "param". After > deploying my service, I invoke the first method: > SOAPAction: "urn:myService#method1" > ...... > <soapenv:Body><param > xmlns="urn:mySchema">U0c5c1lTQmpZWEpoWTI5c1lRPT0=</param></soapenv:Body> > and the service executes the correct method (method1). > On the contrary, when invoking the second method: > SOAPAction: "urn:myService#method2" > ...... > <soapenv:Body><param > xmlns="urn:mySchema">U0c5c1lTQmpZWEpoWTI5c1lRPT0=</param></soapenv:Body> > > the server does not execute method2, method 1 instead is executed. > Maybe, the code is not generated correctly, because the service is not able > to recognize which method (method1 or method2) has to be executed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
