You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Marius Bauer (JIRA)" <ji...@apache.org> on 2010/11/30 13:56:11 UTC
[jira] Created: (WICKET-3207)
Localizer.substitutePropertyExpressions() is called twice when
Localizer.getString() is called
Localizer.substitutePropertyExpressions() is called twice when Localizer.getString() is called
----------------------------------------------------------------------------------------------
Key: WICKET-3207
URL: https://issues.apache.org/jira/browse/WICKET-3207
Project: Wicket
Issue Type: Bug
Affects Versions: 1.4.13
Reporter: Marius Bauer
When you call getString() on a component this component calls Localizer.getString(). This method then calls Localizer.getStringIgnoreSettings() which calls Localizer.substitutePropertyExpressions() for the first time. The return value of getStringIgnoreSettings() is then again passed to substitutePropertyExpressions().
Actually I'm not sure if this is a bug or if this is desired behaviour, but it can lead to problems if you throw an Exception when a resource cannot be found and the value that is put into a string is, for whatever reason, in the format ${foobar}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3207)
Localizer.substitutePropertyExpressions() is called twice when
Localizer.getString() is called
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-3207.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M4
Assignee: Juergen Donnerstag
thanks
> Localizer.substitutePropertyExpressions() is called twice when Localizer.getString() is called
> ----------------------------------------------------------------------------------------------
>
> Key: WICKET-3207
> URL: https://issues.apache.org/jira/browse/WICKET-3207
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.4.13
> Reporter: Marius Bauer
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M4
>
>
> When you call getString() on a component this component calls Localizer.getString(). This method then calls Localizer.getStringIgnoreSettings() which calls Localizer.substitutePropertyExpressions() for the first time. The return value of getStringIgnoreSettings() is then again passed to substitutePropertyExpressions().
> Actually I'm not sure if this is a bug or if this is desired behaviour, but it can lead to problems if you throw an Exception when a resource cannot be found and the value that is put into a string is, for whatever reason, in the format ${foobar}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.