Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1369

ExceptionUtils.findCause() does not use the same approach as ExceptionAnalyzer

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 5.2.4
    • 5.3
    • tapestry-ioc
    • None

    Description

      findCause() only works using the cause property, whereas in many cases (older code typically that predates the cause property, introduced in JDK 1.4)) there's an alternate property that stores the actual nested exception.

      ExceptionAnalyzer does it correctly, at higher cost (lots of property access to identify the cause).

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            hlship Howard Lewis Ship
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: