db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1232) MessageService.getLocalizedMessage(...) should check the validity of its arguments
Date Thu, 20 Apr 2006 11:50:05 GMT
MessageService.getLocalizedMessage(...) should check the validity of its arguments
----------------------------------------------------------------------------------

         Key: DERBY-1232
         URL: http://issues.apache.org/jira/browse/DERBY-1232
     Project: Derby
        Type: Improvement

  Components: Localization, Network Server, Network Client  
    Versions: 10.1.2.0    
    Reporter: Dyre Tjeldvoll
    Priority: Minor
     Fix For: 10.2.0.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