Hi Jean, This is concurrency problem you have got , which I also met problems.
According to the document there are two solutions to solve this: one is to use the properties files like Raul already showed, the another way is to use Tapestry.fireObserverChange() which is not recommended in the document. On 3/26/06, Raul Raja Martinez <[EMAIL PROTECTED]> wrote: > no problem, everybody runs in the same problem, I had the exact same > problem as you and thanks to "Enjoying Web development with Tapestry" by > Kent Tong, a must for a tapestry developer, I figured it out. > > http://www.agileskills2.org/EWDT/ > > > > Jean-Eric Cuendet wrote: > > Exactly! > > I understand one step more in Tapestry now! > > Thanks a lot. > > -jec > > > > Raul Raja Martinez wrote: > >> Are you using instance variables such as?: > >> > >> private String text; > >> > >> public String getText() { > >> return this.text; > >> } > >> > >> public void setText(String text) { > >> this.txt = text; > >> } > >> > >> The approach above should not be used but instead you should use: > >> > >> public abstract String getText(); > >> public abstract void setText(String text); > >> > >> > >> Tapestry will take care of creating the appropriate instance variables > >> and implementing its accessors after enhancing your page or component. > >> If you use instance variables in your abstract pages or component, > >> their value will be reused across pages which is not a good thing and > >> it can also compromise security. > >> > >> > >> > >> > >> > >> Jean-Eric Cuendet wrote: > >> > >>> > >>>> That's no directive of the .page file, these are meta-tags within the > >>>> <head> section of the html. Usually Safari makes the most problems with > >>>> no-caching tags. The following works for me on Safari, IE and Firefox. > >>>> > >>>> > >>>> > >>>> <META http-equiv="Cache-Control" content="no-store, > >>>> no-cache, must-revalidate, max-age=0"> > >>>> <META http-equiv="Cache-Control" content="post-check=0, > >>>> pre-check=0"> > >>>> <meta http-equiv="expires" content="0" > > >>>> <meta http-equiv="Pragma" content="no-cache"> > >>> > >>> > >>> Thanks a lot. I did that but that didn't solved my problem. > >>> The problem was that in my component, one member variable was kept > >>> between pages reuse. So the next same page was rendered with the data > >>> of the previous page. > >>> Initialized the members to null and all was fine. > >>> Thanks. > >>> -jec > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
