[AXIS2-4025] Using JMSMessageID as correlationID for JMS messages

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 1.4
• Component/s: JMS transport
• Environment: OS: Windows XP Pro 2002 Service Pack 2
• Assignee: Asankha Chamath Perera
• Reporter: Cathal Callaghan
• Created: 10/Sep/08 10:30
• Updated: 10/May/13 10:20
• Resolved: 27/Feb/09 02:25

Description

The correlationID solution currently in place in Axis2 version 1.4 does not work.

Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.

Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.

I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.

Thanks,
Cathal