[ https://issues.apache.org/activemq/browse/SM-745?page=comments#action_37445 ] Guillaume Nodet commented on SM-745: ------------------------------------
Maybe one way would be to just publish a message to a topic when a node is started. (which is what ActiveMQ does actually). The problem is mainly to discover failed nodes (and this is the main reason to use ActiveMQ advisories iirc). I was also thinking of making the jms / jca flows inherit a common base classes, as there is some commong logic in both. > Allow usage of other JMS providers than ActiveMQ > ------------------------------------------------ > > Key: SM-745 > URL: https://issues.apache.org/activemq/browse/SM-745 > Project: ServiceMix > Issue Type: Improvement > Affects Versions: 3.0.1 > Reporter: Christian Schneider > Fix For: 3.0.1 > > Attachments: jmsflow.patch, jmsflow.patch, jmsflow2.patch, > jmsflow3.patch > > > 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. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
