[
https://issues.apache.org/jira/browse/WICKET-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-4722.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.9
6.0.0
> Don't set ADDED_AT and CONSTRUCTED_AT keys if components use checking is not
> enabled
> ------------------------------------------------------------------------------------
>
> Key: WICKET-4722
> URL: https://issues.apache.org/jira/browse/WICKET-4722
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5.8, 6.0.0-beta3
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.0.0, 1.5.9
>
>
> 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().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
