[MYFACES-3053] Improve error reporting and logging

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Component/s: General
• Assignee: Unassigned
• Reporter: Martin Kočí
• Created: 22/Feb/11 14:20
• Updated: 28/Jun/22 14:50
• Resolved: 28/Jun/22 14:50

Description

See http://www.mail-archive.com/[e-mail]/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.)

Sub-Tasks

• Handing exception (in exception handler) from render response phase with forward/redirect is inconsistent: Open