My company long time ago decided to expose a JMS queue to customers in order to exchange data. We're in the process to migrate application server and we have to update all the client libraries. So we thought to expose a more "standard" interface.
We're looking to a simple way to expose a JMS queue through a standard SOAP or REST protocol. It's not SOAP over JMS, it would rather be the opposite "JMS over SOAP".
Seem that ActiveMQ(Artemis) has a REST protocol. It is a viable solution for us since we're migrating to Wildfly 10, but it's a bit complicated (see for instance posting a message requires 2 calls: see Posting Messages), and it is ActiveMQ-specific. We have to implement it again for the old Weblogic servers.
The solution we're searching for should have the same reliability of JMS, in respect of the CAP theorem (providing message deduplication on send, and idempotent reads). Any suggestion?
As per my understanding this is anti pattern where we want to combine both REST/Webservice and JMS or creating hybrid model.
JMS has strong reliability,performance,monitoring,exception handling, async response and guaranteed delivery in compared to REST/Webservice. The only weaker point of JMS is external firewall access that can be overcomed by creating hybrid model. Restful JMS. http://activemq.apache.org/rest.html http://activemq.apache.org/activesoap.html
Thanks