camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Krasser (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-126) provide a synchronous dispatch to the stream based resequencer for easier transaction support
Date Fri, 31 Aug 2007 09:15:22 GMT

     [ 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

Attached is a patch for synchronous delivery of messages. Messages are now consumed from an
endpoint and sent to the next processor by a single thread. Further unit tests are included
as well.


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


Mime
View raw message