Hi Alex, > On October 26, 2007 4:45 PM Alexander Klink wrote:
> I've just committed a bit of workflow restructuring. The forked children > workflows now notify their parents when they are finished instead of > waiting for a client to poll for them. This should make things much > easier - especially on the online/offline separation front. > Could someone please check that the LDAP workflows still behave > correctly? I still don't have a test environment for that so I could not > test them. Everything else seems to work just fine, though ... Revision 1119 does not pass workflow tests ( see for example http://build0.cynops.de/openxpki_tests/server/1119_output.txt ). LDAP tests use some extra xml workflow configuration files which are also a subject to patch according to the restructuring proposed. This is one of the reasons why they fail too. But it looks like it is not the only reason and I am not sure about how to do it properly. It also concerns workflow-looping test (80_looping.t). Actually I am confused with the the configuration pattern in workflow_def_certificate_issuance.xml (lines 74-84): <state name="WAITING_FOR_CHILD"> <!-- = notify_parent_success --> <action name="child_finished_successfully" resulting_state="SUCCESS"> <condition name="all_wf_children_instances_finished"/> </action> <!-- = notify_parent_failure --> <action name="child_finished_failure" resulting_state="FAILURE"> </action> </state> Does it mean that the action "child_finished_failure" is always available in the state "WAITING_FOR_CHILD" ? Best regards, Petr Grogoriev ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
