R
Rob Straight
Guest
SonicMQ from Aurea Software is alive and well. Sometimes when we think of support for "generic" JMS providers, we overlook SonicMQ as it adds additional value like guaranteed message delivery on top of the "generic" JMS standard. But clearly it is on our list of supported JMS vendors. We have not tested the Qpid JMS Client (we are not able to test every JMS provider in the marketplace proactively). It is based on the AMQP (Advanced Message Queuing Protocol), which specifies the wire protocol used when sending messages. It is JMS compliant, so it could/should be something that our generic JMS adapter can handle. Like other JMS providers that we have not tested but that our customers are interested in using, we will look at issues that come up and do our best to resolve them. It would be best to raise this as a bug with our Technical Support team to get this looked at "officially". A comment on "agile"- we do follow the Agile development methodology, and we do have examples where we have rolled out new capabilities rather quickly. Our customer base in general is not interested or equipped to take on a continuous stream of new features that a pure Agile methodology could supply- we heard that loud and clear when we did 3 releases in one 13-month period (11.1, 11.2 and 11.3). While we are now on a roughly annual release schedule, we can and do put enhancements into selected Service Packs as needed by our customers. In this particular case, the issue is likely to be considered a bug vs. a feature enhancement, which gives us more flexibility in resolving the issue (including the possibility of a Hot Fix if warranted by the circumstances).
Continue reading...
Continue reading...