* is language-neutral: it will allow the writing of software libraries for communicating with JMS providers in any language that has libraries for communicating over HTTP.
* is RESTful: it provides a RESTful equivalent to all of the non-optional portions of the JMS API including
o registration of resources administered by the messaging provider
o connection and session management
o sending and receipt of all types of JMS message
Implementation overview
HJB
*
is deployed as a servlet (HJBServlet), that can run on any compliant Servlet specification 2.4 container.
*
will work with any messaging vendor that provides a JMS interface.
*
aims to do one thing well. Its role is to act as an HTTP gateway server for JMS resources. Other potentially useful features are deliberately excluded, e.g,
o HTTP session management
o authentication and authorization