1 of 1 people found this helpful
I would suggest to keep the foreign JMS broker outside JBoss Fuse, and just let JBoss Fuse integrate with that broker as a standard JMS client.
Many other JMS brokers are heavy-weight and not designed to be embedded inside another container (eg such as the two brokers you mention).
You would need to use the minimal JBoss Fuse distribution which does not come with AMQ out of the box.
No JBoss Fuse does not do that unless you use the legacy JBI NMR, or setup AMQ for clustering. So out of the box it does not.
Thank you Claus!
Do you think you can help a bit more with a few pointers on how to configure JBoss Fuse as a client? What I need is an "JMS endpoint" in/out which will actually talk to an foreign JMS broker.
I looked in documentation, but I can't find any help on how to configure a custom JMS Endpoint. If you can help or at least point me to such sample, it would be of great help.
Also, if I have jars for a foreign JMS broker which are NOT a OSGI bundle, do I need to create a bundle first? (help of that also appreciated), or I can deploy the libs without having to create any OSGI bundles?
Also, if there was a way to reconfigure the default JMS Broker to be different instead of A-MQ? Is that a configuration change or would require code changes to JBOSS FUSE?
I can perfectly live with just a custom JMS Endpoint without getting rid of A-MQ.
You can use the Camel JMS component as client to any JMS broker
And you need to install the foreign JMS client as an OSGi bundle. You can use wrap to install a plain JAR as OSGi bundle. Though there can be some situations where that wont work.