Use the jetty start class instead. There's little difference between tomcat/jetty when you're using Wicket as a deployment platform, but the development experience is much more different.
Martijn On Tue, Dec 23, 2008 at 11:34 AM, Björn Tietjens <bjor...@web.de> wrote: > Hi, > > I am developing a webapp with wicket on eclipse, deploying as war, using a > local tomcat for testing. > What is the best/easiest way to debug my app with eclipse? > How can I deploy/start the webapp from within eclipse or how can I attach > eclipse to tomcat in order to debug my code? > > Thanx for your help. > Cheers Björn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
