On 3/29/06, Alexei Sokolov <[EMAIL PROTECTED]> wrote:
Hello,
This is my first post here, so please don't yell at me
right away...
Anyway, I was wondering what you think about changing
two places in wicket, both related to class loading.
in ContextParamWebApplicationFactory:
final Class applicationClass =
getClass().getClassLoader().loadClass(
applicationClassName);
change to:
final Class applicationClass =
Thread.currentThread().getContextClassLoader().loadClass(
applicationClassName);
and in DefaultClassResolver:
change:
return
DefaultClassResolver.class.getClassLoader().loadClass(classname);
to:
return
Thread.currentThread ().getContextClassLoader().loadClass(classname);
I don't think it'll brake anything in the existing
apps, but the changes allow for easy integration with
OSGi containers.
Alexei
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
