You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2008/07/30 10:34:00 UTC
[jira] Created: (SM-1487) Consider adding a placeholder shared
library to the servicemix-camel jbi component
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.2.1, 3.2, 3.1.2
Reporter: Willem Jiang
Fix For: 3.2.2
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.
[jira] Commented: (SMXCOMP-15) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49696#action_49696 ]
Willem Jiang commented on SMXCOMP-15:
-------------------------------------
Hi Ron,
sure, It's on my todo list :)
Willem
> Consider adding a placeholder shared library to the servicemix-camel jbi component
> ----------------------------------------------------------------------------------
>
> Key: SMXCOMP-15
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-15
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: 3.2.1
> Reporter: Willem Jiang
> Fix For: servicemix-camel-2009.01
>
> 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.
[jira] Updated: (SM-1487) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated SM-1487:
-----------------------------
Attachment: engines.patch
> 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.2
>
> 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.
[jira] Updated: (SM-1487) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated SM-1487:
-----------------------------
Fix Version/s: 3.3.1
3.4
(was: 3.3)
(was: 3.2.3)
> 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.3.1, 3.4
>
> 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.
[jira] Updated: (SM-1487) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated SM-1487:
-----------------------------
Attachment: shared-libraries.patch
> 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.2
>
> 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.
[jira] Updated: (SM-1487) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated SM-1487:
-----------------------------
Fix Version/s: 3.2.3
3.3
(was: 3.2.2)
> 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.
[jira] Commented: (SM-1487) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (SMXCOMP-15) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved SMXCOMP-15.
---------------------------------
Resolution: Won't Fix
> Consider adding a placeholder shared library to the servicemix-camel jbi component
> ----------------------------------------------------------------------------------
>
> Key: SMXCOMP-15
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-15
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: 3.2.1
> Reporter: Willem Jiang
> Fix For: servicemix-camel-2009.01
>
> 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.
[jira] Commented: (SMXCOMP-15) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Ron Gavlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49688#action_49688 ]
Ron Gavlin commented on SMXCOMP-15:
-----------------------------------
Hi Willem,
What would you think about adding a wiki page that walks through an example of hacking/rebuilding the servicemix-camel component to add an additional library like camel-cxf?
/Ron
> Consider adding a placeholder shared library to the servicemix-camel jbi component
> ----------------------------------------------------------------------------------
>
> Key: SMXCOMP-15
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-15
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: 3.2.1
> Reporter: Willem Jiang
> Fix For: servicemix-camel-2009.01
>
> 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.
[jira] Commented: (SMXCOMP-15) Consider adding a placeholder shared
library to the servicemix-camel jbi component
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49496#action_49496 ]
Willem Jiang commented on SMXCOMP-15:
-------------------------------------
Here is the mail thread about this issue[1], because of the shared library's limitation, it is better to hacking the servicemix-camel component pom.xml to add the additional libraries which are needed in the camel SU.
So I'd like to close this issue without apply the upper patch.
[1] http://cwiki.apache.org/SM/discussion-forums.html#nabble-to18685805|a18685805
> Consider adding a placeholder shared library to the servicemix-camel jbi component
> ----------------------------------------------------------------------------------
>
> Key: SMXCOMP-15
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-15
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: 3.2.1
> Reporter: Willem Jiang
> Fix For: servicemix-camel-2009.01
>
> 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.