The reason is that JMS is the standard API for doing messaging in Java. Java messaging developers are used to JMS and companies have invested in JMS. Adding a new Java API is not desirable. Yes the JMS api is basically a wrapper on AMQP but an essential wrapper for Java developers.
William ----- Original Message ----- From: Adam Crain <[email protected]> To: [email protected] <[email protected]> Sent: Tue Mar 16 00:21:25 2010 Subject: java amqp api vs. jms api This is a generic question for the qpid development folks... There seems to be two APIs available for java clients: direct amqp api and a JMS api However, only the JMS api is touted on the website. Why is the direct amqp api so underdocumented as compared to JMS? They only way one can really figure out how to use it is to look the amqp examples in: qpid/java/client/example/src/main/java/org/apache/qpid/example/amqpexamp le/ I can only assume that the JMS api is a wrapper around the core amqp library itself (i.e. a mapping only) JMS adds a lot of conceptual overhead that takes you further away from the amqp model... Will the direct amqp library always be supported / are there plans to provide better documentation for the direct API? Thanks! Adam Adam Crain Manager of R&D Plymouth Systems, Inc. 919-428-1002 --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
