The values in the flash reset when they are next used (to restore
properties of page B), not when the page containing the flashed values
is rendered. This is subtly different than tapestry-flash for T4,
because the structure of the request cycle is a bit different
(component event requests send page render redirects).
So when page A is resubmitted with errors, the values for page B are
lost (assuming some part of the form submission accesses page B). To
really pin it down, I'd need to see more code.
The solution is to only set values on page B immediately before
returning the page B instance from page A's onSuccess().
On 2/4/07, Ted Steen <[EMAIL PROTECTED]> wrote:
Hi,
PageA injects PageB, in PageB i have a field "someProp" which is
annotated with @Persist("flash").
In the code on PageA.onSuccess() I do pageB.setSomeProp(value) and return pageB.
now PageB shows up with the value in "someProp", but on the next
request (e.g. after form submission with errors) the value is null..
is this expected behaivour?
--
/ted
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
