The problem with the store in session solution is what if two people are
working on the same account at the same time?
Mansour wrote:
Dave Newton wrote:
--- Mansour <[EMAIL PROTECTED]> wrote:
I see what you mean now. and after I call update,
then I have to populate it again to redisplay the modified account.
There's now not to re-select form the DB.
Unless it's stored in session or the form contained
all the data you needed to re-display I don't see how
reloading the bean could be avoided.
Perfect, now we are talking. So, I can store the Account obj in a
request or session.
What I am going to do, write an interceptor to set the account in the
request, and I think this should do it.
right ?
Can I push it into the stack ? Is there away ?
d.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
