On Thursday 30 March 2006 07:10, Alexei Sokolov wrote: > I'm working on integrating Wicket into OSGi container. > Classloader schema in the container is more complex > than the one used by j2se app servers, so simple > Class.forName does not always work.
We are also working on this (Wicket in OSGi) and our solution involves replacing the Wicket ClassResovler with our implementation that deals with the underlying framework (in our case OSGi). So, it should be fairly easy you to use the Thread.contextclassloader there if you like. Cheers Niclas ------------------------------------------------------- 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
