Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: General
    • Labels:
      None

      Description

      See http://www.mail-archive.com/dev@myfaces.apache.org/msg50721.html

      And from http://wiki.java.net/bin/view/Projects/Jsf2RequirementsScratchpad:

      Better Error reporting, like what you get with Tapestry (also in
      JSR-252-EG, where it was said: any time there is an error in any
      part of the lifecycle, the user should see not just a cryptic stack
      trace, but also the component - including file and line number - that
      triggered the problem, the EL expression that was being evaluated -
      including the part of the EL expression that triggered the problem,
      etc. Diagnosability for state saving is also important. On this point,
      Gavin King wants to have centralized error handling, with an
      interception point, perhaps using navigation rules, to help handle
      errors.)

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Martin Kočí
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development