Good idea to try. I understood there were issues with that too, but
can't remember what it was anymore.
Eelco
Gili wrote:
An article related to the topic:
http://www.javaworld.com/javaworld/javaqa/2003-06/01-qa-0606-load.html
I'd go with Thread.currentThread().getContextClassLoader() myself
because at least that is configurable at runtime (so the user can
change its value before Wicket uses it).
Gili
Martijn Dashorst wrote:
Cameron Braid wrote:
I thought the Thread.currentThread().getContextClassLoader() is to
support
this kind of situation
Will that help when someone (a daring person I might say) loads a jar
file using his/her own classloader?
Martijn
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
