Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-3806

Remove the possibility to configure ExceptionMapper

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.5-RC4
    • 1.5-RC5
    • wicket
    • None

    Description

      Currently there are two ways to react on thrown exception - ExceptionMapper and IRequestCycleListener#onException().
      Users should use IRequestCycleListener#onException(). The exception mapper is used as last resort when the exception is not recognized by Wicket to show the configured internal error pages.
      With this ticket we will remove the possibility to configure custom ExceptionMapper.

      Discussed with Igor in IRC.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mgrigorov Martin Tzvetanov Grigorov
            mgrigorov Martin Tzvetanov Grigorov
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment