[
https://issues.apache.org/jira/browse/TRINIDAD-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011340#comment-14011340
]
Scott O'Bryan commented on TRINIDAD-2445:
-----------------------------------------
The reason I reopened this is because this is preventing other filters from
getting the errors if they go before the TrinidadFilter. Please provide a
description about what the issue is that this bug is trying to fix so that we
can assess how to keep this fix but also provide the logic that's needed by
another custom filter.
> 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)
