Hi Rick,
This is the approach what i have taken..
1) I had all forms set to Session Scope in the Struts config.
2) Maintain an "actionStack" form variable in all the form, which
would keep track of all the required actions as CSV in FILO
order(Login,PlayerSearch,EditPlayer,..)
3) Maintain
Andrew Hill wrote the following on 10/25/2004 8:41 PM:
In your case you probably dont need to go as far as I did. You could
perhaps just keep track of the pages in the stack in a session scoped
collection and override the requestProcessor to look in that collection
for the form instead of inst
Hi Rick,
I did this for a large application where there were a lot of different
record types with various linkages much as your roster has with players,
and where said linkages could nest quite deeply.
You will need to use the session to do it cleanly. The idea is to
somehow keep a stack of Act
Hubert Rabago wrote the following on 10/25/2004 11:54 AM:
First, allow the editing of a player from one location only. This
way, I only need to get back to that page.
I 'try' to do this also.
Second, if you're on the roster screen, and you want to edit the
player, I'll let you do that, but in a se
I personally try to avoid situations like this. There are a couple of
ways I avoid it.
First, allow the editing of a player from one location only. This
way, I only need to get back to that page.
Second, if you're on the roster screen, and you want to edit the
player, I'll let you do that, but
To cut to the chase.. Imagine a hypothetical UI where you have
checkboxes next to football players and by checking the boxes and
hitting 'save' you would be saving a roster. Typically you'd have a
FormBean to capture this information and probably a "RosterAction".
Now also imagine that next to
6 matches
Mail list logo
