[
https://issues.jboss.org/browse/JBSEAM-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622020#comment-12622020
]
Marek Novotny commented on JBSEAM-3355:
---------------------------------------
I just tried to understand what you want, but I can't. The "serious bug" with
not throwing original? Original exception is logged at DEBUG level, while it is
in exceptions list. Or you couldn't see it at DEBUG logs?
> SeamExpressionEvaluator gobbles up exceptions
> ----------------------------------------------
>
> Key: JBSEAM-3355
> URL: https://issues.jboss.org/browse/JBSEAM-3355
> Project: Seam 2
> Issue Type: Bug
> Affects Versions: 2.1.0.BETA1
> Reporter: Wolfgang Schwendt
> Priority: Critical
> Fix For: 2.3.0.ALPHA
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
