servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SM-745) Allow using Tibco for the JMSFlow
Date Thu, 08 Mar 2007 14:03:21 GMT

     [ https://issues.apache.org/activemq/browse/SM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Nodet resolved SM-745.
--------------------------------

    Resolution: Fixed

Thanks a lot for this patch Christian !
I have just slightly modified it to keep the old class name for ActiveMQ and to use reflection
for Tibco, 
as the tibco jars are not public.
Could you check it still works for you ?

Author: gnodet
Date: Thu Mar  8 05:59:26 2007
New Revision: 516044

URL: http://svn.apache.org/viewvc?view=rev&rev=516044
Log:
SM-745: Allow using Tibco for the JMSFlow

Added:
   incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/jms/AbstractJMSFlow.java
  (with props)
   incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/jms/JMSFlowTibco.java
  (with props)
Modified:
   incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/nmr/flow/jms/JMSFlow.java



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


Mime
View raw message