Oops, I don't know why did I mention going back again. I guess, I am too fixated on that. I am sorry.
Anyway, just to reiterate, I have a "current object" in the session. "Current" means "currenty being used" whatever that means for you. Object has an ID. I pass this ID to any action which uses this object. It can be edit action, or view action or delete action or store action. Returning to the book example. I don't know what the authors list for :) But whatever, I would have two objects: book itself and authors list. For the first page I would have two references in the form bean: to book object and to authors collection. When I select author from a collection, its name would go to the book object. So, book is a "current object". I can edit it, view it, persist it, delete it. It sits in the session, updated. If I want to display a book on the next page, I just show the book, which already has author in it. If I want to edit it, I show it on edit page, and load the author collection again. And, returning to my object of fixation: if I go back to the book edit page, the book will have author preset, simply because I display the object's fields, not because I take efforts to prepopulate form's fields. Right, this is another thing that I do not do: I do not prepopulate form bean's fields. On 5/12/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > Summing all up, I can describe the approach I use: <...deleted...> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
