As there is a HTTP/HTTPS ActiveMQ Transport protocol, you can already use the APiMan Gateway ;-) Nevertheless, I'm not sure that Apiman could offer real added value for such architecture design as Authentication (Basic, LDAP, JDBC) & Authorization is already designed into ActiveMQ (JAASAuthenticationPlugin & JAASAuthorization plugin) and I don't think that the cache, quota or rate policy are meaningful for JMS-HTTP transfer ... ----- Mail original ----- De: "Eric Wittmann" <eric.wittmann(a)redhat.com&gt; À: "Anton Hughes" <ah(a)tradeworks.io&gt;, "apiman-user" <apiman-user(a)lists.jboss.org&gt; Envoyé: Mercredi 27 Janvier 2016 20:47:58 Objet: Re: [Apiman-user] ApiMan and ActiveMQ Hi Anton. Support for protocols other than http/s is on the roadmap, although it's not coming *soon*. The gateway is absolutely designed to support other protocols. The input/output beans for the gateway attempt to be protocol agnostic, so hopefully we are reasonably well positioned to implement support for something like activemq. I don't have much experience with JMS or activemq, so I don't know offhand how we can insert the gateway in between the client and the API. But I'm sure there must be a way! If you have ideas or want to contribute in this area - we'd be thrilled to provide guidance. Otherwise you'll have to wait until the feature reaches critical priority. :) -Eric On 1/27/2016 1:02 PM, Anton Hughes wrote: _______________________________________________ Apiman-user mailing list Apiman-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/apiman-user