You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/09/19 17:27:24 UTC
[jira] Updated: (DERBY-1232)
MessageService.getLocalizedMessage(...) should check the validity of its
arguments
[ http://issues.apache.org/jira/browse/DERBY-1232?page=all ]
Rick Hillegas updated DERBY-1232:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> MessageService.getLocalizedMessage(...) should check the validity of its arguments
> ----------------------------------------------------------------------------------
>
> Key: DERBY-1232
> URL: http://issues.apache.org/jira/browse/DERBY-1232
> Project: Derby
> Issue Type: Improvement
> Components: Localization, Network Client, Network Server
> Affects Versions: 10.1.2.0
> Reporter: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.2.2.0
>
>
> MessageService.getLocalizedMessage(...) assumes that its third argument, String sqlerrmc, is tokenized. DERBY-1178 showed that it is easy to make a change that violates this assumption. Currently this is not detected because the resulting failures are masked and handled by falling back to (incorrect) defaults.
> It would be preferable if MessageService.getLocalizedMessage(...) could verify that the input is, in fact, a tokenized message, and provide an appropriate error message if isn't. Ideally it should also be more verbose, at least in debug builds, about failing to find the specified locale resources.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira