axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TRANSPORTS-42) Axis2 JMS transport violates W3C SOAP over JMS, Protocol-2038
Date Wed, 10 Aug 2011 20:57:27 GMT

     [ https://issues.apache.org/jira/browse/TRANSPORTS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Veithen resolved TRANSPORTS-42.
---------------------------------------

    Resolution: Duplicate

Same as TRANSPORTS-43.

> Axis2 JMS transport violates W3C SOAP over JMS, Protocol-2038
> -------------------------------------------------------------
>
>                 Key: TRANSPORTS-42
>                 URL: https://issues.apache.org/jira/browse/TRANSPORTS-42
>             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