You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Jason van Zyl <ja...@zenplex.com> on 2003/03/01 05:06:34 UTC

Re: Workflow with Turbine

On Fri, 2003-02-28 at 16:01, Edgar González wrote:
> Hi,
> 
> In a new project we need to implement Workflow features. 
> Anybody has experience with that?
> Any recomendation? OpenSymphony Workflow, Werken's Werkflow, OpenBusinessEngine ?

Werkflow is the only engine based on Aalst's concept of a petrinet
whereas OSWorkflow uses a simple state machine. Go do some research on
citeseer or go find any books on the theory of workflow and you'll find
they are all based on petrinets. All commercial grade workflow engines
are also all based on petrinets. A petrinet is just a graph that models
transitions to places given a set of rules. A superset of what a state
machine can provide.

Currently you define the workflow in Jelly and from there you can do
what you like. I don't let Jelly do anything to the model, I basically
make it send messages to my model when transitions are made in the
workflow. Currently Werkflow has tags which use petrinet terminology and
there are also a set of idiomatic tags which look like plain english.

I'll note I'm biased as I hired Bob to write Werkflow for use in
Tambora. I couldn't find anything else that worked for the seriously
nasty workflows Tambora deals with.

> Thanks
> 
> Edgar
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org