Uploaded image for project: 'MyFaces Core'
  1. MyFaces Core
  2. MYFACES-738

Exceptions thrown during processing of EL statements are not displayed with the underlying cause, and there is no log message.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 1.1.0
    • None
    • None
    • None

    Description

      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.

      Attachments

        1. 738.patch
          0.9 kB
          Nikolay Petrov

        Activity

          People

            Unassigned Unassigned
            cwrm Andrew Harris
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: