axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sadeep Jayasumana (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TRANSPORTS-43) Axis2 JMS transport violates W3C SOAP over JMS, Protocol-2038
Date Tue, 12 Jul 2011 09:19:00 GMT
Axis2 JMS transport violates W3C SOAP over JMS, Protocol-2038
-------------------------------------------------------------

                 Key: TRANSPORTS-43
                 URL: https://issues.apache.org/jira/browse/TRANSPORTS-43
             Project: Axis2 Transports
          Issue Type: Improvement
          Components: JMS
            Reporter: Sadeep Jayasumana


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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message