[jira] Commented: (SM-745) Allow usage of other JMS providers than ActiveMQ
[ https://issues.apache.org/activemq/browse/SM-745?page=comments#action_37542 ] Guillaume Nodet commented on SM-745: I agree with the common shared class. Another thing which is specific to ActiveMQ, is the fact that queues are created dynamically. The jms / jca flows uses lots of different destinations ... and ActiveMQ does not need them to be created through an admin console. 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.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
[jira] Commented: (SM-745) Allow usage of other JMS providers than ActiveMQ
[ https://issues.apache.org/activemq/browse/SM-745?page=comments#action_37548 ] Christian Schneider commented on SM-745: Dynamic creation of queues is also possible in Tibco EMS so we should have no problem with this. I only wonder how security is achieved with dynamic queues. As far as I know everyone can listen and write to a dynamic queue. Can you tell me how the security in servicemix works. I have seen the authorization map is used to authorize users. But I have not yet understood how the authentication works. I know that you can use username/password to access the JMS server but how is this user token transported to the destination? Do I have to do anything special for Tibco EMS to achieve good authentication? 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.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
[jira] Commented: (SM-745) Allow usage of other JMS providers than ActiveMQ
[ 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
[jira] Commented: (SM-745) Allow usage of other JMS providers than ActiveMQ
[ https://issues.apache.org/activemq/browse/SM-745?page=comments#action_37429 ] Guillaume Nodet commented on SM-745: The main problem will come from the discovery mechanism. Currently, the jms / jca flow uses the ActiveMQ feature called Advisory Topics. See http://www.activemq.org/site/advisory-message.html This feature is used so that a new node in the cluster will be detected by receiving a message in onAdvisoryMessage method. This one will send messages to broadcast its internal activated endpoints. This will need to be rewritten to use standard topics. 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 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