Robert,
I'm curious as to how putting the count in a hidden is too late?
Maybe you can tell me? As far as I can tell, the composite object (which holds all the form elements) is null when pageBeginRender() is invoked. In other words, it has not taken any values from the form yet. If I don't instantiate the object in pageBeginRender(), the page throws because it's attempting to set a value on a null object.
I'm going to try Richard's suggestion. See if that gets me somewhere.
Thanks, e.
On May 18, 2005, at 5:00 PM, Robert Zeigler wrote:
Eric Schneider wrote:
Hi,
I have a requirement that I'm stumbling on. I have an editor page
that needs to be completely stateless containing no persistent
properties. Users must be able to open this page in multiple browsers
windows, switching back and forth and performing updates.
This is no problem if there are a fixed amount of form elements. When
the user clicks save, I instantiate the bean in pageBeginRender () so it
can successfully take the values from the form.
Where it gets awkward is when you have a dynamic number form elements.
(i.e. - a customer has 0-many shipping addresses). I have to
re-inflate that list of shipping addresses before values are set to the
beans within the lists. Unfortunately, there really isn't a good way
to tell how many shipping address there are, aside from putting this
count in a hidden form input (which is too late anyway). Has anyone
geared up something like this?
I'm curious as to how putting the count in a hidden is too late? When
the page is first rendered, do you have access to the size of the list
before the loop? If so, couldn't you just put in the size of the list in
a @Hidden (before the loop) and use a listener with the @Hidden to
re-instantiate the list? I've used this strategy several times with
success. But... maybe I'm missing something? :)
Robert
I hope I'm explaining this well enough. Any suggestions would be greatly appreciated.
Thanks,
e.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user- [EMAIL PROTECTED]
--------------------------------------------------------------------- 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]
