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 "Valery Ushakov (JIRA)" <ji...@apache.org> on 2010/07/01 00:26:52 UTC
[jira] Created: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
-----------------------------------------------------------------
Key: AXIS2-4760
URL: https://issues.apache.org/jira/browse/AXIS2-4760
Project: Axis2
Issue Type: Bug
Affects Versions: 1.5.1
Environment: axis2-1.5.1
Reporter: Valery Ushakov
This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
Install axis2 and start the default standalone server that provides version service.
Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
1) wsa:Action header is present
2) SOAP action parameter is present both
2a) inside start-info parameter (standard location) and
2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
Content-Type: multipart/related;
boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
type="application/xop+xml";
action="urn:getVersion";
start-info="application/soap+xml; action=\"urn:getVersion\""
Content-Length: 487
--B6331265-36EA-70D4-9375-0FF743A48AA2
Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
<S12:Envelope
xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<S12:Header>
<wsa:Action>urn:getVersion</wsa:Action>
<wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
</S12:Header>
<S12:Body/>
</S12:Envelope>
--B6331265-36EA-70D4-9375-0FF743A48AA2--
Normal getVersionResponse message is returned.
Now change the order of action and start-info parameters in the message content-type so that it looks like:
Content-Type: multipart/related;
boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
type="application/xop+xml";
start-info="application/soap+xml; action=\"urn:getVersion\"";
action="urn:getVersion"
Axis2 replies with a fault (prettified for readability):
HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>
soapenv:Sender
</soapenv:Value>
<soapenv:Subcode>
<soapenv:Value
xmlns:wsa="http://www.w3.org/2005/08/addressing">
wsa:InvalidAddressingHeader
</soapenv:Value>
<soapenv:Subcode>
<soapenv:Value
xmlns:wsa="http://www.w3.org/2005/08/addressing">
wsa:ActionMismatch
</soapenv:Value>
</soapenv:Subcode>
</soapenv:Subcode>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">
Aheader representing a Message Addressing Property is not
valid and the message cannot be processed
</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail>
<wsa:ProblemHeaderQName
xmlns:wsa="http://www.w3.org/2005/08/addressing">
wsa:Action
</wsa:ProblemHeaderQName>
</soapenv:Detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4760.
------------------------------------
Resolution: Incomplete
Before investigating this issue further we need to determine if the root cause is one of the known issues in Geronimo's JavaMail/JAF implementation or if there is an issue in Axiom/Axis2. Therefore we need to know what JavaMail/JAF implementation is used by the Axis2 deployment.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887242#action_12887242 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
There are actually multiple issues related to HTTPTransportUtils#initializeMessageContext:
1. The HTTPTransportUtils, TransportUtils and BuilderUtils contain multiple methods that implement Content-Type decoding logic. See e.g. TransportUtils#processContentTypeForAction, TransportUtils#getSOAPNamespaceFromContentType and BuilderUtils#getCharSetEncoding. There is much code duplication (e.g. the logic to process quoted values) and the decoding logic is implemented with very different degrees of conformance to the specs. Probably it would be much better to create a javax.mail.internet.ContentType object once from the Content-Type value and extract all necessary information from that object (javax.mail.internet.ContentType is known to parse the Content-Type value correctly). This may even perform better, considering the repeated usage of String#indexOf, JavaUtils#indexOfIgnoreCase, String#substring and String#trim in these methods.
2. The code in HTTPTransportUtils#initializeMessageContext is difficult to understand. E.g. to most people it will not be clear at first glance that the condition contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) > -1 actually catches plain SOAP 1.2 messages as well as MTOM messages.
3. HTTPTransportUtils#initializeMessageContext contains content type specific logic. The right place for this logic would be the corresponding org.apache.axis2.builder.Builder implementation.
4. HTTPTransportUtils#initializeMessageContext is used only in the HTTP transport. It is not clear why the logic that extracts the SOAP 1.2 action would not apply in the same way to the JMS and mail transports (both of which support Content-Type headers).
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887242#action_12887242 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
There are actually multiple issues related to HTTPTransportUtils#initializeMessageContext:
1. The HTTPTransportUtils, TransportUtils and BuilderUtils contain multiple methods that implement Content-Type decoding logic. See e.g. TransportUtils#processContentTypeForAction, TransportUtils#getSOAPNamespaceFromContentType and BuilderUtils#getCharSetEncoding. There is much code duplication (e.g. the logic to process quoted values) and the decoding logic is implemented with very different degrees of conformance to the specs. Probably it would be much better to create a javax.mail.internet.ContentType object once from the Content-Type value and extract all necessary information from that object (javax.mail.internet.ContentType is known to parse the Content-Type value correctly). This may even perform better, considering the repeated usage of String#indexOf, JavaUtils#indexOfIgnoreCase, String#substring and String#trim in these methods.
2. The code in HTTPTransportUtils#initializeMessageContext is difficult to understand. E.g. to most people it will not be clear at first glance that the condition contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) > -1 actually catches plain SOAP 1.2 messages as well as MTOM messages.
3. HTTPTransportUtils#initializeMessageContext contains content type specific logic. The right place for this logic would be the corresponding org.apache.axis2.builder.Builder implementation.
4. HTTPTransportUtils#initializeMessageContext is used only in the HTTP transport. It is not clear why the logic that extracts the SOAP 1.2 action would not apply in the same way to the JMS and mail transports (both of which support Content-Type headers).
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887223#action_12887223 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Looks like HTTPTransportUtils#initializeMessageContext doesn't decode the Content-Type header properly.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4760.
------------------------------------
Resolution: Incomplete
Before investigating this issue further we need to determine if the root cause is one of the known issues in Geronimo's JavaMail/JAF implementation or if there is an issue in Axiom/Axis2. Therefore we need to know what JavaMail/JAF implementation is used by the Axis2 deployment.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887242#action_12887242 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
There are actually multiple issues related to HTTPTransportUtils#initializeMessageContext:
1. The HTTPTransportUtils, TransportUtils and BuilderUtils contain multiple methods that implement Content-Type decoding logic. See e.g. TransportUtils#processContentTypeForAction, TransportUtils#getSOAPNamespaceFromContentType and BuilderUtils#getCharSetEncoding. There is much code duplication (e.g. the logic to process quoted values) and the decoding logic is implemented with very different degrees of conformance to the specs. Probably it would be much better to create a javax.mail.internet.ContentType object once from the Content-Type value and extract all necessary information from that object (javax.mail.internet.ContentType is known to parse the Content-Type value correctly). This may even perform better, considering the repeated usage of String#indexOf, JavaUtils#indexOfIgnoreCase, String#substring and String#trim in these methods.
2. The code in HTTPTransportUtils#initializeMessageContext is difficult to understand. E.g. to most people it will not be clear at first glance that the condition contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) > -1 actually catches plain SOAP 1.2 messages as well as MTOM messages.
3. HTTPTransportUtils#initializeMessageContext contains content type specific logic. The right place for this logic would be the corresponding org.apache.axis2.builder.Builder implementation.
4. HTTPTransportUtils#initializeMessageContext is used only in the HTTP transport. It is not clear why the logic that extracts the SOAP 1.2 action would not apply in the same way to the JMS and mail transports (both of which support Content-Type headers).
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4760:
--------------------------------------
Assignee: Andreas Veithen
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4760.
------------------------------------
Resolution: Incomplete
Before investigating this issue further we need to determine if the root cause is one of the known issues in Geronimo's JavaMail/JAF implementation or if there is an issue in Axiom/Axis2. Therefore we need to know what JavaMail/JAF implementation is used by the Axis2 deployment.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4760:
--------------------------------------
Assignee: Andreas Veithen
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886039#action_12886039 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Please look for JARs called mail-x.y.z.jar or geronimo-javamail_1.4_spec-x.y.z.jar (for JavaMail) and activation-x.y.z or geronimo-activation_a.b_spec-x.y.z.jar (for JAF). If you are running Axis2 in an application server you also need to check first if the server runtime exposes the JavaMail and JAF APIs.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887223#action_12887223 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Looks like HTTPTransportUtils#initializeMessageContext doesn't decode the Content-Type header properly.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887242#action_12887242 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
There are actually multiple issues related to HTTPTransportUtils#initializeMessageContext:
1. The HTTPTransportUtils, TransportUtils and BuilderUtils contain multiple methods that implement Content-Type decoding logic. See e.g. TransportUtils#processContentTypeForAction, TransportUtils#getSOAPNamespaceFromContentType and BuilderUtils#getCharSetEncoding. There is much code duplication (e.g. the logic to process quoted values) and the decoding logic is implemented with very different degrees of conformance to the specs. Probably it would be much better to create a javax.mail.internet.ContentType object once from the Content-Type value and extract all necessary information from that object (javax.mail.internet.ContentType is known to parse the Content-Type value correctly). This may even perform better, considering the repeated usage of String#indexOf, JavaUtils#indexOfIgnoreCase, String#substring and String#trim in these methods.
2. The code in HTTPTransportUtils#initializeMessageContext is difficult to understand. E.g. to most people it will not be clear at first glance that the condition contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) > -1 actually catches plain SOAP 1.2 messages as well as MTOM messages.
3. HTTPTransportUtils#initializeMessageContext contains content type specific logic. The right place for this logic would be the corresponding org.apache.axis2.builder.Builder implementation.
4. HTTPTransportUtils#initializeMessageContext is used only in the HTTP transport. It is not clear why the logic that extracts the SOAP 1.2 action would not apply in the same way to the JMS and mail transports (both of which support Content-Type headers).
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887223#action_12887223 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Looks like HTTPTransportUtils#initializeMessageContext doesn't decode the Content-Type header properly.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887223#action_12887223 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Looks like HTTPTransportUtils#initializeMessageContext doesn't decode the Content-Type header properly.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886039#action_12886039 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Please look for JARs called mail-x.y.z.jar or geronimo-javamail_1.4_spec-x.y.z.jar (for JavaMail) and activation-x.y.z or geronimo-activation_a.b_spec-x.y.z.jar (for JAF). If you are running Axis2 in an application server you also need to check first if the server runtime exposes the JavaMail and JAF APIs.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884922#action_12884922 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
Test messages were not generated by JavaMail.
I used JDK 1.6.0_19-b04 linux 64-bit to run axis2 1.5.1 for this test. Both are straight default installs.
I have no idea about internal dependencies of axis2 and where do they come from, so I cannot provide meaningful answer, sorry... :(
I'm not actually using axis2. My code needs to talk MTOM (I use private MIME library) and some people use it against axis2, and axis2 MTOM messages accepted/generated by axis2 have number of quirks in its use of MIME that make life somewhat painful.
Another example would be https://issues.apache.org/jira/browse/AXIS2-4037 I filed quite a while ago (never got any feedback on that one). I had to add a kludge to the MIME library I use to accept non-conformant content-id headers generated by axis2.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884922#action_12884922 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
Test messages were not generated by JavaMail.
I used JDK 1.6.0_19-b04 linux 64-bit to run axis2 1.5.1 for this test. Both are straight default installs.
I have no idea about internal dependencies of axis2 and where do they come from, so I cannot provide meaningful answer, sorry... :(
I'm not actually using axis2. My code needs to talk MTOM (I use private MIME library) and some people use it against axis2, and axis2 MTOM messages accepted/generated by axis2 have number of quirks in its use of MIME that make life somewhat painful.
Another example would be https://issues.apache.org/jira/browse/AXIS2-4037 I filed quite a while ago (never got any feedback on that one). I had to add a kludge to the MIME library I use to accept non-conformant content-id headers generated by axis2.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884905#action_12884905 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Which JavaMail implementation and version do you use?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884905#action_12884905 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Which JavaMail implementation and version do you use?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884905#action_12884905 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Which JavaMail implementation and version do you use?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887242#action_12887242 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
There are actually multiple issues related to HTTPTransportUtils#initializeMessageContext:
1. The HTTPTransportUtils, TransportUtils and BuilderUtils contain multiple methods that implement Content-Type decoding logic. See e.g. TransportUtils#processContentTypeForAction, TransportUtils#getSOAPNamespaceFromContentType and BuilderUtils#getCharSetEncoding. There is much code duplication (e.g. the logic to process quoted values) and the decoding logic is implemented with very different degrees of conformance to the specs. Probably it would be much better to create a javax.mail.internet.ContentType object once from the Content-Type value and extract all necessary information from that object (javax.mail.internet.ContentType is known to parse the Content-Type value correctly). This may even perform better, considering the repeated usage of String#indexOf, JavaUtils#indexOfIgnoreCase, String#substring and String#trim in these methods.
2. The code in HTTPTransportUtils#initializeMessageContext is difficult to understand. E.g. to most people it will not be clear at first glance that the condition contentType.indexOf(SOAP12Constants.SOAP_12_CONTENT_TYPE) > -1 actually catches plain SOAP 1.2 messages as well as MTOM messages.
3. HTTPTransportUtils#initializeMessageContext contains content type specific logic. The right place for this logic would be the corresponding org.apache.axis2.builder.Builder implementation.
4. HTTPTransportUtils#initializeMessageContext is used only in the HTTP transport. It is not clear why the logic that extracts the SOAP 1.2 action would not apply in the same way to the JMS and mail transports (both of which support Content-Type headers).
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4760:
--------------------------------------
Assignee: Andreas Veithen
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885013#action_12885013 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
How do I tell which version is used? Or am I supposed to RTFS?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4760.
------------------------------------
Resolution: Incomplete
Before investigating this issue further we need to determine if the root cause is one of the known issues in Geronimo's JavaMail/JAF implementation or if there is an issue in Axiom/Axis2. Therefore we need to know what JavaMail/JAF implementation is used by the Axis2 deployment.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885013#action_12885013 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
How do I tell which version is used? Or am I supposed to RTFS?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886287#action_12886287 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
I'm running standalone server. axis2-1.5.1 release. It has lib/mail-1.4.jar
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4760:
--------------------------------------
Assignee: Andreas Veithen
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886039#action_12886039 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Please look for JARs called mail-x.y.z.jar or geronimo-javamail_1.4_spec-x.y.z.jar (for JavaMail) and activation-x.y.z or geronimo-activation_a.b_spec-x.y.z.jar (for JAF). If you are running Axis2 in an application server you also need to check first if the server runtime exposes the JavaMail and JAF APIs.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884905#action_12884905 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Which JavaMail implementation and version do you use?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886039#action_12886039 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Please look for JARs called mail-x.y.z.jar or geronimo-javamail_1.4_spec-x.y.z.jar (for JavaMail) and activation-x.y.z or geronimo-activation_a.b_spec-x.y.z.jar (for JAF). If you are running Axis2 in an application server you also need to check first if the server runtime exposes the JavaMail and JAF APIs.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884922#action_12884922 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
Test messages were not generated by JavaMail.
I used JDK 1.6.0_19-b04 linux 64-bit to run axis2 1.5.1 for this test. Both are straight default installs.
I have no idea about internal dependencies of axis2 and where do they come from, so I cannot provide meaningful answer, sorry... :(
I'm not actually using axis2. My code needs to talk MTOM (I use private MIME library) and some people use it against axis2, and axis2 MTOM messages accepted/generated by axis2 have number of quirks in its use of MIME that make life somewhat painful.
Another example would be https://issues.apache.org/jira/browse/AXIS2-4037 I filed quite a while ago (never got any feedback on that one). I had to add a kludge to the MIME library I use to accept non-conformant content-id headers generated by axis2.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887223#action_12887223 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Looks like HTTPTransportUtils#initializeMessageContext doesn't decode the Content-Type header properly.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885013#action_12885013 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
How do I tell which version is used? Or am I supposed to RTFS?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886287#action_12886287 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
I'm running standalone server. axis2-1.5.1 release. It has lib/mail-1.4.jar
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886287#action_12886287 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
I'm running standalone server. axis2-1.5.1 release. It has lib/mail-1.4.jar
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886287#action_12886287 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
I'm running standalone server. axis2-1.5.1 release. It has lib/mail-1.4.jar
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885013#action_12885013 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
How do I tell which version is used? Or am I supposed to RTFS?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886039#action_12886039 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Please look for JARs called mail-x.y.z.jar or geronimo-javamail_1.4_spec-x.y.z.jar (for JavaMail) and activation-x.y.z or geronimo-activation_a.b_spec-x.y.z.jar (for JAF). If you are running Axis2 in an application server you also need to check first if the server runtime exposes the JavaMail and JAF APIs.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884922#action_12884922 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
Test messages were not generated by JavaMail.
I used JDK 1.6.0_19-b04 linux 64-bit to run axis2 1.5.1 for this test. Both are straight default installs.
I have no idea about internal dependencies of axis2 and where do they come from, so I cannot provide meaningful answer, sorry... :(
I'm not actually using axis2. My code needs to talk MTOM (I use private MIME library) and some people use it against axis2, and axis2 MTOM messages accepted/generated by axis2 have number of quirks in its use of MIME that make life somewhat painful.
Another example would be https://issues.apache.org/jira/browse/AXIS2-4037 I filed quite a while ago (never got any feedback on that one). I had to add a kludge to the MIME library I use to accept non-conformant content-id headers generated by axis2.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886287#action_12886287 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
I'm running standalone server. axis2-1.5.1 release. It has lib/mail-1.4.jar
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4760:
--------------------------------------
Assignee: Andreas Veithen
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
> Assignee: Andreas Veithen
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4760.
------------------------------------
Resolution: Incomplete
Before investigating this issue further we need to determine if the root cause is one of the known issues in Geronimo's JavaMail/JAF implementation or if there is an issue in Axiom/Axis2. Therefore we need to know what JavaMail/JAF implementation is used by the Axis2 deployment.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884905#action_12884905 ]
Andreas Veithen commented on AXIS2-4760:
----------------------------------------
Which JavaMail implementation and version do you use?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884922#action_12884922 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
Test messages were not generated by JavaMail.
I used JDK 1.6.0_19-b04 linux 64-bit to run axis2 1.5.1 for this test. Both are straight default installs.
I have no idea about internal dependencies of axis2 and where do they come from, so I cannot provide meaningful answer, sorry... :(
I'm not actually using axis2. My code needs to talk MTOM (I use private MIME library) and some people use it against axis2, and axis2 MTOM messages accepted/generated by axis2 have number of quirks in its use of MIME that make life somewhat painful.
Another example would be https://issues.apache.org/jira/browse/AXIS2-4037 I filed quite a while ago (never got any feedback on that one). I had to add a kludge to the MIME library I use to accept non-conformant content-id headers generated by axis2.
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4760) Content-Type still not parsed
correctly in MTOM SOAP 1.2 messages
Posted by "Valery Ushakov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885013#action_12885013 ]
Valery Ushakov commented on AXIS2-4760:
---------------------------------------
How do I tell which version is used? Or am I supposed to RTFS?
> Content-Type still not parsed correctly in MTOM SOAP 1.2 messages
> -----------------------------------------------------------------
>
> Key: AXIS2-4760
> URL: https://issues.apache.org/jira/browse/AXIS2-4760
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: axis2-1.5.1
> Reporter: Valery Ushakov
>
> This is sort of a followup to https://issues.apache.org/jira/browse/AXIS2-4076 I guess.
> Install axis2 and start the default standalone server that provides version service.
> Send MTOM-encoded SOAP1.2 get version request, e.g. netcat something like the following (I intentionally start with the case that works). Important details to note about this message:
> 1) wsa:Action header is present
> 2) SOAP action parameter is present both
> 2a) inside start-info parameter (standard location) and
> 2b) as top-level parameter of the message Content-Type (where axis2 &co put it).
> For further info about point #2 see https://issues.apache.org/jira/browse/WSCOMMONS-290
> POST /axis2/services/Version.VersionHttpSoap12Endpoint/ HTTP/1.1
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> action="urn:getVersion";
> start-info="application/soap+xml; action=\"urn:getVersion\""
> Content-Length: 487
>
> --B6331265-36EA-70D4-9375-0FF743A48AA2
> Content-Type: application/xop+xml; type="application/soap+xml; action=\"urn:getVersion\""
>
> <S12:Envelope
> xmlns:S12="http://www.w3.org/2003/05/soap-envelope"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <S12:Header>
> <wsa:Action>urn:getVersion</wsa:Action>
> <wsa:MessageID>urn:uuid:806D8FD2D542EDCC2C1199332890651</wsa:MessageID>
> </S12:Header>
> <S12:Body/>
> </S12:Envelope>
> --B6331265-36EA-70D4-9375-0FF743A48AA2--
> Normal getVersionResponse message is returned.
> Now change the order of action and start-info parameters in the message content-type so that it looks like:
> Content-Type: multipart/related;
> boundary=B6331265-36EA-70D4-9375-0FF743A48AA2;
> type="application/xop+xml";
> start-info="application/soap+xml; action=\"urn:getVersion\"";
> action="urn:getVersion"
> Axis2 replies with a fault (prettified for readability):
> HTTP/1.1 500 A header representing a Message Addressing Property is not valid and the message cannot be processed
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>
> soapenv:Sender
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:InvalidAddressingHeader
> </soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:ActionMismatch
> </soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">
> Aheader representing a Message Addressing Property is not
> valid and the message cannot be processed
> </soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail>
> <wsa:ProblemHeaderQName
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> wsa:Action
> </wsa:ProblemHeaderQName>
> </soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> If I remove WS-A headers from the SOAP envelope then action/start-info order works, while start-info/action mode results in
> HTTP/1.1 500 The endpoint reference (EPR) for the Operation not found is 10.125.133.56/axis2/services/Version.VersionHttpSoap12Endpoint/ and the WSA Action = \"urn:getVersion\""
> So it looks like axis2 does pay attention to action parameter in start-info, but does not parse it correctly.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org