You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Alastair Maw (JIRA)" <ji...@apache.org> on 2007/06/11 00:46:26 UTC
[jira] Updated: (WICKET-341) [Patch] AjaxServerAndClientTimeFilter
either throws an exception or displays a wrong text
[ https://issues.apache.org/jira/browse/WICKET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw updated WICKET-341:
--------------------------------
Fix Version/s: 1.3.0-beta3
Assignee: Alastair Maw
Need to make sure this isn't an issue for 1.3
> [Patch] AjaxServerAndClientTimeFilter either throws an exception or displays a wrong text
> -----------------------------------------------------------------------------------------
>
> Key: WICKET-341
> URL: https://issues.apache.org/jira/browse/WICKET-341
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 2.0 branch (discontinued)
> Reporter: Martin Benda
> Assignee: Alastair Maw
> Fix For: 1.3.0-beta3
>
> Attachments: AjaxServerAndClientTimeFilter.patch
>
>
> When IResourceSettings.getThrowExceptionOnMissingResource() is true (the default value), the AjaxServerAndClientTimeFilter throws MissingResourceException instead of displaying a default message "Server parsetime: X, Client parsetime: Y".
> Moreover, when "ServerAndClientTimeFilter.statustext" and "ajax.ServerAndClientTimeFilter.statustext" resource keys are defined, it does not throw the exception, but a wrong message is displayed --- ${servertime} and ${clienttime} variables in the resource string are not interpolated.
> The attached patch fixes both bugs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.