How can the remote publish/subscribe use case work? Aren JMS implementations incompatible?
One issue that usually comes up with connecting different JMS implementations (even without Kaazing Enterprise Gateway) is the lack of a JMS wire protocol. Clearly this results in incompatibilities with JMS vendor products. For example, the publisher uses Apache ActiveMQ and the remote subscribers use Tibco EMS. You can address this issue with our JMS-Stomp and Stomp-JMS protocol converters.
Related Questions
- Does the specification require that all JMS implementations provide both point-to-point and publish/subscribe messaging?
- How do I use multiple Kaazing WebSocket Gateways to setup a remote publish/subscribe architecture?
- How can the remote publish/subscribe use case work? Aren JMS implementations incompatible?
