[JS2-947] Properly handling container invocation errors like processAction throwing an unexcepted exception and displaying a meaningful message to the end user

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.0
• Component/s: Container
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 31/Mar/09 09:59
• Updated: 04/Oct/11 21:08
• Resolved: 07/May/09 00:48

Description

For example in the ActionValveImpl, we trap all exceptions (except PortletContainerException) thrown by the container invocation, only log them, and then simply invoke with the next Valve...
For example with a NPE thrown like currently in the the JSF-Demo when you click on the Root tree node, the following meaningless end message is shown on the page:

Portlet is Not Available: jsf-demo::guessNumber
Reason: null

I think we either should come up with a pluggable ErrorHandlingValve or else send a response error (which then could be "trapped" itself with a configured error handling page in web.xml)