You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/10/05 16:42:23 UTC

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

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

James Strachan commented on CAMEL-126:
--------------------------------------

Sorry this issue fell through the cracks. I tried applying the patch and got compile errors in the StreamResequencer; not yet sure its that trunk has moved on since the patch was created or if its an IDEA bug applying the patch...



> 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, 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.