[
https://issues.apache.org/jira/browse/WICKET-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540185#comment-14540185
]
Martijn Dashorst commented on WICKET-5906:
------------------------------------------
It appears that the constructor refactor of Wicket 7 for StringResourceModel
allows the code to bind a String parameter (which was a possible default value
in 6.19.0) now as an optional parameter, causing the default to be considered
null, and wrecking havoc.
> Use default on missing resource does not work
> ---------------------------------------------
>
> Key: WICKET-5906
> URL: https://issues.apache.org/jira/browse/WICKET-5906
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0-M5
> Reporter: Martijn Dashorst
> Fix For: 7.0.0-M6
>
>
> A regression since 6.19.0: when a StringResourceModel tries to lookup a key,
> but that key doesn't exist in any of the resource bundles, it should use the
> default if one is provided (and the setting is enabled in Wicket's
> ResourceSettings), but currently throws an exception, or returns a string
> with a warning that the resource could not be found.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
