Nice follow-up article on integrating components outside of Camel Core:
http://community.jboss.org/wiki/CamelGatewayUsingnon-coreComponents
o Is the jboss.esb lib directory the only recommended place to put component libraries? It's certainly possible to put it in one of the higher level AS lib directories. Is it possible to bundle them with the ESB application? Do we recommend against these other methods?
o Component jars in the jboss.esb lib directory will be loaded during server startup. Correct me if I'm wrong, but adding additional jars here will require the ESB sar to be redeployed or (more likely) the server restarted. Might want to point this out.
o Having a single class loading space for additional components means that there can only be one version of a component in the ESB runtime at any given time. Probably worth mentioning this point.
o There is a distinct possibility that one of the many camel components will include jars that we already have in the ESB or the AS already. If the versions of these dependencies are different than things can go boom. Isolating the class space with class loader repository might be one way to address this. Another way to address it is to say "YMMV". ;-)
`k.