db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Halley Pacheco de Oliveira (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1376) File java/engine/org/apache/derby/loc/messages_en.properties - Message XSLAT.D
Date Tue, 06 Jun 2006 21:57:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1376?page=comments#action_12415058 ] 

Halley Pacheco de Oliveira commented on DERBY-1376:

Hi Suresht,

Reading the text of the message I couldn't devise the concern about the directory belonging
to other database.

By this reason, I liked what David Van Couvering wrote in Derby Developers discussion list
(Re: DERBY-1376 - Text for exceptions - File java/engine/org/apache/derby/loc/messages_en.properties):

"At one project in Sun you actually had an API that *required* you to provide the error messages,
the probable cause, and a recommended course of action as three separate messages."

Using this guideline for writing error messages, the message could be:

Error message: Log directory {0} exists.
Probable cause: Maybe the directory belongs to other database.
Recommended course of action: Make sure specified logDevice location is correct.

So, using this guideline what is missing in the text of the message is the probable cause.


> File java/engine/org/apache/derby/loc/messages_en.properties - Message XSLAT.D
> ------------------------------------------------------------------------------
>          Key: DERBY-1376
>          URL: http://issues.apache.org/jira/browse/DERBY-1376
>      Project: Derby
>         Type: Improvement

>   Components: Localization
>     Versions:
>  Environment: Text for exceptions
>     Reporter: Halley Pacheco de Oliveira
>     Priority: Minor
>      Fix For:

> The message XSLAT.D (String LOG_SEGMENT_EXIST = "XSLAT.D";) states:
> XSLAT.D=Log directory {0} exists. Please make sure specified logDevice location is correct.
> But it seems by the source code that the problem is not that this directory exists, but
the fact that it is not empty (// make sure log directory is empty, in LogToFile.java). So
it seems to me that the following message would be better:
> XSLAT.D=Log directory {0} is not empty. Please make sure specified logDevice location
is correct.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message