Patrick Casey wrote:
If you make it persistent, it's stuck to your session. If you just
leave it around on the page, it just pops up the next time somebody pulls
that page out of pool. If it's the same user who put it in there (as is the
case in a single user test system usually), then all is well. If it's
somebody else though, things are going to get very weird very fast.
--- Pat
-----Original Message-----
From: Scott F. Walter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 01, 2005 5:24 PM
To: [email protected]
Subject: Stupid Property Question
Greetings,
I have been using Tapestry for a couple of months now and I have to
confess I don't know the answer to a basic Tapestry question. What is
the difference between marking a property as persistent in the page
specification (along with declaring abstract getter/setter) compared to
creating an instance variable in the page with appropiate concrete
getter/setter.
To me they both seem to persist.
Thanks.
--
Scott F. Walter Scott F. Walter
Principal Consultant
Vivare, Inc.
E: [EMAIL PROTECTED]
E: [EMAIL PROTECTED]
Visit scottwalter.com <http://scottwalter.com> --Point. Click. Explore!
---------------------------------------------------------------------
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]
Yikes! I better go back through my pages, because I know I was lazy a
couple of times and didn't bother with making a property persistent in
the page specification.
--
Scott F. Walter Scott F. Walter
Principal Consultant
Vivare, Inc.
E: [EMAIL PROTECTED]
E: [EMAIL PROTECTED]
Visit scottwalter.com <http://scottwalter.com> --Point. Click. Explore!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
