Good catch. Well, that just means that it is an issue across the board.
Lets get a list together of possible approaches and put it up somewhere for
us to comment on and review.
----- Original Message -----
From: "Frye, Dave" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 05, 2001 2:22 PM
Subject: RE: Work flow RFC
> >From Barracuda's Scope Summary (see,
> http://barracuda.enhydra.org/Barracuda/docs/scope_summary.html#2.4),
> Barracuda's scope explicitly excludes application flow control.
>
> didge
>
> -----Original Message-----
> From: Jonathan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 05, 2001 9:34 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Work flow RFC
>
>
> Again, Ive got to say look at the Barracuda project. They have one of
these
> gui configurers. Check it out at
> http://barracuda.enhydra.org/Barracuda/GetBConfig.event
>
>
> ----- Original Message -----
> From: "Craig Tataryn" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, June 05, 2001 12:28 PM
> Subject: Work flow RFC
>
>
> > Hi, I would like your comments for the workflow item on our TODO list.
> > Currently this is how I've envisioned the workflow project:
> >
> > 1) A nice GUI type Applet or Application that has visual constructs
> > which can be connected in a Visio type manner to create an Activity
> > diagram or some other type of flow diagram.
> >
> > 2) This diagram will be persisted in an XML file which holds meta data
> > for the elements in diagram (position, type of construct (controller,
> > flat html page, cgi script, flow arrow, etc..)).
> >
> > 3) The diagram can be exported to a struts config file via XSLT (i.e.
> > workflow.xml -> workflow2struts.xsl -> struts-config.xml)
> >
> > 4) A diagram can also be imported from a struts-config.xml file via XSLT
> > (i.e. struts-config.xml -> struts2workflow.xsl -> workflow.xml). Of
> > course some sort of "pretty layout" code would have to be used to
> > un-jumble the mess of constructs that are sucked out of the
> > struts-config.xml file (i.e. take a guess at proper positioning
> > information).
> >
> > The GUI should employ some sort of extensibility mechanism like BSF
> > (http://oss.software.ibm.com/developerworks/projects/bsf) or Bean Shell
> > (http://www.beanshell.org/) to allow users to plug-in their own
> > functionality (i.e. validation code) without jeopardizing the core code
> > (what I call the Emeril Lagasse technique -- BAM!).
> >
> > I realize this is a very high level look at the TODO but I think as we
> > get more comments we will get more granular and can start dishing out
> > segments.
> >
> > Let me know what you think.
> >
> > <tataryn:craig/>
> >
>
