[
https://issues.apache.org/jira/browse/AXIS2-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved TRANSPORTS-43 to AXIS2-5561:
--------------------------------------------------
Component/s: (was: JMS)
JMS
Fix Version/s: (was: 1.7.0)
1.6.3
1.7.0
Key: AXIS2-5561 (was: TRANSPORTS-43)
Project: Axis2 (was: Axis2 Transports)
> Axis2 JMS transport violates W3C SOAP over JMS, Protocol-2038
> -------------------------------------------------------------
>
> Key: AXIS2-5561
> URL: https://issues.apache.org/jira/browse/AXIS2-5561
> Project: Axis2
> Issue Type: Improvement
> Components: JMS
> Reporter: Sadeep Jayasumana
> Fix For: 1.7.0, 1.6.3
>
> Attachments: TRANSPORTS-43.patch
>
>
> Protocol-2038 states
> <Quote>
> If the JMSCorrelationID is set in the request message, then the
> JMSCorrelationID header field in the response message MUST be set to the same
> value as the JMSCorrelationID header field in the request message. If the
> JMSCorrelationID header field is not set in the request message, then the
> JMSCorrelationID header field in the response message MUST be set to the
> value of the JMSMessageID header in the request message.
> </Quote>.
> However, current implementation of Axis2 JMS transport always copies the
> JMSMessageID of the request message as the JMSCorrelationID of the response
> message, even when JMSCorrelationID is present.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
