I probably should have prefaced my feedback by saying that I don't think it requires functionality changes or even further testing right now. Probably just a 3-4 bullet summary something along the lines of:
- When installing additional Camel components, it is recommended that the component jars and any dependenies are placed in the JBoss ESB SAR's lib directory
- AS 4: .../server/default/deploy/jbossesb.sar/lib/
- AS 5: .../server/default/deployers/esb.deployer/lib/
- While component jars can be installed in alternate locations (e.g. server lib, or within an ESB application), this has not been tested.
- A restart of the ESB server will be required afer installing the component jars before the component's URI can be used by the Camel gateway
We can add class loader scoping to the above instructions when we get around to it. Or maybe someone in the community that's interested will do it and post their experience to the forum.
`k.