D
dbeavon
Guest
Jboss is redhat's distribution of apache active MQ (with apache artemis as the broker). They are beginning to adopt a wire protocol called qpid. And they ship a jms client now that is built on qpid (once again, a redistribution of apache's "qpid-jms" which you can find here: https://qpid.apache.org/releases/qpid-jms-0.22.0/index.html ) I almost got this "qpid-jms" stuff working with OE 11.6 on Java 1.7. But the problem I am running into is that OE assumes there will be a method on the ConnectionFactory called "SetBrokerURL". But there isn't a method by that name on the qpid-jms connection factory (JmsConnectionFactory). Here is the error: java.lang.Exception: org.apache.qpid.jms.JmsConnectionFactory class file not men tioned correctly: java.lang.NoSuchMethodException: org.apache.qpid.jms.JmsConnec tionFactory.setBrokerURL(java.lang.String) It would be nice to know what the recommendation from Progress is for this situation. I think the "SetBrokerURL" was common for method name for the other JMS connection factories but not an *actual* part of the JMS standard. Instead of SetBrokerURL, the "qpid-jms" client appears to have a similar method called "setRemoteURI". Please let me know what I should do. I suppose I can downgrade to the old openwire-based activemq jms client because it still seems to work; but it is not included anymore with latest JBOSS AMQ downloads so I'm going way out on a limb to keep using it. Perhaps Progress needs to do a more thorough job of allowing a variety of JMS clients. I think there are only three that are listed in the whitepaper of "generic" jms options. Or better yet, please consider adopting qpid messaging which is a lower level protocol (not simply an API)... The "generic jms" approach is obviously not generic enough for the use of the "qpid-jms" API from Apache.
Continue reading...
Continue reading...