the state of our ruby workflow engine (2)
An enumeration of points on the current development status of our open source Ruby workflow and bpm engine, like done previously.
* almost all of the OpenWFE expressions got implemented. There are some variations, for example, in OpenWFEja, there was a <do> expression for tagging a block of code for further undo/redo operations. Now all expressions can be tagged with the ‘tag’ attribute.
* OpenWFEru is not limited anymore to XML expressed process definitions, it now understands processes defined as Ruby classes (like in the quickstart for example), this allows for interesting process definitions ‘macros’ in Ruby.
* it’s a pure open source Ruby workflow engine, developed on “ruby 1.8.5 (2006-12-25 patchlevel 12) [i686-darwin8.8.3]“, tests on JRuby (0.9.9) seem promising, there seem to be only an issue when safe levels are set.
* a simple and effective persistence implementation is now in place. It stores process instances and workitems in files using YAML. Other implementation are being planned, there will most likely be something with ActiveRecord, but nothing sure for now.
* a process journaling system is integrated into OpenWFEru, replaying processes is possible. The current weak point for this system is documentation, it’s an advanced technique, the ‘replay’ aspect is hard to explain in an easy way.
* a mini web application for viewing process definitions in a graphical way has been written, it could make its way into the source repository soon. It’s Rails based.
* there is a fair amount of documentation, of course, contributions are welcome.
* I’ve been receiving lots of request for a Rails integration, but no help actually (con
tributesume), I’ll probably start exploring that myself, earning my Rails dev badge on the way.
There are lots of other small things, but this is sufficient for now.
I’ll probably release 0.9.9 this week.