Yes, I think they are, but the issue is that after a couple of catch
throws, the cause becomes the previous catcher rather than the
underlying reason for the failure. So there is originally a throwable
catch, that is caught and an EvaluationException thrown, which is caught
and another EvaluationException thrown, which wraps the previous one,
then this second EvaluationException is caught and another one thrown.
The end result is that the displayed error is just information about the
previous EvaluationException rather than the first one.
So maybe the issue is that because EvaluationException is a
RuntimeException, it is being caught and rethrown unnecessarily in
PropertyResolverImpl. Perhaps the try/catch blocks can catch and throw
the same exception, instead of creating a new one.
Alternatively, just a WARN log message at the first exception would make
debugging easier.
Regards Andy
-----Original Message-----
From: Martin Marinschek (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 30, 2005 5:48 PM
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (MYFACES-738) Exceptions thrown during
processing of EL statements are not displayed with the underlying cause,
and there is no log message.
[
http://issues.apache.org/jira/browse/MYFACES-738?page=comments#action_12
356351 ]
Martin Marinschek commented on MYFACES-738:
-------------------------------------------
But the Exceptions are (as far as I have looked through the code right
now) properly initialized with their corresponding init cause, right?
regards,
Martin
> Exceptions thrown during processing of EL statements are not displayed
with the underlying cause, and there is no log message.
>
------------------------------------------------------------------------
------------------------------------------------------
>
> Key: MYFACES-738
> URL: http://issues.apache.org/jira/browse/MYFACES-738
> Project: MyFaces
> Type: Bug
> Versions: 1.1.0
> Reporter: Andrew Harris
>
> Very difficult to identify exceptions that are thrown during
processing of EL statements, since all information is swallowed without
logging.
> org.apache.myfaces.el.PropertyResolverImpl.getProperty catches a
Throwable exception and creates a new EvaluationException
> This is then caught by
org.apache.myfaces.el.PropertyResolverImpl.getValue as a
RuntimeException and then throws a new EvaluationException.
> This is in turn caught by the
org.apache.myfaces.el.ValueBindingImpl.getValue method Exception catch
and another new EvaluationException is thown.
> The error message on the UI is "Exception:
javax.faces.el.EvaluationException: Cannot get value for expression
'#{erHandler.expectedReceipt.seqno}'" which has lost all trace of the
underlying exception.
> Would be better to have the information from the underlying exception
in the error message in the UI. If this is not practical, then a logged
message would greatly facilitate debugging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
