D
dbeavon
Guest
Thanks for the quick feedback. You left out Sonic MQ in your list of certified providers. Did you kick them off the island? You probably should, considering what they are charging for a support contract to do simple messaging. 
What can we do to get this into 11.6 service pack 4 that is supposed to be released shortly? We are a couple months away from a production upgrade to OE 11.6.4 (from OE 11.3) and we aren't likely to be using 11.7 for several years. Also, what did you change to allow for the use of Jboss? Did you write your own custom connection factories that wrap around the "real" ones? Or did you extend the jmsprovider configuration to allow us to specify the *method* names used for each of those different connection factories? Or perhaps JBoss finally agreed to add your "setBrokerURL()" method to all of their JMS client libraries? It is unfortunate that messaging/integration changes like this would require a full upgrade to the installation of OpenEdge... I understand that Progress is adopting "agile" practices for developing new versions of OpenEdge; but it really doesn't seem very "agile" at all that we can't use the Jboss qpid-jms client until after we upgrade to 11.7.1 - several years from now. This type of change (switching messaging client versions) would not be so difficult for us to make in some other ecosystems like .Net or Java. Depending on what you had to do to get Jboss up and running, we would be very open to attempting a similar thing on 11.6. Please let me know.
Continue reading...
What can we do to get this into 11.6 service pack 4 that is supposed to be released shortly? We are a couple months away from a production upgrade to OE 11.6.4 (from OE 11.3) and we aren't likely to be using 11.7 for several years. Also, what did you change to allow for the use of Jboss? Did you write your own custom connection factories that wrap around the "real" ones? Or did you extend the jmsprovider configuration to allow us to specify the *method* names used for each of those different connection factories? Or perhaps JBoss finally agreed to add your "setBrokerURL()" method to all of their JMS client libraries? It is unfortunate that messaging/integration changes like this would require a full upgrade to the installation of OpenEdge... I understand that Progress is adopting "agile" practices for developing new versions of OpenEdge; but it really doesn't seem very "agile" at all that we can't use the Jboss qpid-jms client until after we upgrade to 11.7.1 - several years from now. This type of change (switching messaging client versions) would not be so difficult for us to make in some other ecosystems like .Net or Java. Depending on what you had to do to get Jboss up and running, we would be very open to attempting a similar thing on 11.6. Please let me know.Continue reading...