[
https://issues.apache.org/jira/browse/WICKET-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-5386.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.12.0
7.0.0
> ChainingModel should not check if the modelObject given as argument is null
> ---------------------------------------------------------------------------
>
> Key: WICKET-5386
> URL: https://issues.apache.org/jira/browse/WICKET-5386
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.11.0
> Reporter: Frédéric Donckels
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 7.0.0, 6.12.0
>
> Original Estimate: 20m
> Remaining Estimate: 20m
>
> In Wicket 1.5.x there was no check against the null value of the target of a
> CompoundPropertyModel.
> This allowed to define a CPM based on a possibly value, then being able to
> refer to sub-properties of that value in through labels included in the
> markup without fearing a NullPointerException, nice empty labels would be
> displayed instead.
> Now that CPM has been refactored, null values are explicitly rejected, but
> only in the constructor.
> Changing the model through a call to setObject doesn't check the null value
> and allows the previous behaviour to work again.
> (another workaround is to pass Model.of(value) in the constructor).
> These are workarounds, the check itself adds no value and removes
> functionality.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
