This is usually called "action chaining" * http://struts.apache.org/2.x/docs/action-chaining.html
Experience shows that chaining should be used with care. If chaining is overused, an application can turn into "spaghetti code". Be sure to ask yourself why you need to chain from Action1 to Action2. Could the logic in Action2 be pushed back to a support class or business facade so that Action1 can call it too? Ideally, Action classes should be as short as possible. All the core logic should be pushed back to a support class or a business facade, so that Actions only call methods. Actions are best used as adapters, rather than as a class where coding logic is defined. -- HTH, Ted <http://www.husted.com/ted/blog/> On 10/4/07, ros <[EMAIL PROTECTED]> wrote: > > Hi! > > I use struts2 and want to load object in action1 and then access in in > action2 and result jsp, like on drawing > > my1.html -(myobject.id)-> action1.save -(myobject)-> action2.edit > -(myobject)-> my2.jsp -> my2.html > > I do not want to load this object in action2.edit if it was already loaded > in action1.save. > > Can struts2 pass objects from action to action? > > Thanks. > > > -- > View this message in context: > http://www.nabble.com/how-to-keep-object-from-action-to-action-tf4569127.html#a13040888 > Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
