Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-2601

Exception handling - Improve the exception reporting with more context information

    Details

      Description

      Once we clean up #

      {exception}

      and #

      {handledException}

      (remove one...),
      we need to add more context information. I don't know how to do that
      so I don't have any recommendation how this could be implemented -
      only that I heard that Tapestry has good exceptions. What I need
      (especially now in production) is more information about the request
      that triggered the exception. For example, I want to be able to
      reproduce the exception by executing the same GET/POST request. So
      this needs to include request header/parameter information and
      information about the server-side state (is it a new session, etc). I
      need to be able to access that information in my exception handler and
      for production optionally have it logged. Without this, I need to rely
      on user error reports which so far have not resulted in a single
      bugfix of the wiki, because I can't reproduce what the users are doing.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  shane.bryzak Shane Bryzak
                • Votes:
                  4 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated: