You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Kamil (JIRA)" <ji...@apache.org> on 2015/01/25 21:12:35 UTC

[jira] [Updated] (WICKET-5820) StringResourceModel doesn't handle null values correctly

     [ https://issues.apache.org/jira/browse/WICKET-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kamil updated WICKET-5820:
--------------------------
    Description: 
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:
new StringResourceModel("my.resource.${my.propery}"), myModel);
one can expect the need to provide 'my.resource.null' resource key (same case as with DropDownChoice). 
In fact, Wicket is searching for 'my.resource.${my.propery}' (literarily) which is wrong.

  was:
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:
new StringResourceModel("my.resource.${my.propery}"), myModel);
one can expect to 'provide my.resource.null' resource key (same case as with DropDownChoice). 
In fact, Wicket is searching for 'my.resource.${my.propery}' (literarily) which is wrong.


> 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:
> new StringResourceModel("my.resource.${my.propery}"), myModel);
> one can expect the need to provide 'my.resource.null' resource key (same case as with DropDownChoice). 
> In fact, Wicket is searching for 'my.resource.${my.propery}' (literarily) which is wrong.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)