From 4441ec37bad07f74c2e110f382dccbfd4a62f8bd Mon Sep 17 00:00:00 2001 From: Marco Rietveld Date: Fri, 31 May 2013 03:31:43 +0200 Subject: [PATCH] Fixed mistake in Chapter-ExceptionMgmt.xml --- .../en-US/Chapter-ExceptionMgmt/Chapter-ExceptionMgmt.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jbpm-docs/src/main/docbook/en-US/Chapter-ExceptionMgmt/Chapter-ExceptionMgmt.xml b/jbpm-docs/src/main/docbook/en-US/Chapter-ExceptionMgmt/Chapter-ExceptionMgmt.xml index 70b7c4b182..55a83e2b88 100644 --- a/jbpm-docs/src/main/docbook/en-US/Chapter-ExceptionMgmt/Chapter-ExceptionMgmt.xml +++ b/jbpm-docs/src/main/docbook/en-US/Chapter-ExceptionMgmt/Chapter-ExceptionMgmt.xml @@ -508,7 +508,7 @@ in the BPMN2, we set the signal to Error-code. When signalling the jBPM process engine with an event of some sort, you should keep in mind the rules for signalling process events. - Error events can be signalled by sending an "Error-" + <the errorCode + Error events can be signalled by sending an "Error-" + <the errorCode attribute value> value to the session. Signal events can be signalled by sending the name of the signal to the session.