This behavior is not limited to the reverse ajax call but it is seen with all the pages. It is as if the polling for page change stops with the reverse ajax call. Can a Thread.sleep(...) in a dispatcher cause the page change polling to stop?
----- Original Message ---- From: Thiago H. de Paula Figueiredo <thiag...@gmail.com> To: Tapestry users <users@tapestry.apache.org> Sent: Sun, 23 May, 2010 6:01:48 PM Subject: Re: comet implementation issue On Sat, 22 May 2010 19:19:01 -0300, rajesh sukumaran <rajeshs_...@yahoo.co.in> wrote: > Hi, Hi! > Once the reverse ajax script fires the change made to the TML files will not > get reflected in the browser. I have to restart the web application to see > the effect of a change in TML files. This is causing lot of inconvenience in > the development environment. I guess the .tml file checks are only triggered when there's a request for the corresponding page. As you're using a dispatcher, this check may not be done. One trick you can do is to change something in the page class (type a space, delete it, save), as it will rebuild the internal representation of the page, including its template. --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
