You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jonas Boëthius (JIRA)" <ji...@apache.org> on 2007/09/05 16:31:35 UTC
[jira] Reopened: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonas Boëthius reopened AXIS2-2389:
-----------------------------------
Still not dispatching correct, now tested on Axis2, version 1.3.
> Dispatching based on the SOAP message body does not work for document/literal style
> -----------------------------------------------------------------------------------
>
> Key: AXIS2-2389
> URL: https://issues.apache.org/jira/browse/AXIS2-2389
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.1.1
> Environment: Axis2, version 1.1.1
> Tomcat 5.0
> JDK1.6.0
> Reporter: Jonas Boëthius
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.3
>
>
> I am using a document/literal service and found that the dispatching based on the message body does not seem to work. Any SOAPAction header except the one defined in the WSDL causes the following fault:
> org.apache.axis2.AxisFault: Operation Not found EPR is...
> I've used ADB data binding and generated server side classes and services.xml using the WSDL2Java utility.
> When debugging, I can see that the SOAPMessageBodyBasedDispatcher
> is invoked for the dispatching, that it finds the correct request element name but when passing the call to the getOperation method in the AxisService class, the operationsAliasesMap does not contain the name of the request element. It seems like the initialization of the operationsAliasesMap does not consider the case needed for the SOAPMessageBodyBasedDispatcher.
> Found an easy work-around of manually adding the name of the request root element as actionMapping in the generated services.xml file.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org