From: "Murray Collingwood" <[EMAIL PROTECTED]>
I guess pushing the form bean into the session would do this, but session
variables for a
request level function is probably not recommended.
It is by me. :) Put the form in session scope, and most of your problems
will disappear. You pick up a couple of new ones, but the tradeoffs are
generally worth it.
One of my webapps deals exclusively with editing records, and it takes
several requests to finally complete an edit (or an add). All that time, I
have a DTO (Value Object... what are we calling them this week?) and a form
bean in session scope, updating the DTO as necessary until the user hits
'Finish'.
The database key is read-only, in fact it's never in the form bean, it gets
displayed with <c:out> directly from the DTO.
--
Wendy Smoak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
