At 6:43 PM +0200 10/13/05, Matthias Wessendorf wrote:
Wolfgang-
I am now doing something like this
inside of execute(Context context):
ActionContext ctx = (ActionContext) context;
...
ActionMapping mapping = (ActionMapping)ctx.getActionConfig();
ActionForward fw = mapping.findForward("success");
Since the passed ContextIMPL is ServletActionContext, I think it will be
ok... in any environment (portlet e.g)
If you aren't already extending any other class, your commands can
inherit from ActionCommandBase, which may make the expectation that
it be used with an ActionContext more clear -- it's just a simple
command which casts the context and passes it to an abstract
execute(ActionContext) method which you'd implement in your class.
One of the intentions behind moving creation of the ActionContext
into ComposableRequestProcessor (after a brief experiment with trying
to adapt any Context) was to be able to guarantee that all commands
called by the ComposableRequestProcessor would be passed not just a
Context, but an ActionContext.
Joe
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
