[jira] Updated: (CAMEL-126) provide a synchronous dispatch to the stream based resequencer for easier transaction support

["Martin Krasser (JIRA)" <ji...@apache.org>]

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

Martin Krasser updated CAMEL-126:
---------------------------------

    Attachment: camel-core.patch-update

I could not reproduce the compile errors when using Eclipse for applying the patch. There was only a minor conflict within the javadocs. However, I re-created a patch for the latest trunk (attachment: camel-core.patch-update) to remove these minor conflicts. Also, the path names in the patch are now relative to the camel-core module.


> provide a synchronous dispatch to the stream based resequencer for easier transaction support
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-126
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-126
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: James Strachan
>         Attachments: camel-core.patch, camel-core.patch-update, resequencer-docu.txt
>
>
> Currently the ResequencerEngine uses a Queue for asynchronous delivery of the messages. We might want to provide a Processor instead; so we could if we prefer use synchronous dispatch. 
> e.g. to be able to use a single thread and JMS transaction on a single JMS session (to avoid XA etc) to do 
> * consume messages
> * reorder
> * send them on to another destination
> * jms session.commit()
> As far as I understand it, the current async mechanism will make transactional re-sequencing harder right?

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