[
https://issues.apache.org/jira/browse/WICKET-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Meier resolved WICKET-5820.
--------------------------------
Resolution: Fixed
Fix Version/s: 7.0.0-M5
null is now interpolated as 'null' in the resourceKey.
As we don't know whether applications are depending on the previous
interpolation with variableNames, we can't change this for 6.x though.
Thanks!
> improve StringResourceModel's resource key interpolation for null
> -----------------------------------------------------------------
>
> Key: WICKET-5820
> URL: https://issues.apache.org/jira/browse/WICKET-5820
> Project: Wicket
> Issue Type: Improvement
> Reporter: Kamil
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 7.0.0-M5
>
> Attachments: TestCase_WICKET_5820.java, fix-WICKET-5820.patch,
> fix-WICKET-5820_other_approach.patch
>
>
> When using StringResourceModel one can add property expression into the
> resourceKey.
> As documentation states: expression will be evaluated if the model parameter
> is not null.
> But when parameter *is null*, with given example:
> {code}
> new StringResourceModel("my.resource.${my.propertyValue}"), myModel);
> {code}
> one can expect the need to provide
> {code}
> my.resource.null
> {code} resource key (same case as with DropDownChoice).
> In fact, Wicket is searching for
> {code}
> my.resource.${my.propertyValue}
> {code} (*literarily*) instead which is just wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
