OpenWFE is a workflow engine. It is robust, extensible, and scalable. Access libraries for Python, Perl, and .NET make it easy to write custom interfaces or agents (automatic participants) for a workflow-enabled system.
Information regarding Project Releases and Project Resources. Note that the information here is a quote from Freecode.com page, and the downloads themselves may not be hosted on OSDN.
One important concept was introduced for stores: the
order in which they are instantiated in the worklist
configuration file is now the order in which they are
asked if they accept a workitem for a given
participant name. The first store to accept (by name
pattern matching) a workitem 'wins' it. The default
store is no longer 'Store.default', but the last
declared store. To follow this scheme, the example
Store.default was moved to the end of the release
store declarations. Various bugfixes were made.
This release fixed a few bugs and included patches
for the SqlWorkItemStore. A nasty bug that could
crash the worklist's JVM if too many workitems were
stored in each a thread was fixed. Given a certain
maximum limit, the current implementation will switch
to unthreaded storage operation. The ExpressionPool
(file version) storage tree was made a bit deeper to
have less files in the directories. The ControlSession
interface reached a more mature stage as pyya REST
tests were introduced for it.
This release introduces a lot of changes in the release tree
structure. The tree is less flat, there are fewer launch
scripts. The 'engine' package got fully qualified to
'openwfe.org.engine' instead of simply 'openwfe.org' which
was confusing and it induced another set of changes to the
configuration files. Control over REST got implemented so
that Python (and soon .Net) interfaces will be able to cancel
or freeze/unfreeze flow pieces.
The ExpressionPool and ExpressionStore were completely reorganized, with the latter now only caring about storage while the first now handles caching, control, and in the future, clustering. The Swis (Sql WorkItem Store) was changed to allow a more efficient extension. The 'cancel flow' and 'cancel expression' control actions now produce history log records.
The implementation of the engine control tools was
tightened. Cancelling a flow or just a participant
can be done through ./control.sh (or control.bat),
and participants may be frozen if the flow hasn't
reached them. The Web client and its flow diagram
display show the addition of the dispatch and
reply time, making it easier to spot what happened
to a flow and when it happened. The standard
(Java) reactor now supports reloading its Java
agents without having to be restarted.
