Disclaimer:Not knowing your application I realize that the following may be prescribing something you are already doing.
I wonder if you can avoid some of the problems you are having with re-entrant pages by using lightweight action classes. Say you have business services to - retrieve master data - process the queries - process the updates - etc. Being business services they are oblivious of the very existence of Struts. Now, these can be utilized and/or combined by the controller layer (your struts actions). So, you can imagine some Action-0 which does sundry stuff and then gets the data for the master page by invoking the necessary business process(es). A user selects an item and triggers various operations (as you have indicated) via the detail page(s). When the user now wishes to go back to the master page, the action responsible simply invokes the necessary business process(es). This obviates the need to chain a call to Action-0. Typically, there is an assumed context when an Action is invoked. Coupling or chaining actions may violate the context expected by the callee. In other words the caller may have to take several steps just ensure that the context expected is re-created. Extracting your business processes out of the Action classes should minimize the need for chaining. A completely orthogonal approach that *may* satisfy your needs is to place the bean(s) needed by your master page in session scope. This again will preclude the need for repetitive processing. Sri --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
