Event handling has come up several times, but no one's put any code on the table yet :-(
If we were ever to do anything about event handling, or generic validators, I'd love to see something that was compatible with Barracuda. They are doing some nice work over there. Meanwhile, the workflow iniative does have many of the same attributes, and could probably be used in place of the way many people use events now. It thinks in terms of the steps required to complete a workflow, where steps can fire other steps until the workflow is complete, or more input is required. Craig's goal is to realize something that can be used by non-programmers and programmers alike, and configured via, say, XML. The initial code is being built in the commons, and is platform/framework independant. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/struts/ [EMAIL PROTECTED] wrote: > > Take a look at how Barracuda event handling works. I think it allows most > of this type of handling to be done quite elegantly. The web site is > http://barracuda.enhydra.org > The code is open source, and could be used either directly, or as a library > if the licenses are compatible. Otherwise, it might be possible to write > similar functionality, or it would be possible to take some of the ideas > and work with them in Struts. Unfortunately, I think that any change of > this type will be a very significant change (regardless of whether it is > the Barracuda model or a service interface.) > > The base idea is that events are handled rather than "requests" or > "process" classes. Events can fire other events, and there is a chain of > event handling so that default events can be used if there isn't a specific > event. > > Bill Wallace > > (716) 214-8872 > Fax: (716) 295-4718 > Element K > 'the knowledge catalyst' > www.elementk.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
