I have just checked in a small amount of code to allow multiple flows to be defined in ServiceMix.
This is only the first step and not much tested.
The next one is to enhance the DefaultFlowChooser (which implements the simple interface
https://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/FlowChooser.java)
to select the flow based on the needed QoS for a given exchange and the capabilities of the flow.

QoS to be used are
   * transactional : if the ME is enlisted in the current XA transaction
   * persistent : if the ME should be persisted
* synchronous : if the ME has been sent synchronously (the jca flow can not handle such cases)
   * clustered : if the endpoint is remote (or local + remote)

The last point will need http://jira.activemq.org/jira/browse/SM-149 to be fixed.

Cheers,
Guillaume Nodet

Reply via email to