could you post the source of your page and template?
are you using https? http <-> https switches?

we're already using T5 in production and never had this issues

g,
kris




Ciaran Wood <[EMAIL PROTECTED]> 
12.06.2008 16:03
Bitte antworten an
"Tapestry users" <users@tapestry.apache.org>


An
Tapestry users <users@tapestry.apache.org>
Kopie

Thema
Question about T5's page lifecycle - instance variables NOT being purged






I¹ve noticed on a tapestry app that we are building, that if two users on
separate machines go to the same page, the second user can see the first
users submitted details on the form. We¹re just using a Form component, a
model Object in the page class and declaring each of the properties as
Œeditor¹ components (Textfield, Checkbox etc) like so:

<t:textfield t:id="userName" t:value="member.credentials.userName"
t:validate="required,minLength=4,maxLength=16,regexp²/>

We¹re not using a beanEditForm since the Member object has nested objects
such as Credentials, Contact etc. I¹ve checked that the two users are
getting different JSESSIONIDs, so no session sharing is present. There is 
a
@Persist(session) annotation on the Member model object inside the page. 
Is
this a bug in Tapestry? I thought that Tapestry was meant to clear all
instance variables once the page returns to the pool?

Cheers for any help, I¹m completely stumped!

Ciaran Wood


Reply via email to