[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3355) SeamExpressionEvaluator gobbles up exceptions

Fri Jun 19 15:29:56 EDT 2009

    [ https://jira.jboss.org/jira/browse/JBSEAM-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12473083#action_12473083 ] 

Alexandros Karypidis commented on JBSEAM-3355:
----------------------------------------------

I arrived to this issue report from reading http://seamframework.org/Community/UsingJBPMELInSeam

According to that thread, this bug arose when trying to fix:

https://jira.jboss.org/jira/browse/JBSEAM-3250
https://jira.jboss.org/jira/browse/JBPAPP-1192

I am just adding this information so that whoever deals with this has a full picture of what the desired outcome is (i.e. to fix this while maintaining jBPM/Seam integration).

> SeamExpressionEvaluator gobbles up exceptions 
> ----------------------------------------------
>
>                 Key: JBSEAM-3355
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3355
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Wolfgang Schwendt
>            Priority: Critical
>
> Rev 8710 of org.jboss.seam.bpm.SeamExpressionEvaluator  introduced a serious bug.    If the  invocation of the method expression (me.invoke(...)) throws an exception such as org.jboss.seam.security.AuthorizationException, the SeamExpressionEvaluator  afterwards tries to evaluate the EL expression as a value expression.  This of course results in a second exception thrown: PropertyNotFoundException.    Consequently, the list "exceptions" has size > 2 (rather than just size==1), which results in SeamExpressionEvaluator throwing an ELException that does not wrap the exception which originally caused the method expression invocation to fail.
> The bug was introduced because, compared with earlier versions, the try/catch-blocks for the method expression and value expression evaluation were changed and are now wrong.   This is serious because it breaks the handling of any application exception thrown while evaluating the EL method expression, such as AuthorizationException.

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