Activity

I checked this problem - ROME PluginManager try to use class loader from endpoint bundle. I added simple fallback condition to ROME - first of all ROME try to use bundle class loader to resolve plugin classes. If they will thow ClassNotFoundException PluginManager will use local class loader. All ROME features should work with this because patch does not have any impact to standard behaviour.

Łukasz Dywicki
added a comment - 22/Mar/10 15:28 I checked this problem - ROME PluginManager try to use class loader from endpoint bundle. I added simple fallback condition to ROME - first of all ROME try to use bundle class loader to resolve plugin classes. If they will thow ClassNotFoundException PluginManager will use local class loader. All ROME features should work with this because patch does not have any impact to standard behaviour.

Hello Willem,
You're right - this path is for ROME not for Camel. I subitted this here because ROME looks like death project (spam on developer mailing list, no activity on issue tracker). If patch will be accepted we can fix and move ROME codebase to servicemix bundles repository.

Łukasz Dywicki
added a comment - 23/Mar/10 09:16 Hello Willem,
You're right - this path is for ROME not for Camel. I subitted this here because ROME looks like death project (spam on developer mailing list, no activity on issue tracker). If patch will be accepted we can fix and move ROME codebase to servicemix bundles repository.

Willem Jiang
added a comment - 24/Mar/10 08:51 Hi Lukasz,
I'm afraid you need to create a JIRA in ServiceMix,which may ring the bell of Gert
The only thing that I think we can do in Camel is updating the features file for new ROME bundle.

If the patch provided fixes the issue, it's OK for me. We have two ways to get this included in Camel:

use the version provided in repository.code-house.org which already includes the fix

build a servicemix bundle for Rome which includes this fix

Personally, I would prefer option 2 because that will eventually get us a valid bundle for Rome in central repository. If that's OK for everyone, I'll move the issue to the SMX4 project and build the bundle to update the Camel features.xml afterwards. If we stick to scenario 1, all we need to do in Camel is use that bundle in our features.xml and we're done.

Gert Vanthienen
added a comment - 24/Mar/10 09:00 L.S.,
If the patch provided fixes the issue, it's OK for me. We have two ways to get this included in Camel:
use the version provided in repository.code-house.org which already includes the fix
build a servicemix bundle for Rome which includes this fix
Personally, I would prefer option 2 because that will eventually get us a valid bundle for Rome in central repository. If that's OK for everyone, I'll move the issue to the SMX4 project and build the bundle to update the Camel features.xml afterwards. If we stick to scenario 1, all we need to do in Camel is use that bundle in our features.xml and we're done.
Regards,
Gert