Message catalog formats, Elements of a log message catalog, Message catalog formats -5 – BEA WebLogic Server User Manual
Page 23: Elements of a log message catalog -5
Message Catalog Formats
Internationalization Guide
2-5
An example of a
method
attribute for the above message is as follows:
-method=“logNoFile(String name, String path)”
The message expects two arguments,
{0}
and
{1}
:
{0}
is used in the message body.
Both are used in the message detail.
Neither is used in the
<cause>
or
<action>
section.
In addition, the arguments are expected to be strings, or representable as strings.
Numeric data is represented as
{n,number}
. Dates are supported as
{n,date}
. You
must assign a severity level for log messages. Log messages are generated through the
generated
Logger
methods, as defined by the
method
attribute.
Message Catalog Formats
The catalog format for top-level and locale-specific catalog files is slightly different.
The top-level catalogs define the textual messages for the base locale. Locale-specific
catalogs only provide translations of text defined in the top-level version. Log message
catalogs are defined differently from simple text catalogs.
Elements of each of these types of catalogs are described in the following sections:
Elements of a Log Message Catalog
Elements of a Simple Text Message Catalog
Elements of a Locale-Specific Catalog
Elements of a Log Message Catalog
This section provides reference information for the following elements of a log
message catalog: