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/03/26 13:10:32 UTC
[jira] Created: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
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
Priority: Minor
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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504293 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2389:
-----------------------------------------------------
can you attach your wsdl, service class and the client code?
> 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
>
> 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
[jira] Reopened: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
Posted by "Jonas Boëthius (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2389:
------------------------------------
Assignee: Amila Chinthaka Suriarachchi
> 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: Minor
>
> 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
[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2389:
------------------------------------
Priority: Critical (was: Blocker)
> 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: Critical
> Fix For: 1.3
>
> Attachments: EchoApi.wsdl, request_response.log
>
>
> 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
[jira] Closed: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srinath Perera closed AXIS2-2389.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.3
I ran some tests and I belive this is fix on the trunk. I am closing the issue. If you see the error please reopen it with WSDL and client code.
> 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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525627 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2389:
-----------------------------------------------------
it seems you are using tomcat with a different context root than axis2. and also you wsdl has service name EchoApiService and url uses the echoapi.
I'll have a look at with these changes.
If you could please check with the simpleHttpserver without those changes.
> 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
>
> Attachments: EchoApi.wsdl, request_response.log
>
>
> 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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525289 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2389:
-----------------------------------------------------
I invoke a service with your wsdl with this request which does not have any soap actions
POST /axis2/services/EchoApiService HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8
User-Agent: Axis2
Host: 127.0.0.1:8080
Transfer-Encoding: chunked
163
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Body>
<ns1:EchoRequest xmlns:ns1="http://www.apache.org/api/services/echoapi11/types">
<ns1:correlationId>id</ns1:correlationId>
<ns1:echo>echo</ns1:echo>
<ns1:boolean>true</ns1:boolean>
</ns1:EchoRequest>
</soapenv:Body>
</soapenv:Envelope>0
and it worked fine.
Can you send your request and full stack trace.
> 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
>
> Attachments: EchoApi.wsdl
>
>
> 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
[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
Posted by "Jonas Boëthius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonas Boëthius updated AXIS2-2389:
----------------------------------
Attachment: EchoApi.wsdl
WSDL of the tested service.
> 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
>
> Attachments: EchoApi.wsdl
>
>
> 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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Sach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658220#action_12658220 ]
Sach commented on AXIS2-2389:
-----------------------------
I am having same problem with AXIS2 1.4.1 release on Websphere 5.1. Attaching the logs here
This only works if you deploy the service on simple server built with AXIS2 without SOAPAction. What that means is message based dispatching does not work.
SOAP Sample:
<SOAP-ENV:Body>
<ser:searchElectronicDocument>
<requestor>NDRS</requestor>
</ser:searchElectronicDocument>
[12/19/08 15:47:49:581 EST] d207ad SystemOut O 15:47:49,580 DEBUG BuilderUtil:312 - Input contentType (text/xml;charset=UTF-8)
[12/19/08 15:47:49:582 EST] d207ad SystemOut O 15:47:49,581 DEBUG BuilderUtil:351 - CharSetEncoding from content-type (UTF-8)
[12/19/08 15:47:49:583 EST] d207ad SystemOut O 15:47:49,582 DEBUG TransportUtils:156 - createSOAPEnvelope using Builder (class org.apache.axis2.builder.ApplicationXMLBuilder) selected from type (application/xml)
[12/19/08 15:47:49:584 EST] d207ad SystemOut O 15:47:49,584 DEBUG StAXUtils:177 - XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
[12/19/08 15:47:49:586 EST] d207ad SystemOut O 15:47:49,585 DEBUG Phase:269 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking pre-condition for Phase "Transport"
[12/19/08 15:47:49:587 EST] d207ad SystemOut O 15:47:49,586 DEBUG Phase:282 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking phase "Transport"
[12/19/08 15:47:49:588 EST] d207ad SystemOut O 15:47:49,587 DEBUG Phase:289 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking Handler 'RequestURIBasedDispatcher' in Phase 'Transport'
[12/19/08 15:47:49:589 EST] d207ad SystemOut O 15:47:49,588 DEBUG RequestURIBasedServiceDispatcher:50 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking for Service using target endpoint address : http://fir.nwie.net:9087/docaccess/services/AddressBookService
[12/19/08 15:47:49:590 EST] d207ad SystemOut O 15:47:49,589 DEBUG Utils:184 - parseRequestURLForServiceAndOperation : [http://fir.nwie.net:9087/docaccess/services/AddressBookService][/docaccess/services]
[12/19/08 15:47:49:591 EST] d207ad SystemOut O 15:47:49,590 DEBUG ProjectResourceBundle:70 - org.apache.axis2.i18n.resource::handleGetObject(servicefound)
[12/19/08 15:47:49:592 EST] d207ad SystemOut O 15:47:49,591 DEBUG AbstractDispatcher:95 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Found AxisService : AddressBookService
[12/19/08 15:47:49:596 EST] d207ad SystemOut O 15:47:49,592 DEBUG Phase:303 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking post-conditions for phase "Transport"
[12/19/08 15:47:49:597 EST] d207ad SystemOut O 15:47:49,596 DEBUG Phase:269 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking pre-condition for Phase "Security"
[12/19/08 15:47:49:598 EST] d207ad SystemOut O 15:47:49,597 DEBUG Phase:282 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking phase "Security"
[12/19/08 15:47:49:598 EST] d207ad SystemOut O 15:47:49,598 DEBUG Phase:303 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking post-conditions for phase "Security"
[12/19/08 15:47:49:599 EST] d207ad SystemOut O 15:47:49,599 DEBUG Phase:269 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking pre-condition for Phase "PreDispatch"
[12/19/08 15:47:49:600 EST] d207ad SystemOut O 15:47:49,600 DEBUG Phase:282 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking phase "PreDispatch"
[12/19/08 15:47:49:601 EST] d207ad SystemOut O 15:47:49,601 DEBUG Phase:303 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking post-conditions for phase "PreDispatch"
[12/19/08 15:47:49:602 EST] d207ad SystemOut O 15:47:49,601 DEBUG Phase:269 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking pre-condition for Phase "Dispatch"
[12/19/08 15:47:49:603 EST] d207ad SystemOut O 15:47:49,602 DEBUG Phase:282 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking phase "Dispatch"
[12/19/08 15:47:49:604 EST] d207ad SystemOut O 15:47:49,603 DEBUG Phase:289 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking Handler 'SOAPMessageBodyBasedDispatcher' in Phase 'Dispatch'
[12/19/08 15:47:49:605 EST] d207ad SystemOut O 15:47:49,604 DEBUG Phase:289 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking Handler 'RequestURIBasedDispatcher' in Phase 'Dispatch'
[12/19/08 15:47:49:606 EST] d207ad SystemOut O 15:47:49,606 DEBUG Phase:289 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking Handler 'RequestURIOperationDispatcher' in Phase 'Dispatch'
[12/19/08 15:47:49:608 EST] d207ad SystemOut O 15:47:49,607 DEBUG Utils:184 - parseRequestURLForServiceAndOperation : [http://fir.nwie.net:9087/docaccess/services/AddressBookService][/docaccess/services]
[12/19/08 15:47:49:609 EST] d207ad SystemOut O 15:47:49,608 DEBUG RequestURIBasedOperationDispatcher:64 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Attempted to check for Operation using target endpoint URI, but the operation fragment was missing
[12/19/08 15:47:49:610 EST] d207ad SystemOut O 15:47:49,609 DEBUG Phase:289 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking Handler 'HTTPLocationBasedDispatcher' in Phase 'Dispatch'
[12/19/08 15:47:49:611 EST] d207ad SystemOut O 15:47:49,610 DEBUG Phase:303 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Checking post-conditions for phase "Dispatch"
[12/19/08 15:47:49:612 EST] d207ad SystemOut O 15:47:49,612 DEBUG ProjectResourceBundle:70 - org.apache.axis2.i18n.resource::handleGetObject(operationnotfoundforepr)
[12/19/08 15:47:49:614 EST] d207ad SystemOut O 15:47:49,613 DEBUG Phase:315 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking flowComplete() in Phase "PreDispatch"
[12/19/08 15:47:49:615 EST] d207ad SystemOut O 15:47:49,614 DEBUG Phase:315 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking flowComplete() in Phase "Security"
[12/19/08 15:47:49:615 EST] d207ad SystemOut O 15:47:49,615 DEBUG Phase:315 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking flowComplete() in Phase "Transport"
[12/19/08 15:47:49:616 EST] d207ad SystemOut O 15:47:49,616 DEBUG Phase:334 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] Invoking flowComplete() for Handler 'RequestURIBasedDispatcher' in Phase 'Transport'
[12/19/08 15:47:49:617 EST] d207ad SystemOut O 15:47:49,617 DEBUG AxisServlet:152 - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://fir.nwie.net:9087/docaccess/services/AddressBookService and the WSA Action = null
[12/19/08 15:47:49:632 EST] d207ad SystemOut O 15:47:49,631 DEBUG AddressingHelper:70 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] isReplyRedirected: FaultTo is null. Returning isReplyRedirected
[12/19/08 15:47:49:633 EST] d207ad SystemOut O 15:47:49,632 DEBUG AddressingHelper:49 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669659] isReplyRedirected: ReplyTo is null. Returning false
[12/19/08 15:47:49:635 EST] d207ad SystemOut O 15:47:49,634 DEBUG Phase:269 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669709] Checking pre-condition for Phase "MessageOut"
[12/19/08 15:47:49:636 EST] d207ad SystemOut O 15:47:49,635 DEBUG Phase:282 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669709] Invoking phase "MessageOut"
[12/19/08 15:47:49:637 EST] d207ad SystemOut O 15:47:49,636 DEBUG Phase:303 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669709] Checking post-conditions for phase "MessageOut"
[12/19/08 15:47:49:638 EST] d207ad SystemOut O 15:47:49,637 DEBUG ApplicationXMLFormatter:139 - contentType set from messageContext =null
[12/19/08 15:47:49:639 EST] d207ad SystemOut O 15:47:49,638 DEBUG ApplicationXMLFormatter:140 - (NOTE) contentType from format is=multipart/related; boundary=MIMEBoundaryurn_uuid_9A091E02085FEBA2CF1229719669714; type="application/xop+xml"; start="0.urn:uuid:9A091E02085FEBA2CF1229719669715@apache.org"; start-info="text/xml"
[12/19/08 15:47:49:640 EST] d207ad SystemOut O 15:47:49,639 DEBUG ApplicationXMLFormatter:164 - contentType returned =application/xml; charset=UTF-8
[12/19/08 15:47:49:641 EST] d207ad SystemOut O 15:47:49,640 DEBUG ApplicationXMLFormatter:94 - start writeTo()
[12/19/08 15:47:49:642 EST] d207ad SystemOut O 15:47:49,642 DEBUG StAXUtils:265 - XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
[12/19/08 15:47:49:645 EST] d207ad SystemOut O 15:47:49,644 DEBUG ApplicationXMLFormatter:126 - end writeTo()
[12/19/08 15:47:49:646 EST] d207ad SystemOut O 15:47:49,645 DEBUG TransportUtils:430 - Did not find RequestResponseTransport cannot set response written
[12/19/08 15:47:49:647 EST] d207ad SystemOut O 15:47:49,646 DEBUG Phase:315 - [MessageContext: logID=urn:uuid:9A091E02085FEBA2CF1229719669709] Invoking flowComplete() in Phase "MessageOut"
[12/19/08 15:47:49:648 EST] d207ad SystemOut O 15:47:49,647 DEBUG TransportUtils:476 - Entering deleteAttachments()
[12/19/08 15:47:49:648 EST] d207ad SystemOut O 15:47:49,648 DEBUG TransportUtils:508 - Exiting deleteAttachments()
> 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: Critical
> Attachments: EchoApi.wsdl, request_response.log
>
>
> 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.
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Jonas Boëthius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525116 ]
Jonas Boëthius commented on AXIS2-2389:
---------------------------------------
Correct dispatching (with default configuration) to a service based on the attached WSDL is made only when the SOAPAction header has the value stated in the WSDL. For other cases the dispatching fails with error "The endpoint reference (EPR) for the Operation not found....".
Client code is not attached since I use XML spy to manipulate the SOAPAction header. Use any client which makes it possible to control the value of the SOAPAction header to reproduce the problem.
> 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
>
> Attachments: EchoApi.wsdl
>
>
> 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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Jonas Boëthius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498970 ]
Jonas Boëthius commented on AXIS2-2389:
---------------------------------------
Still the same problem in version 1.2. The work-around still applies.
> 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
> Priority: Minor
>
> 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
[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-2389:
-------------------------------------
Priority: Blocker (was: Minor)
> 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
>
> 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
[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message
body does not work for document/literal style
Posted by "Jonas Boëthius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonas Boëthius updated AXIS2-2389:
----------------------------------
Attachment: request_response.log
This is my final comment on this issue. If you cannot reproduce the problem I must accept it (and that I probably do something wrong).
The attached file contains the complete request-response for a successful invocation (with correct SOAPAction header) and a failed invocation (without the header). No stacktrace was generated.
> 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
>
> Attachments: EchoApi.wsdl, request_response.log
>
>
> 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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Jonas Boëthius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486679 ]
Jonas Boëthius commented on AXIS2-2389:
---------------------------------------
I've tried the release candidate, but I still cannot get it to work. This dispatching should work with the default configuration of the axis2.xml, shouldn't it?
> 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
> Priority: Minor
>
> 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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572682#action_12572682 ]
Davanum Srinivas commented on AXIS2-2389:
-----------------------------------------
lowering priority a bit.
> 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: Critical
> Fix For: 1.3
>
> Attachments: EchoApi.wsdl, request_response.log
>
>
> 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
[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP
message body does not work for document/literal style
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484299 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2389:
-----------------------------------------------------
please try with http://people.apache.org/~deepal/axis2/1.2-RC1/axis2-1.2-RC1.zip. I fixed this issue for Axis2 1.2
> 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
> Priority: Minor
>
> 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