I was thinking that it would be an applet or application. Something rich.
Ted, as for "enforcing" the workflow, I hadn't even considered it. The goal of
the TODO is just to make a graphical tool that allows you to define a workflow
and automate the process of setting up your config files to support the
workflow. Atleast that's how I read it.
<tataryn:craig/>
Joshua Yip wrote:
> Are you trying to develop an workflow application using purely servlets and
> jsp?
>
> XML is the future!
>
> Joshua Yip
> Software Developer
> IB-DOCS.COM
> Intelligent Business Document dot Com
> Office email: [EMAIL PROTECTED]
> Personal Email:[EMAIL PROTECTED]
> YahooID: joshuayip
> ICQ:8657630
>
> ----- Original Message -----
> From: "Ted Husted" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, June 06, 2001 12:48 AM
> Subject: Re: Work flow RFC
>
> > I'm still fuzzy on the mechanism we would use to represent and enforce
> > the workflow. There has been mention of things like command tokens, but
> > are any code samples available.
> >
> > Can anyone explain how Barracuda implements their workflow, and whether
> > it could be mapped to the Struts Actions/ActionMappings model?
> >
> > I believe Barracuda and Struts are complementary in most ways, and it
> > would be in our best interest to adopt and adapt rather than
> > roll-our-own, if feasible.
> >
> > Jonathan wrote:
> > >
> > > 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
