[
http://jira.jboss.com/jira/browse/JBESB-656?page=comments#action_12367842 ]
Daniel Bevenius commented on JBESB-656:
---------------------------------------
Could we name the JMSMessageID to org.jboss.soa.esb.message.transport.jms.messageID, or
simply let it be named JMSMessageID?
If we also pass along the JMSCorrelationID with the ESB Message object later there will be
confusion about which is which.
The reason for this is that an application can set the JMSCorrelationID to an application
specific string and it does not have to involve the JMSMessageID.
JMSCorrelationID pulled from message body when it should be the
header
----------------------------------------------------------------------
Key: JBESB-656
URL:
http://jira.jboss.com/jira/browse/JBESB-656
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Mark Little
Priority: Critical
Fix For: 4.2 Milestone Release 3
if (message.getBody().get("MessageId")!=null) {
oMsg.setJMSCorrelationID((String)message.getBody().get("MessageId"));
}
Does not make sense, because the MessageId is from the EPR, which is within the header.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira