Release notes for Piece_Flow 1.14.0 (stable)
Release Date: 2007-09-28
A new release of Piece_Flow is now available.
What's New in Piece_Flow 1.14.0
- Two new interfaces for the continuation server
- Two new interfaces for the continuation server have been available. One is Piece_Flow_Continuation_Service. The other is Piece_Flow_Continuation_Server. Piece_Flow_Continuation_Service is a service class which provides simple interfaces to access attributes of the active flow object and to get some information from flow executions. Users should use this class instead of Piece_Flow_Continuation from this release forward. Piece_Flow_Continuation_Server is a class which just provides the features for the continuation server only. Framework developers should use this class instead of Piece_Flow_Continuation from this release forward. Besides, Piece_Flow_Continuation has been deprecated.
- A Defect Fix
- A defect that caused the same cache to be used if the relative paths of the flow definition files are same even though the absolute paths of the files are different has been fixed.
See the following release notes for details.
Enhancements
- Added missing code for checking whether the flow execution has started or not to getCurrentStateName() and getPreviousStateName(). (Piece_Flow)
- Improved some error messages and comments. (Piece_Flow)
- Changed the visibility of isExclusive() to private. isExclusive() has been marked as deprecated. (Piece_Flow_Continuation)
- Refactored Piece_Flow_Continuation. It has been divided into some classes, and deprecated. (Ticket #30)
- Refactored Piece_Flow. (Ticket #32)
Defect Fixes
- Fixed the defect that caused the same cache to be used if the relative paths of the flow definition files are same even though the absolute paths of the files are different. (Ticket #34) (Piece_Flow_ConfigReader_Common)
