Re: [Perl-workflow-devel] Typed conditions and perl config
Brought to you by:
jonasbn
From: Jim B. <cb...@bu...> - 2008-03-17 12:19:43
|
Has anyone had a chance to try any of the new functionality? We've been running it in our dev and QA environments and so far everything appears to be working correctly. Any chance we could look at a plan to release to CPAN? Thanks, Jim Jim Brandt wrote: > Hello all, > > I've checked in changes for the following: > > * conditions can now be typed, so if you have foo and a bar workflows, > they can implement the condition AdminRequired with the same name, but > different code for each. > > * I applied all the type changes to the perl config. > > Other notes: > > * I decided not to implement types for validators because I couldn't > come up with a case where a validator would vary by type. I mean > 'is_number' or 'is_email_address' should be the same regardless of a type. > > * The tests for perl configuration were very light, so most of my time > was spent trying to add testing infrastructure for perl configs. > > * There was no testing of persister configs, so I added some. There is > room for more. > > * I discovered that the persister configuration isn't consistent with > the other methods. For example, in the xml, actions look like: > > <actions> > <action> > > But persisters don't have that outer tag level. It would probably be > good to add it at some point, but it would be tricky to do so and not > break things for older installs. > > So if you get a chance, let me know if the new tests work on your > systems. Even better, if you have real workflow systems in a dev area, > let me know if anything is broken there. I'm going to continue testing > on my systems. > > Jim > > > -- Jim Brandt Administrative Computing Services University at Buffalo |