db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1232) MessageService.getLocalizedMessage(...) should check the validity of its arguments
Date Wed, 06 Dec 2006 14:56:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1232?page=all ]

Rick Hillegas updated DERBY-1232:
---------------------------------

    Fix Version/s: 10.2.3.0
                       (was: 10.2.2.0)

Move to 10.2.3.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.1
>            Reporter: Dyre Tjeldvoll
>            Priority: Minor
>             Fix For: 10.2.3.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

        

Mime
View raw message