Couldn't ActionInvocation just do nested storage of the ActionContext, just
like GenericDispatcher did?
-Pat
----- Original Message -----
From: "Jason Carreira" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 20, 2003 12:20 PM
Subject: RE: [OS-webwork] XWork: calling Actions from Actions
> Patrick, this came up while you were gone. Did you have any thoughts on
> this? In order to be able to do this easily, we'd need to pull the
> ActionContext initialization out of the ActionInvocation initialization,
> so you can use one ActionContext for multiple invocations. Matt didn't
> like the option where you do:
>
> ActionContext myContext = ActionContext.getContext();
> ActionInvocation anotherInvocation = new
> ActionInvocation("someNamespace","anotherAction");
> String otherResult = anotherInvocation.invoke();
> ActionContext.setContext(myContext);
>
> Which would be needed to save the current context, then re-set it after
> invoking the other action... This is not really pretty, but as I'm
> thinking about it, it could be a helper method in ActionSupport...
>
> Jason
>
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
