Just looking at the proposal, I need to comment that the idea behind the proposal seems very similar to code that we at Witness Systems have been working on to allow 'Wizard' type functionality for our users to prevent them from mis-configuring items with complicated dependencies. Our code is based on the State Table Pattern (from the book Real-Time UML, by Bruce Powell Douglas. 1998 Addison Wesley) and the Avalon Framework (the state machine engine is Configurable, Initializable, etc.) In addition, the Bean Scripting Framework is used to allow the flexible scripting of transition guards. Currently we are using Rhino to access the state machine engine context and evaluate the guards. Our company has also agreed to allow this code to be released back into the open source community (Cocoon? Avalon?), so I thought you might be interested ...
-----Original Message----- From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 7:45 PM To: [EMAIL PROTECTED] Subject: RE: [FYI] Struts flow proposal >From: John Morrison [mailto:[EMAIL PROTECTED]] > >> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] >> >> http://jakarta.apache.org/struts/proposals/workflow.html > >Humm, some of that looks quite familiar... Indeed Good night ~Gerhard +----------------------------------------------+ My parents have been visiting me for a few days. I just dropped them off at the airport. They leave tomorrow. +----------------------------------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
