The design of the BaseAction and other classes in the o.a.s.scaffold package is very clean and allows for modular code development. However, how does one use the classes effectively without creating instance variables -- a big no, no when it comes to Struts Actions.
For example, the BaseAction's execute() method centrally calls preProcess(), executeLogic() and postProcess() passing each method the action mapping, the form bean, the request and response objects. How then should one handle business objects that are generated in one method and may be required in another? What's the best way to persist (to the request/session) objects that will be expected by components after this action completes? One could set up a convention to perform such persistence in, say, the postProcess() method. However, how does one pass the necessary objects to this method. It is very tempting to use instance variables, but in a multi-threaded container that's just suicidal. Any suggestions? Sri
