[
https://issues.apache.org/jira/browse/MYFACES-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070123#comment-13070123
]
Martin Kočí commented on MYFACES-3053:
--------------------------------------
I will commit some patches for this area - but only new classes for the new
exception handling and logging infrastructure. If change in current codebase
needed, I'll attach it as patch for discussion first. When we resolve this
issue completely, we can backport result to 2.0 branch.
> Improve error reporting and logging
> -----------------------------------
>
> Key: MYFACES-3053
> URL: https://issues.apache.org/jira/browse/MYFACES-3053
> Project: MyFaces Core
> Issue Type: Improvement
> Components: General
> Reporter: Martin Kočí
> Priority: Minor
>
> See http://www.mail-archive.com/[email protected]/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.)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
