Hi. I'm probably not going to help you on this one, but I've also had
problems with tomcat and classloading.
I'm using Eclipse and WTP.
I've wicket library (besides other libraries) in tomcat's lib directory
and tomcat refused to load the wicket.protocl.http.WicketServlet.
So in my project I've created my WicketServlet class simply extending
wicket.protocol.http.WicketServlet and put my class in web.xml and it works.
-Matej
Phil Kulak wrote:
I know this is a classloader issue, and probably all Tomcat's problem,
but I am getting these damn things all the time. When I make a change
and reload, this happens about half the time. It takes another reload
(or two) to get Tomcat to wake up and figure out that the class
exists. The reason I'm posting it here is because it only happens to
Wicket apps for some reason and I figure I may not be the only one
experiencing this. Anyway, if anyone's seen this before, please let me
know, it's killing my productivity.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
