Try client persistance. persist="client:page" instead of persist="session"
GbT wrote: > Ok, I understand, but it seems code redundant for me to write three > property for the same object only to submit values back... Suppose I > have 20 fields for example to edit... I have to declare every single > field in the Edit page... and assign every form field to them.... > Isn't it possible to do something similar to WebObjects component > based things... passing the object directly? > > Il giorno 29/mar/06, alle ore 16:00, Mike Snare ha scritto: > >> The problem with just making it persistent is that you now have to >> handle the case where the user gets to the edit page via a path other >> than the intended one (probably clicking on an article title or >> something). >> >> Normally, you could just check to whether the article or id was null >> or empty in the validate method, then redirect to an appropriate page. >> Now you can't do that. During a particular session the article or id >> will never be null once the page is correctly accessed once. This may >> not be desired. >> >> Imagine the user uses your edit page to edit an article then visits >> several other pages. If he then uses the drop-down menu for the back >> button to get back to the edit page he'll see the edit page for >> whatever article he last edited. >> >> Just a thought, >> -Mike >> >> --------------------------------------------------------------------- >> 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]
