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

Don't set ADDED_AT and CONSTRUCTED_AT keys if components use checking is not enabled

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5.8, 6.0.0-beta3
    • Fix Version/s: 6.0.0, 1.5.9
    • Component/s: wicket
    • Labels:
      None

      Description

      A user reported that he sees stacktraces in the file that is used as a page store: http://markmail.org/thread/xywvuxc24kooyil4.

      The problem is that org.apache.wicket.settings.IDebugSettings#isLinePreciseReportingOnNewComponentEnabled() and/or org.apache.wicket.settings.IDebugSettings#isLinePreciseReportingOnAddComponentEnabled() returned 'true' but org.apache.wicket.settings.IDebugSettings#getComponentUseCheck() returned 'false'. In this case the constructed_at and added_at stacktraces were collected but later were not null-ified at org.apache.wicket.Page#onAfterRender().

        Attachments

          Activity

            People

            • Assignee:
              mgrigorov Martin Tzvetanov Grigorov
              Reporter:
              mgrigorov Martin Tzvetanov Grigorov
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: