Sekhar Vajjhala wrote on 10/19/09 09:38:
> Bill Shannon wrote:
>> Sekhar Vajjhala wrote on 10/16/09 13:32:
>>> Bill Shannon wrote:
>>>> How do you know if a message is *supposed* to have a message id?
>>> The assumption I am making is that all messages in the file being
>>> analyzed
>>> (e.g. LogStrings.properties) must have a message id .
>>
>> But that's not true.
> The serviceability page
> http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV3LoggingServiceability
>
> states that Any SEVERE, WARNING, INFO messages must have a message ID .
Yes, that's true, but it's not clear that all messages in that file
are such messages.
> The page
> http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV3LoggingMessageFormat
>
> states that all messages in LogStrings.properties must have a message ID.
I believe that overstates the requirement.
> The diag.cause.* and diag.check.* messages don't are not required to have a
> message ID, but these are already filtered out by the tool.
>
> So, what other messages can be in resource bundles /
> LogStrings.properties that
> are not required to have a message id ?
Non-error message output.
For example, when you start a domain, it produces output telling
you where the log file is, what port it's using, etc. I don't think
of this as error message output that needs a message ID, and yet it's
text that needs to be localized.
In addition, there are other items such as command usage messages,
descriptions of options, etc. that are not individual error messages
that should have a message ID, but rather are used to compose a larger
message.