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

Page#onInitialize called after an exception in the constructor of Page

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 6.11.0
    • 6.13.0, 7.0.0-M1
    • wicket
    • None
    • Linux

    Description

      Page#onInitialize is called when the constructor of Page throws an exception, i.e. when the Page is not initialized correctly. This can cause additional exceptions which are usually added to an error log even in cases in which the exception in the constructor is handled (by Wicket). This issue is possibly related to WICKET-5083.

      Another case of the problem occurs when setResponsePage(...) is used in the constructor to navigate away from a page that can't be initialized correctly.

      I'm attaching a quickstart.

      Attachments

        1. 5387.1.tar.gz
          20 kB
          Walter B. Rasmann
        2. 5387.tar.gz
          18 kB
          Walter B. Rasmann
        3. WICKET-5387.patch
          0.8 kB
          Martin Tzvetanov Grigorov

        Issue Links

        relates to

        Improvement - An improvement or enhancement to an existing feature or task. WICKET-5415 Do not initialize pages which were not rendered

        • Major - Major loss of function.
        • Resolved

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

          People

            mgrigorov Martin Tzvetanov Grigorov
            wicket.x.ttp Walter B. Rasmann
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment