D]
> Subject: Re: Suggestion for Workflow processing in Struts
>
>
> The differences are not much between what u are suggesting vs what I
> mentioned.
> but I would like to point some differences though:
> 1. I believe that a Struts action's should have
> outcomes/result
The differences are not much between what u are suggesting vs what I
mentioned.
but I would like to point some differences though:
1. I believe that a Struts action's should have outcomes/results rather
than basing workflows right away. So a manager can say Action has
Result/Outcome (we can choos
Instead of changing the perform action, how about extending the action
mappings to support workflow constructs? In addition to form bean types,
forwards, redirects, and input pages, the ActionMappings tree could also
store workflows.
if (..) return (mapping.findWorkflow("Failure") ;
else return (
Currently the perform() method in the Action object takes ActionMapping as
one of the parameters & returns the ActionForward instance corresponding
to an evaluated result.
Instead, we could let the perform(...) method return a String which is the
result value. The ActionServlet can then determine