[ http://issues.apache.org/jira/browse/MYFACES-738?page=comments#action_12356351 ]
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
