[ http://jira.activemq.org/jira//browse/SM-366?page=all ]
Guillaume Nodet resolved SM-366:
--------------------------------
Assign To: Guillaume Nodet
Resolution: Fixed
Fix Version: 3.0-M1
Author: gnodet
Date: Thu Mar 23 08:16:40 2006
New Revision: 388198
URL: http://svn.apache.org/viewcvs?rev=388198&view=rev
Log:
SM-366: jms and jca flow should not use the same queues
Also improve the jca flow to auto-detect a TransactionContextManager from the
spring context (if any)
Modified:
incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/jca/JCAFlow.java
incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/jms/JMSFlow.java
> jms and jca flow should not use the same queues
> -----------------------------------------------
>
> Key: SM-366
> URL: http://jira.activemq.org/jira//browse/SM-366
> Project: ServiceMix
> Type: Improvement
> Components: servicemix-core
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 3.0-M1
>
>
> As they can now be chosen based on QoS (the jca flow supports transactions),
> they should not use the same queues, so that the QoS will be kept.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
