From jira-events at lists.jboss.org Thu Apr 22 11:47:11 2010
Content-Type: multipart/mixed; boundary="===============1328039200104851241=="
MIME-Version: 1.0
From: Toshiya Kobayashi (JIRA) <jira-events at lists.jboss.org>
To: jbpm-issues at lists.jboss.org
Subject: [jbpm-issues] [JBoss JIRA] Created: (JBPM-2854) If exception handlers
 are defined in multiple nodes,
 only the first one is triggered during one execution
Date: Thu, 22 Apr 2010 11:47:11 -0400
Message-ID: <541563850.1271951231143.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

--===============1328039200104851241==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

If exception handlers are defined in multiple nodes, only the first one is =
triggered during one execution
---------------------------------------------------------------------------=
------------------------------

                 Key: JBPM-2854
                 URL: https://jira.jboss.org/jira/browse/JBPM-2854
             Project: jBPM
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Runtime Engine
    Affects Versions: jBPM 3.2.8
            Reporter: Toshiya Kobayashi


If you run a process definition below with ExceptionActionHandler which thr=
ows IllegalArgumentException, the first exception will be handled by the fi=
rst exception handler and the second exception won't be handled --- will be=
 thrown as a DelegationException to the client.
This behavior was introduced by JBPM-1887 to avoid infinite loop. But Execu=
tionContext.exception can be cleared after handling the exception. Then avo=
iding loop and using multiple exception handlers will be achieved at a time=
. =


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

<process-definition  xmlns=3D"urn:jbpm.org:jpdl-3.2"  name=3D"sample">

        <start-state name=3D"start-state1">
                <transition to=3D"node1"></transition>
        </start-state>

        <node name=3D"node1">
                <event type=3D"node-enter">
                        <script>
                                System.out.println(&quot;node1 called.&quot=
;);
                        </script>
                        <action class=3D"com.test.action.ExceptionActionHan=
dler"></action>
                </event>
                <exception-handler exception-class=3D"java.lang.IllegalArgu=
mentException">
                        <script>
                                System.out.println(&quot;node1 Exception Ha=
ndler OK.&quot;);
                        </script>
                </exception-handler>
                <transition to=3D"node2"></transition>
        </node>

        <node name=3D"node2">
                <event type=3D"node-enter">
                        <script>
                                System.out.println(&quot;node2 called.&quot=
;);
                        </script>
                        <action class=3D"com.test.action.ExceptionActionHan=
dler"></action>
                </event>
                <exception-handler exception-class=3D"java.lang.IllegalArgu=
mentException">
                        <script>
                                System.out.println(&quot;node2 Exception Ha=
ndler OK.&quot;);
                        </script>
                </exception-handler>
                <transition to=3D"end-state1"></transition>
        </node>

        <end-state name=3D"end-state1"></end-state>

</process-definition>


-- =

This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
ps://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       =20

--===============1328039200104851241==--