[
https://issues.apache.org/activemq/browse/SM-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44790#action_44790
]
Willem Jiang commented on SM-1487:
----------------------------------
Since the shared lib's jars can't see the jars in servicemix-camel, the better
solution is hacking the servicemix-camel's pom.xml, adding the external camel
components into the pom.xml.
> Consider adding a placeholder shared library to the servicemix-camel jbi
> component
> ----------------------------------------------------------------------------------
>
> Key: SM-1487
> URL: https://issues.apache.org/activemq/browse/SM-1487
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: 3.1.2, 3.2, 3.2.1
> Reporter: Willem Jiang
> Fix For: 3.2.3, 3.3
>
> Attachments: engines.patch, shared-libraries.patch
>
>
> 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 ..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
