Hi Alex, > On Monday, October 29, 2007 6:00 PM Alexander Klink wrote:
>> Revision 1119 does not pass workflow tests ( see for example >> http://build0.cynops.de/openxpki_tests/server/1119_output.txt ). > I believe this is due to the fact that IPC::ShareLite was not yet > installed on build0. The tests pass just fine on my Mac OS X development > box. 15_csr_and_certificate_issuance.t fails on FreeBSD with IPC::ShareLite installed. It says I18N_OPENXPKI_TRANSPORT_SIMPLE_CLIENT_READ_CLOSED_CONNECTION. Revision 1118 passes this test without any trouble. > >> 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). > The workflow looping test should be pretty obsolete after this change > anyhow, as we do not do looping anymore. > The looping test could be used to check whether the workflow forking and parent-children signaling works OK. >> Actually I am confused with 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" ? > Yes, any child may tell the parent that it failed at any time, which > will lead to the parent failing as well. On the other hand, the > child_finished_successfully activity is only available for the last > calling child - as no other child has notified failure, we assume > that they exited successfully. Thank you Alex, then I'll try to figure out why does LDAP fail. BTW could it be due to double describing <action name="notify_parent_success"... ( in workflow_activity_certificate_ldap_publishing.xml and in workflow_activity_certificate_issuance.xml ) ? Best regards, Petr Grigoriev ------------------------------------------------------------------------- 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
