about processes and engines

The road to 1.7.0

I’m switching OpenWFE from 1.6.x to 1.7.x. I was pissed off by some ‘hacks’ I had in it for ‘flat sequences’. There will be less code, thus less bug probabilities.

Switching from 1.6.3pre3 to 1.7.0pre0 means that some things won’t be backward compatible between those two versions of OpenWFE.

The 1.6.x line has a <sequence> implementation that is flattened : Children of a sequence expression are directly [doubly-]linked to their previous and next.

So what happens to your installed 1.6.x engine and its long-running process instances ? If you didn’t use any sequence (which I doubt) you could safely migrate to the 1.7.0 main line.
You could also stop your OpenWFE suite, switch the <sequence> from FlatSequenceExpression to SequenceExpression and run again until there are no more process instances running ‘flat’.

(grep -r ‘Next’ work/engine/pool/ or something like that)

I will anyway branch 1.6.3 to allow bugs on that line to get fixed without requiring anybody to upgrade. But 1.7.0 is and will be way better.

1.7.0’s engine is 4k less than the 1.6.2 one.

Written by John Mettraux

March 15, 2006 at 9:09 pm

Posted in openwfe, technical

One Response

Subscribe to comments with RSS.

  1. I think the best way to migrate to a new version of the engine is to install a second engine, since openWFE allows that. Then the client code will have to use the new engine for launching new flows, while the old flows continue to run on the old engine. Result: no headaches, hopefully.


    April 4, 2006 at 3:34 pm

Comments are closed.

%d bloggers like this: