You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2015/01/26 08:58:35 UTC
[jira] [Commented] (WICKET-5820) StringResourceModel doesn't handle
null values correctly
[ https://issues.apache.org/jira/browse/WICKET-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291552#comment-14291552 ]
Martin Grigorov commented on WICKET-5820:
-----------------------------------------
bq. Wicket is searching for {code} my.resource.${my.propertyValue} {code} (literarily) instead which is just wrong.
Why it is wrong? Wicket doesn't interpolate the resource keys. Where did you read that it should do it ?
> StringResourceModel doesn't handle null values correctly
> --------------------------------------------------------
>
> Key: WICKET-5820
> URL: https://issues.apache.org/jira/browse/WICKET-5820
> Project: Wicket
> Issue Type: Bug
> Reporter: Kamil
>
> 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)