To circle back to this question for historical reasons and those searching
the thread, the actual binding of these is transparrent. When you create a
JNDI based registry for your camel components, the JNDI registry is fused
with the JNDI system of JBOSS so that you can assume that any lookup in
You can create the InitialContext the standard JEE way and have it
integrate with the JBoss AS.
Not sure how you do that, but in old days, it was all that initial
context factory and hashtable options you needed to configure.
Also you can have a jndi.properties in the root classpath that has
So for sure the camel registry is not integrated with the app server. No
problem, I can register stuff from the app server in the
CamelContextLifecycle
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA*
*Author of: Hardcore Java (2003) and Maintainable Java (2012)*
*LinkedIn:
I am running my Camel routes packaged as a WAR in JBoss (Actually EAP 6.1.1
which is JBossAS 7.2 I believe) which is a departure from what I am used to
with Servicemix and so on. So I was wondering about the JNDI registry in
light of the application server. Does the registry integrate with the
