Hi -- I've been looking at the workflow component, and I think I must be misunderstanding something when it comes to the variable handlers.
In the ezcWorkflowExecution class, it looks like the saveToHandlers function is called in two functions: end() and suspend(). In the suspend function, just before saveToHandlers is called, all variables that have handlers associated with them are first unset. As a result, the saveToVariableHandlers function will not actually do anything on suspend. Is this correct? Also, I am planning on using the variable handlers to store workflow variables into their own database tables (rather than serialized into a single table) so that they can be accessed easily by the surrounding code (to view status flags, etc). However, the saveToVariableHandlers function does not pass the execution object (or the execution ID) to the variable handler, so I cannot identify to which workflow instance a particular variable belongs. To get around that, I am planning on extending the ezcWorkflowDatabaseExecution class to pass the execution object (or just the execution id) to the variable handler. Is it just that this is not how the variable handlers were meant to be used? Thanks very much --Martin -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
