You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Michael Mansell (JIRA)" <ji...@apache.org> on 2009/01/04 00:00:05 UTC
[jira] Created: (CAMEL-1221) Unable to find dynamically loaded
languages when using OSGi
Unable to find dynamically loaded languages when using OSGi
-----------------------------------------------------------
Key: CAMEL-1221
URL: https://issues.apache.org/activemq/browse/CAMEL-1221
Project: Apache Camel
Issue Type: Bug
Components: camel-osgi
Affects Versions: 1.5.0
Environment: OSGi Equinox 3.4.2
Reporter: Michael Mansell
The camel-osgi component only supports loading Components via the OSGi bundles in the 1.5.0 release code. It looks like someone started to add more things that can be automatically loaded on the trunk, because there was a refactor to allow TypeConverters to be added via OSGi bundles.
Definitely, adding Languages is still missing (both in 1.5.0 and on the trunk). Perhaps there are more as well, as I'm not up on all the things that Camel loads using the same mechanism.
I've got Languages working by patching my copy of 1.5.0 (basically by creating my own version of the LanguageResolver based on the OSGiComponentResolver), but as the refactor seems to be taking the code in a different direction, I'm not going to push a patch yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1221) Unable to find dynamically loaded
languages when using OSGi
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48443#action_48443 ]
Willem Jiang commented on CAMEL-1221:
-------------------------------------
Hi Michael,
Thanks for pointing the language resolver issue out. I will take care of it.
Willem
> Unable to find dynamically loaded languages when using OSGi
> -----------------------------------------------------------
>
> Key: CAMEL-1221
> URL: https://issues.apache.org/activemq/browse/CAMEL-1221
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-osgi
> Affects Versions: 1.5.0
> Environment: OSGi Equinox 3.4.2
> Reporter: Michael Mansell
> Assignee: Willem Jiang
>
> The camel-osgi component only supports loading Components via the OSGi bundles in the 1.5.0 release code. It looks like someone started to add more things that can be automatically loaded on the trunk, because there was a refactor to allow TypeConverters to be added via OSGi bundles.
> Definitely, adding Languages is still missing (both in 1.5.0 and on the trunk). Perhaps there are more as well, as I'm not up on all the things that Camel loads using the same mechanism.
> I've got Languages working by patching my copy of 1.5.0 (basically by creating my own version of the LanguageResolver based on the OSGiComponentResolver), but as the refactor seems to be taking the code in a different direction, I'm not going to push a patch yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-1221) Unable to find dynamically loaded
languages when using OSGi
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-1221:
-----------------------------------
Assignee: Willem Jiang
> Unable to find dynamically loaded languages when using OSGi
> -----------------------------------------------------------
>
> Key: CAMEL-1221
> URL: https://issues.apache.org/activemq/browse/CAMEL-1221
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-osgi
> Affects Versions: 1.5.0
> Environment: OSGi Equinox 3.4.2
> Reporter: Michael Mansell
> Assignee: Willem Jiang
>
> The camel-osgi component only supports loading Components via the OSGi bundles in the 1.5.0 release code. It looks like someone started to add more things that can be automatically loaded on the trunk, because there was a refactor to allow TypeConverters to be added via OSGi bundles.
> Definitely, adding Languages is still missing (both in 1.5.0 and on the trunk). Perhaps there are more as well, as I'm not up on all the things that Camel loads using the same mechanism.
> I've got Languages working by patching my copy of 1.5.0 (basically by creating my own version of the LanguageResolver based on the OSGiComponentResolver), but as the refactor seems to be taking the code in a different direction, I'm not going to push a patch yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1221) Unable to find dynamically loaded
languages when using OSGi
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-1221.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.5.1
Hi Michael,
Could you check out the latest Camel2.0 snapshot or camel 1.5.1 snapshot to verify my fixing ?
Willem
> Unable to find dynamically loaded languages when using OSGi
> -----------------------------------------------------------
>
> Key: CAMEL-1221
> URL: https://issues.apache.org/activemq/browse/CAMEL-1221
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-osgi
> Affects Versions: 1.5.0
> Environment: OSGi Equinox 3.4.2
> Reporter: Michael Mansell
> Assignee: Willem Jiang
> Fix For: 1.5.1, 2.0.0
>
>
> The camel-osgi component only supports loading Components via the OSGi bundles in the 1.5.0 release code. It looks like someone started to add more things that can be automatically loaded on the trunk, because there was a refactor to allow TypeConverters to be added via OSGi bundles.
> Definitely, adding Languages is still missing (both in 1.5.0 and on the trunk). Perhaps there are more as well, as I'm not up on all the things that Camel loads using the same mechanism.
> I've got Languages working by patching my copy of 1.5.0 (basically by creating my own version of the LanguageResolver based on the OSGiComponentResolver), but as the refactor seems to be taking the code in a different direction, I'm not going to push a patch yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.