From jira-events at lists.jboss.org Thu Apr 22 11:47:11 2010
Content-Type: multipart/mixed; boundary="===============5411327566368313060=="
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>

--===============5411327566368313060==
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

--===============5411327566368313060==--

From jira-events at lists.jboss.org Thu Apr 22 11:51:10 2010
Content-Type: multipart/mixed; boundary="===============3961731895165995201=="
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] Updated: (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:51:10 -0400
Message-ID: <718867414.1271951470541.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 541563850.1271951231143.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com

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


     [ https://jira.jboss.org/jira/browse/JBPM-2854?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:all-tabpanel ]

Toshiya Kobayashi updated JBPM-2854:
------------------------------------

    Attachment: JBPM-2854.patch


patch for GraphElement and ExceptionHandlerTest

> If exception handlers are defined in multiple nodes, only the first one i=
s 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
>         Attachments: JBPM-2854.patch
>
>
> If you run a process definition below with ExceptionActionHandler which t=
hrows IllegalArgumentException, the first exception will be handled by the =
first 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 Exe=
cutionContext.exception can be cleared after handling the exception. Then a=
voiding loop and using multiple exception handlers will be achieved at a ti=
me. =

> =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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node1 Exception =
Handler 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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node2 Exception =
Handler 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

--===============3961731895165995201==--

From jira-events at lists.jboss.org Tue May 25 17:38:54 2010
Content-Type: multipart/mixed; boundary="===============5394173558480074475=="
MIME-Version: 1.0
From: Alejandro Guizar (JIRA) <jira-events at lists.jboss.org>
To: jbpm-issues at lists.jboss.org
Subject: [jbpm-issues] [JBoss JIRA] Assigned: (JBPM-2854) If exception
 handlers are defined in multiple nodes,
 only the first one is triggered during one execution
Date: Tue, 25 May 2010 17:38:54 -0400
Message-ID: <464729922.3978.1274823534888.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 541563850.1271951231143.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com

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


     [ https://jira.jboss.org/browse/JBPM-2854?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:all-tabpanel ]

Alejandro Guizar reassigned JBPM-2854:
--------------------------------------

    Assignee: Alejandro Guizar


> If exception handlers are defined in multiple nodes, only the first one i=
s triggered during one execution
> -------------------------------------------------------------------------=
--------------------------------
>
>                 Key: JBPM-2854
>                 URL: https://jira.jboss.org/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
>            Assignee: Alejandro Guizar
>             Fix For: jBPM 3.2.10
>
>         Attachments: JBPM-2854.patch
>
>
> If you run a process definition below with ExceptionActionHandler which t=
hrows IllegalArgumentException, the first exception will be handled by the =
first 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 Exe=
cutionContext.exception can be cleared after handling the exception. Then a=
voiding loop and using multiple exception handlers will be achieved at a ti=
me. =

> =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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node1 Exception =
Handler 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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node2 Exception =
Handler 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       =20

--===============5394173558480074475==--

From jira-events at lists.jboss.org Tue May 25 17:38:55 2010
Content-Type: multipart/mixed; boundary="===============8620519877905496746=="
MIME-Version: 1.0
From: Alejandro Guizar (JIRA) <jira-events at lists.jboss.org>
To: jbpm-issues at lists.jboss.org
Subject: [jbpm-issues] [JBoss JIRA] Updated: (JBPM-2854) If exception handlers
 are defined in multiple nodes,
 only the first one is triggered during one execution
Date: Tue, 25 May 2010 17:38:54 -0400
Message-ID: <1501797851.3979.1274823534926.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 541563850.1271951231143.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com

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


     [ https://jira.jboss.org/browse/JBPM-2854?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:all-tabpanel ]

Alejandro Guizar updated JBPM-2854:
-----------------------------------

    Fix Version/s: jBPM 3.2.10


> If exception handlers are defined in multiple nodes, only the first one i=
s triggered during one execution
> -------------------------------------------------------------------------=
--------------------------------
>
>                 Key: JBPM-2854
>                 URL: https://jira.jboss.org/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
>            Assignee: Alejandro Guizar
>             Fix For: jBPM 3.2.10
>
>         Attachments: JBPM-2854.patch
>
>
> If you run a process definition below with ExceptionActionHandler which t=
hrows IllegalArgumentException, the first exception will be handled by the =
first 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 Exe=
cutionContext.exception can be cleared after handling the exception. Then a=
voiding loop and using multiple exception handlers will be achieved at a ti=
me. =

> =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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node1 Exception =
Handler 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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node2 Exception =
Handler 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       =20

--===============8620519877905496746==--

From jira-events at lists.jboss.org Thu Aug 12 21:22:49 2010
Content-Type: multipart/mixed; boundary="===============9119909756883527317=="
MIME-Version: 1.0
From: Alejandro Guizar (JIRA) <jira-events at lists.jboss.org>
To: jbpm-issues at lists.jboss.org
Subject: [jbpm-issues] [JBoss JIRA] Resolved: (JBPM-2854) If exception
 handlers are defined in multiple nodes,
 only the first one is triggered during one execution
Date: Thu, 12 Aug 2010 21:22:49 -0400
Message-ID: <723868340.26369.1281662569201.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 541563850.1271951231143.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com

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


     [ https://jira.jboss.org/browse/JBPM-2854?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:all-tabpanel ]

Alejandro Guizar resolved JBPM-2854.
------------------------------------

    Resolution: Done


> If exception handlers are defined in multiple nodes, only the first one i=
s triggered during one execution
> -------------------------------------------------------------------------=
--------------------------------
>
>                 Key: JBPM-2854
>                 URL: https://jira.jboss.org/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
>            Assignee: Alejandro Guizar
>             Fix For: jBPM 3.2.10
>
>         Attachments: JBPM-2854.patch
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> If you run a process definition below with ExceptionActionHandler which t=
hrows IllegalArgumentException, the first exception will be handled by the =
first 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 Exe=
cutionContext.exception can be cleared after handling the exception. Then a=
voiding loop and using multiple exception handlers will be achieved at a ti=
me. =

> =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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node1 Exception =
Handler 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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node2 Exception =
Handler 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       =20

--===============9119909756883527317==--

From jira-events at lists.jboss.org Thu Aug 12 21:22:49 2010
Content-Type: multipart/mixed; boundary="===============5646002459986517134=="
MIME-Version: 1.0
From: Alejandro Guizar (JIRA) <jira-events at lists.jboss.org>
To: jbpm-issues at lists.jboss.org
Subject: [jbpm-issues] [JBoss JIRA] Updated: (JBPM-2854) If exception handlers
 are defined in multiple nodes,
 only the first one is triggered during one execution
Date: Thu, 12 Aug 2010 21:22:49 -0400
Message-ID: <30608075.26368.1281662569131.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 541563850.1271951231143.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com

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


     [ https://jira.jboss.org/browse/JBPM-2854?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:all-tabpanel ]

Alejandro Guizar updated JBPM-2854:
-----------------------------------

     Original Estimate: 0 minutes
    Remaining Estimate: 0 minutes


GraphElement now clears the exception from the ExecutionContext after handl=
ing it, allowing ExecutionContext to handle further exceptions.

> If exception handlers are defined in multiple nodes, only the first one i=
s triggered during one execution
> -------------------------------------------------------------------------=
--------------------------------
>
>                 Key: JBPM-2854
>                 URL: https://jira.jboss.org/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
>            Assignee: Alejandro Guizar
>             Fix For: jBPM 3.2.10
>
>         Attachments: JBPM-2854.patch
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> If you run a process definition below with ExceptionActionHandler which t=
hrows IllegalArgumentException, the first exception will be handled by the =
first 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 Exe=
cutionContext.exception can be cleared after handling the exception. Then a=
voiding loop and using multiple exception handlers will be achieved at a ti=
me. =

> =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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node1 Exception =
Handler 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.&qu=
ot;);
>                         </script>
>                         <action class=3D"com.test.action.ExceptionActionH=
andler"></action>
>                 </event>
>                 <exception-handler exception-class=3D"java.lang.IllegalAr=
gumentException">
>                         <script>
>                                 System.out.println(&quot;node2 Exception =
Handler 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       =20

--===============5646002459986517134==--