On Tue, 15 Jun 2010 19:37:54 -0300, ebt <no.spam.tal...@gmail.com> wrote:
I should have also added that I am using the tomcat service from within
eclipse using run-as etc. I guess that might add a layer of complexity
that would be hard to pin down. I shut down tomcat and dropped into the
terminal and ran mvn jetty:run and everything ran normally.
I have a very bad experience with the Tomcat support in Eclipse. Jetty is
superior IMHO.
This points to a
configuration issue rather than a Tapestry issue. I guess worse comes to
worse I can try to figure out how to remote debug using jetty.
Just use m2eclipse, a run configuration that launches jetty:run and debug
it normally. You don't need to configure remote debug.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
