camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-136) resequencer should support an optional Expression/Comparator to determine if the two messages belong to the same set (in which case should they be reordered)
Date Fri, 02 Nov 2007 17:48:26 GMT

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

James Strachan updated CAMEL-136:
---------------------------------

    Assignee:     (was: James Strachan)

> resequencer should support an optional Expression/Comparator to determine if the two
messages belong to the same set (in which case should they be reordered) 
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-136
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-136
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: James Strachan
>            Priority: Minor
>
> e.g. to support reordering according to the JMSXGroupID / JMSXGroupSeq headers we only
reorder messages for the same value of JMSXGroupID if the sequence numbers are out of range.
> For ActiveMQ we generally only reorder messages for the same Destination and ProducerId
but differing ProducerSequenceId.
> So in pseudocode its 
> {code}
> if (groupComparator.compare(firstMessage, secondMessage) == 0) {
>   if (messageComparator.compare(firstMessage, secondMessage) > 0) {
>     // lets swap the messages
>   }
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message