2008/5/7 Shahbaz Chaudhary <[EMAIL PROTECTED]>: > Hi, I also started testing with the QPid version of the stack (rather > than the Red hat mrg) because Qpid has a non-jms Java api.
On trunk (i.e. not yet a released version) there is a non-JMS low level API. > I was hoping to avoid JMS entirely, it sounds like the standard and the > expected practice is actually to use JMS for java based projects rather > than the AMQP specific api? So far, we have found that almost all our users want a JMS API since most people are either migrating from another JMS product or are familiar with JMS due to its ubiquity. Things like Mule or Spring work out of the box with Qpid for example because it is JMS compliant. However, it may be that some people want to interact directly at the protocol level and that was the motivation for having another API. I would be very interested to know your reasons for wanting to avoid JMS and also, if you can share it, what your use case is. This is so that we can make sure we address all your requirements in the next release(s). The people who have worked on the low level API can also perhaps help out here. Thanks, Robert
