There are also some previous posts related to file-locking under Jetty that may be relevant to this problem. There are config workarounds suggested in some previous posts if you search for file locking.
Regards, Jim. -----Original Message----- From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 22 December 2010 16:10 To: Tapestry users Subject: Re: Strange behaviour of jetty On Wed, 22 Dec 2010 13:59:44 -0200, Jens Reufsteck <jens.reufst...@staufenbiel.de> wrote: > Hi, Hi! > from time to time, I get the following exception: > Unable to resolve 'Login' to a known page name. Available page names: > ExceptionReport, PropertyDisplayBlocks, PropertyEditBlocks, ServiceStatus This looks like a failed context undeploy. With Tapestry's live class reloading, you can disable the Jetty's automatic context redeploy on class change. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
