[
https://issues.apache.org/jira/browse/WICKET-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Quenot resolved WICKET-210.
-----------------------------------------
Resolution: Fixed
> Fixing DisabledComponentTest
> ----------------------------
>
> Key: WICKET-210
> URL: https://issues.apache.org/jira/browse/WICKET-210
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Jean-Baptiste Quenot
> Priority: Minor
> Attachments: 20070113-wicket-1.x-DisabledComponentTest
>
>
> -------------------------------------------------------------------------------
> Test set: wicket.DisabledComponentTest
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.281 sec <<<
> FAILURE!
> testDisabled(wicket.DisabledComponentTest) Time elapsed: 0.024 sec <<<
> ERROR!
> java.lang.NullPointerException
> at wicket.Component.getRequest(Component.java:1066)
> at wicket.Page.mayTrackChangesFor(Page.java:1337)
> at wicket.Page.componentStateChanging(Page.java:1068)
> at wicket.Component.addStateChange(Component.java:2300)
> at wicket.Component.setEnabled(Component.java:1872)
> at
> wicket.DisabledComponentTest.testDisabled(DisabledComponentTest.java:53)
> The attached patch ensures that Page.mayTrackChangesFor() returns false when
> there is no current RequestCycle.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
