camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-577) ResolverUtil can't resolve class under osgi enviroment
Date Wed, 11 Jun 2008 17:52:00 GMT


Claus Ibsen commented on CAMEL-577:

Freeman, why are you returning early if its a spring delegating bundle loader?

+    	if (loader.getClass().getName().equals("org.springframework.osgi.util.BundleDelegatingClassLoader"))
+    		return;
+    	}

Is it because its loaded using bundles before, if so could you not return just after the loading
from bundle, or move the check into that code, so its nearly the bundle stuff.

At least I think there should be some comments in the code why we return only for this osgi

> ResolverUtil can't resolve class under osgi enviroment
> ------------------------------------------------------
>                 Key: CAMEL-577
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Freeman Fang
>             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.

View raw message