[
https://issues.apache.org/activemq/browse/CAMEL-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43422#action_43422
]
Claus Ibsen commented on CAMEL-577:
-----------------------------------
Freeman, I dont suppose I could ask you to try again with TRACE level debugging
in org.apache.camel.util.ResolverUtil.
I would like to see if the trace logging is useable in situations to resolve
problems. Especially of the osgi logging is useable, eg. the logging of the
bundle toString() itself - does it provide a good toString() implementation or
do we need to log: bundleId, symbolName, and whatever can be relevant.
If you could paste the logging output here would be super great.
> ResolverUtil can't resolve class under osgi enviroment
> ------------------------------------------------------
>
> Key: CAMEL-577
> URL: https://issues.apache.org/activemq/browse/CAMEL-577
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.3.0
> Reporter: Freeman Fang
> Assignee: Claus Ibsen
> Fix For: 1.4.0
>
> Attachments: CAMEL-577.patch
>
>
> in method of
> protected void find(Test test, String packageName, ClassLoader loader)
> it try to load class from directory or jar, it works for standalone mode.
> But if the classloader of the method is osgi bundle class loader, it will
> fail since the getResource(packgename) return neither directory nor jar
> for example, package name is org/apache/camel/convert, then what returned is
> /org/apache/camel/convert, so both loadImplementationsInDirectory and
> loadImplementationsInJar doesn't work in this case
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
