[SMXCOMP-15] Consider adding a placeholder shared library to the servicemix-camel jbi component

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.2.1
• Fix Version/s: servicemix-camel-2009.01
• Component/s: servicemix-camel
• Assignee: Unassigned
• Reporter: Willem Jiang
• Created: 30/Jul/08 08:33
• Updated: 16/Feb/09 15:39
• Resolved: 16/Feb/09 03:13

Description

The camel component just contains the core camel-jars, but some usecases require the use of addon components (for example camel-cxf) which are not present in the core camel-jar. If you have multiple SU's with a dependency on an addon component then you will hit classloading conflicts (ClassCastException typically ). You currently need to:

1) Add the camel extension components to a jbi shared library

2) Edit the camel components jbi.xml and add your shared library to the components bootstrap classpath as shown in this example:
http://open.iona.com/issues/secure/attachment/11763/jbi.xml

Having to edit the jbi.xml is not ideal so this enhancement is to add a placeholder shared library to the camel-core component. The shared library can be empty but will need to exist in the hot deploy directory.

This would eliminate the need to hack the jbi.xml, you would just need to overwrite the shared library ..