I'm new to struts and haven't watched all the discussion about workflow
processing. If anyone could give me a short introduction on what has
happened so far I would be thankful (since I like the design behind struts I
would really like to contribute). As far as I can see from the discussion,
you are planning to integrate the workflow processing into the ActionServlet
(in some way). I may have missed an important point, but wouldn't it be more
flexible to seperate the workflow processing from the action mapping and the
ActionServlet. What I mean is to create a standalone workflow processing
engine that can be invoked from special Action classes, but that doesn't
know anything about Actions or servlets.
Andreas
> -----Original Message-----
> From: Rajan Gupta [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 16, 2001 2:11 AM
> To: [EMAIL PROTECTED]
> 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/results rather
> than basing workflows right away. So a manager can say Action has
> Result/Outcome (we can choose what we like amongst the 2), rather than
> action has workflows, because worklflows can be reused across actions.
> 2. A workflow should be executed based upon the outcome of an action
> e.g. When a user has made a payment, ActionPayment has the
> following
> results "Payment Successful", Insufficient Funds"
> Let us say that we want to take the user to an offer
> Screen to pay his
>
> balance if the result is "Insufficient Funds" and also log the fact
> that
> we did so. This is my opinion is a workflow which results
> as an outcome
>
> of an action.
> 3. Struts does not use references to JSP pages, actions &
> possibly using
> the same paradigm may not use references to web flow
> steps. This will
> lead to code duplicacy in terms of the "type="
> Struts may allow use of references in its actions
> e.g. Offer.jsp may be referenced using a reference names OfferVU
> allowing OfferVU to be used in any action mapping. So if offer.jsp
> changes to a new name, we do not have to go to every
> action mapping and
>
> replace the name. Similarly for Actions & their types
>
> Thanks
> Rajan
>
