OpenWFE 1.3.1 released

OpenWFE 1.3.1 tightened the implementation of the engine control tools. 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 webclient and especially its flow diagram display shows the addition of the dispatch and reply time, making it easier to spot what and when happened to a flow.

The standard (java) reactor now supports reloading its java agents without having to get restarted.

OpenWFE 1.3.1 - released 2004/07/19

- [engine] established rule : "only unapplied participant expressions
may be frozen". This will perhaps change, after user feedback.
- [engine] task #85883 : implemented the 'cancel case'. A whole workflow
instance may be cancelled.
- [engine] task #85882 : implemented 'cancel activity'. A [participant]
expression may be cancelled.
- [engine] bug #992385 : cancel a flow didn't remove its root expression.
Fixed.
- [doc] task #99897 : drawn roadmap for project.
- [webclient] bug #990022 : cancelling during launch item lead to dead end white
screen. Fixed.
- [droflo] task #101850 : now display the dispatch time in droflo display
for the current participant.
- [droflo] task #101801 : droflo in display mode shows reply time for
participants.
- [engine] task #100303 : implemented full getStatus() for XmlExpressionStore
service.
- [reactor] task #101746 : recompiled java agents (in reactor-scripts/) are
automatically reloaded (especially useful in their test phase).
- [engine] task #101701 : implemented 'cancelx' command for engine control
- [engine] task #101702 : renamed control command 'unfreeze' to 'unfreezex'