On May 28, 2010, at 9:15 PM, Thiago H. de Paula Figueiredo wrote:
On Fri, 28 May 2010 19:41:45 -0300, Norman Franke <nor...@myasd.com>
wrote:
Since I re-populate the list in the onPrepare() call, I'm not sure
why it's doing this. The volatile option is not use anywhere, and
if I tried, I get a NPE anyway.
Loop's volatile parameter is deprecated. Use formState="none" instead.
From the dox, that didn't appear to be an option, just VALUES and
INTERATION. I think my main issue was the the working version stored
the query parameters as part of the activation context, whereas the
broken one wanted it to be submitted from the form. Since onPrepare is
called before the form data was set, my array was null, so Tapestry
decided to restore the values from the form. Not very intuitive, but a
least I have a fix.
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
