Jetspeed 2
  1. Jetspeed 2
  2. JS2-947

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

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: Container
    • Labels:
      None

      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)

        Activity

        Hide
        Ate Douma added a comment -

        Fixed by leveraging the new RequestDiagnostics feature from JS2-992

        Show
        Ate Douma added a comment - Fixed by leveraging the new RequestDiagnostics feature from JS2-992

          People

          • Assignee:
            Ate Douma
            Reporter:
            Ate Douma
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development