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

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46213#action_46213 ] 

Claus Ibsen commented on CAMEL-126:
-----------------------------------

Martin, I think the Config object could be a shared object for all kind that uses the BatchProcessor
- resequencer
- aggregator

So we should consider having a shared config object for this in Camel 2.0. But I like it. Then its possible to have Java DSL and use Spring XML for dynamic values, where they are easier to spot and change.

> 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
>            Assignee: Gert Vanthienen
>             Fix For: 1.5.0
>
>         Attachments: camel-core.patch, camel-core.patch-update, camel-core.patch-update-2.zip, camel-core.patch-update-3, 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.