Ahh, yeah... I've got that around here somewhere... Thanks Geoff, ya got me - worked like a charm, though I'd assume that if the framework creates the underlying var, it would manage it as well. Oh well, thanks again...
-----Original Message----- From: Geoff Longman [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 03, 2005 9:14 PM To: Tapestry users Subject: Re: Tap4: Simple form field state question You have a <property-specification> for the email property... Let's see that pls. Geoff On 8/3/05, Lance Arlaus <[EMAIL PROTECTED]> wrote: > I apologize for the newbie clutter I'm introducing (I'll be sure to give > back in due time). > > The real question here is whether Tapestry is supposed to clear the concrete > fields it's created for the abstract properties defined in my page class or > if I'm responsible for overriding detach or some other appropriate method. > It would seem to make sense that Tap would handle this for me (the examples > don't appear to explicitly clear fields on detach). > > -----Original Message----- > From: Lance Arlaus [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 03, 2005 1:42 PM > To: 'Tapestry users' > Subject: Tap4: Simple form field state question > > I have a very simple page with a form containing a few fields linked to > properties on my page class like so: > > > > Page: > > <input jwcid='email' length='30'> > > Spec: > > <component id="email" type="TextField"> > > <binding name="displayName" value="Email"/> > > <binding name="value" value="email"/> > > <binding name="validators" value="required, email"/> > > </component> > > Class: > > public abstract String getEmail(); > > public abstract void setEmail(String email); > > > > > > I've noticed that if I enter a value in the field, submit the form, then > navigate to the original root app URL and refresh, the previously entered > value reappears. > > Checking the rendered page source HTML, the page is clearly being rendered > anew by Tapestry with the previous values. > > Where and how is this state being saved? I haven't maked any fields > persistent or anything to notify Tapestry to intercede. > > I thought Tapestry would reinitialize the page prior to rendering. If not, > what's the best practice on this? > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- The Spindle guy. http://spindle.sf.net Get help with Spindle: http://lists.sourceforge.net/mailman/listinfo/spindle-user Announcement Feed: http://www.jroller.com/rss/glongman?catname=/Announcements Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- 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]
