You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Trevor Pounds (JIRA)" <ji...@apache.org> on 2008/10/03 18:25:52 UTC

[jira] Commented: (SMX4NMR-25) JMS flow

    [ https://issues.apache.org/activemq/browse/SMX4NMR-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46163#action_46163 ] 

Trevor Pounds commented on SMX4NMR-25:
--------------------------------------

I'm interested to know what drawbacks you are referring to with JMSFlow?  The only alternative is to use explicit clustering with another technology such as ActiveMQ with replyTo destinations.  I find that this provides better performance and more control over the QOS (i.e. transaction, time to live, etc), but requires you to explicitly configure additional binding components.  What distributed topologies do you recommend for one-way and two-way MEPs?

> JMS flow
> --------
>
>                 Key: SMX4NMR-25
>                 URL: https://issues.apache.org/activemq/browse/SMX4NMR-25
>             Project: ServiceMix NMR
>          Issue Type: New Feature
>            Reporter: Guillaume Nodet
>            Assignee: Rob Davies
>
> Implement a JMS / JCA flow.  Note that the JMS flow in 3.x is not really reliable and does not support redelivery / rollback / transactions.

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