[ https://issues.apache.org/jira/browse/TRINIDAD-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880990#comment-13880990 ]
Jeanne Waldman commented on TRINIDAD-2445: ------------------------------------------ Sending content: C:\Trinidad\Trunk3\trinidad-impl\src\main\java\org\apache\myfaces\trinidadinternal\webapp\TrinidadFilterImpl.java Sending content: C:\Trinidad\Trunk3\trinidad-impl\src\main\java\org\apache\myfaces\trinidadinternal\config\xmlHttp\XmlHttpConfigurator.java Sending content: C:\Trinidad\Trunk3\trinidad-impl\src\main\xrts\org\apache\myfaces\trinidadinternal\resource\LoggerBundle.xrts Completed: At revision: 1561022 > 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: Archetype > 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.1.5#6160)