this is important for serviceability requirements. Other modules do
maintain these tags which are called message ids. The message ids and
corresponding messages will be displayed in by the admin console under
logviewer. See the following page for more info:
http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV3LoggingServiceability
I think that you are right that maintaining the message ids is a manual
process. There are a limited amount of message ids with corresponding
diagnostic messages in the resource bundles at this time. Abhijit has
asked me to follow up with folks and get more of this data in the
resource bundles, at least for SEVERE and WARNING messages. I think
that for SEVERE and WARNING messages these should be manageable. I know
that the support folks find this info very helpful.
carla
Bill Shannon wrote:
> Some of the error messages from the CLI include message numbers/tags,
> like "CLI128". It seems that the intent was that customers could look
> up this tag and get more information about the error.
>
> Is this still important?
>
> Is anyone other than the CLI maintaining these numbers/tags?
>
> Maintaining the numbers/tags is a fair amount of work, especially
> without any tools to help. And it's not clear that anyone is maintaining
> the corresponding message database.
>
> Should we continue with this? Can we afford it?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>