On Thu, 30 Dec 2004 10:18:54 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On Thu, 30 Dec 2004 12:47:04 -0500, Sean Schofield > <[EMAIL PROTECTED]> wrote: > > I have developed a basic workflow engine that I have found to be > > extremely useful in my current Struts applications. I developed it > > after finding shortcomings in the open source workflow stuff that was > > available at the time. > > > > As you think about workflow, don't forget to keep an eye on a new > Apache Incubator project called Agila, which bills itself as a > "lightweight BPM engine and auxiliary services." There's no code yet, > so it's not possible to tell if it will meet your needs, but worth a > bookmark for future reference: > > http://incubator.apache.org/projects/agila/index.html > > I'm also curious if you looked at Don's continuations support (based > on the same idea in Cocoon) in Struts Flow. > > http://struts.sourceforge.net/struts-flow/index.html
Also, if you're using JDK 5, Apache Beehive's Page Flow: http://incubator.apache.org/beehive/pageflow/pageflow_overview.html -- Martin Cooper > > I know Craig mentioned a possible need for workflow stuff for Shale. > > I'm not sure if its along the lines of what he is interested in as I > > have not had the time to delve into Shale yet. > > So far, I'm developing some ideas and design patterns around state > information that is saved longer than a request, but shorter than a > session -- and gracefully managing the associated pages and > corresponding view controllers. It's not quite ready for the rest of > the world to look at yet, but will be soon. > > > > > In a nutshell, it provides a simple and flexible framework for > > implementing workflows. It has states, operations, conditions and > > transitions. It provides a default implementation that writes to a > > database (but that is not required.) > > > > I am currently refactoring it to make it a little easier to be used by > > others (borrowing from some of the structural ideas I've seen used in > > commons-chain). I'd be happy to share it for anyone who might want to > > examine/borrow the code. > > > > Also, I'm interested in possibly taking it open source (perhaps as > > commons-sandbox first.) Let me know if anyone is interested in > > working with me on this. > > I'd be interested in seeing what you've come up with. > > > > > sean > > > > Craig > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
