As far as I understood flash strategy is needed to store values between
form submission and render requests.
Your flow:
1. onActivate() create values and store them in session
2. onSubmit() retrieve values and remove them from session => add value to
detached collection
3. onActivate() retrieve val
bit of a hack but can you put the list to a single string delimited by
control chars or caret ^
prior to form submission
then on rendering of 2nd page convert back from single string to list
chris
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/PersistenceConstants-FLAS
if i don't want to store the List in the session for a long time, is there
any advice to solve this problem?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/PersistenceConstants-FLASH-cann-t-persist-List-String-langs-tp5719462p5720163.html
Sent from the Tapestry - User ma
All the fields marked with @Persist(PersistenceConstants.FLASH) are cleared.
(Internally these fields are cleared as soon as the value is read from the
session)
regards
Taha
On Feb 19, 2013, at 2:49 PM, John wrote:
> Initially there will be no session, then after the first submit there will
Initially there will be no session, then after the first submit there will
be an empty session.
Geoff
So flash items are cleared from the session after a form submit? Are all
items cleared or just the ones in the form?
John
On Mon, 18 Feb 2013 20:38:03 -0300, John wrote:
If a field uses the FLASH persist constant but is not a @Property is it
the same as being persisted in the session with plain @Persist because
the field is not read by the template directly to take it out of the
session?
No. @Persist with @
I "think" because you refer to the *langs* object in the *activation* event
method, it flashes the object. You find it as an empty list, correct ?
I'm not fully aware of the FLASH persistence but I suppose it's only meant
for persisting form fields across requests and a Collection isn't
applicable
