[
https://issues.apache.org/activemq/browse/SM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated SM-745:
-------------------------------
Component/s: servicemix-core
Fix Version/s: 3.2
Assignee: Guillaume Nodet
Issue Type: New Feature (was: Improvement)
Summary: Allow using Tibco for the JMSFlow (was: Allow usage of
other JMS providers than ActiveMQ)
> Allow using Tibco for the JMSFlow
> ---------------------------------
>
> Key: SM-745
> URL: https://issues.apache.org/activemq/browse/SM-745
> Project: ServiceMix
> Issue Type: New Feature
> Components: servicemix-core
> Affects Versions: 3.0.1
> Reporter: Christian Schneider
> Assigned To: Guillaume Nodet
> Fix For: 3.2
>
> Attachments: jmsflow.patch, jmsflow.patch, jmsflow2.patch,
> jmsflow3.patch, jmsFlowActiveMQandTibco.zip
>
>
> JMSFlow and JCA flow are too tightly bound to ActiveMQ. Instead of ActiveMQ
> specific classes jms Interfaces should be used where possible.
> I have attached a patch that replaces ActiveMQConnection and
> ActiveMQConnectionFactory by the jms equivalents.
> There is one possible issue with my patch. The getConnectionFactory now
> returns a ConnectionFactory instead of a ActiveMQConnectionFactory. I don´t
> know if any other part of the sources depends on the specific class.
> My patch is of course only the first step. The next could be having a
> specific subclass JMSFlowActiveMQ that does all stuff that is ActiveMQ
> specific.
> I will deliver a second patch for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
