For a standalone application there is no standard way to make your code
independent of the jms provider.
You will have to provide the provider client jars at some point.
Of course you can externalize the class name in some way but you are on
your own in how to do it.
Christian
On 07.10.2014 13:31, James Green wrote:
This is a standalone Spring app with Java configuration.
On 7 October 2014 12:21, Christian Schneider <ch...@die-schneider.net>
wrote:
If you are deploying to a web container then you should refer to the
ConnectionFactory using JNDI. If you are using OSGi you can use an OSGi
service.
This way you avoid making your route bundle depend on the jms provider.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
