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 "Sadeep Jayasumana (JIRA)" <ji...@apache.org> on 2011/07/12 11:19:00 UTC
[jira] [Created] (TRANSPORTS-43) Axis2 JMS transport violates W3C
SOAP over JMS, Protocol-2038
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
[jira] [Updated] (TRANSPORTS-43) Axis2 JMS transport violates W3C
SOAP over JMS, Protocol-2038
Posted by "Sadeep Jayasumana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sadeep Jayasumana updated TRANSPORTS-43:
----------------------------------------
Attachment: TRANSPORTS-43.patch
Attaching the patch. Please review and commit.
> 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
> 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.
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
[jira] [Updated] (TRANSPORTS-43) Axis2 JMS transport violates W3C
SOAP over JMS, Protocol-2038
Posted by "Sagara Gunathunga (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sagara Gunathunga updated TRANSPORTS-43:
-----------------------------------------
Fix Version/s: 1.7.0
> 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
> Fix For: 1.7.0
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Resolved] (TRANSPORTS-43) Axis2 JMS transport violates W3C
SOAP over JMS, Protocol-2038
Posted by "Sagara Gunathunga (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sagara Gunathunga resolved TRANSPORTS-43.
------------------------------------------
Resolution: Fixed
Patch available on r1294650
> 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
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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