big OSWF update

I've fixed/modified the exception handling in oswf to be a lot more 
useful/helpful. All exceptions are now checked, which means that any 
code calling oswf needs to catch them. This is the only thing that 
client code has to modify. The advantage is that you now get a lot more 
information about what actually went wrong, whether it's a store 
problem (StoreException), a factory problem (FactoryException), or 
something else (WorkflowException).

Also implemented is the auto action functionality. I think I''m missing 
something because this turned out to be simpler than I thought.

Basically an action can now have an optional 'auto' attribute, which 
can be true or false. If true, then when the workflow moves to its 
step, the auto actions are checked, the first one that matches is auto 
executed, and so on until we get to a state where no auto actions 
apply. I've added 4 test cases that illustrate how this works.

Please be aware that I do not need this functionality myself, so I 
don't know if I'm testing the use cases you guys are trying to 
implement. I'd be hugely grateful if people can write simple example 
auto action descriptors that aren't covered by the existing cases, so 
we can add them to the test suite, even better would be descriptors 
which show errors with the current implementation!

I'm sure there are some problem since so much code has changed, so 
please be patient and I promise it'll all be ironed out very quickly, 
assuming of course people who run into bugs report them promptly ;)

Existing projects shouldn't have any problems, I've tested this with 
JIRA's sourcecode as well as our own portal app which uses osworkflow 
quite a bit.



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com