You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Scott O'Bryan (JIRA)" <de...@myfaces.apache.org> on 2014/05/28 19:17:01 UTC
[jira] [Comment Edited] (TRINIDAD-2445) Prevent exceptions from
propagating out of the ServletFilter
[ https://issues.apache.org/jira/browse/TRINIDAD-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011332#comment-14011332 ]
Scott O'Bryan edited comment on TRINIDAD-2445 at 5/28/14 5:15 PM:
------------------------------------------------------------------
Silly question but I'm wondering WHY this was needed? The bug is not very informative.
was (Author: darkarena):
Silly question but I'm wondering WHY this was needed. The bug is not very informative.
> Prevent exceptions from propagating out of the ServletFilter
> ------------------------------------------------------------
>
> Key: TRINIDAD-2445
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2445
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: 2.1.1-core
> Reporter: Arjun Vade
> Assignee: Jeanne Waldman
> Fix For: 2.1.1-core
>
> Attachments: 17191718.patch
>
>
> Any exceptions from the Trinidad code that runs before JSF lifecycle that propagates to application server layer may result in the end user not seeing a meaningful error message in UI.
> Solution: Trinidad code that runs before the JSF lifecycle shouldn't allow exceptions to propagate out of the ServletFilter.
> The fix is simply to add code to our various ServletFilters to trap the errors at that point before the errors propagate out.
--
This message was sent by Atlassian JIRA
(v6.2#6252)