[
https://jira.jboss.org/jira/browse/DNA-581?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-581:
-----------------------------------
One way to do this is to change the I18n class to have, in addition to the localized
message, a locale-independent and immutable "event code". Thus, the I18n
framework could not only find in a bundle the localized messages for a given local but
also to look up the code in another resource file (one that doesn't change with
locale). Basically, this can have the same property-file format as the localization
files, except that the value should be the code. To match other
JBoss.org projects, the
code should be of the form "<SYSTEM>-<EVENT_CODE>", where
"<SYSTEM>" is a unique name of the system that is at most 6 characters
(e.g., "MODES" for ModeShape) and "<EVENT_CODE>" is a 5-digit,
leading zero-padded unique number for the message (e.g., "00001"). I would
recommend breaking the 100K-1 range of event codes into ranges for each of our subsystems,
so "01XXXX" might apply to our graph subproject, "02XXXX" might apply
to the JCR implementation, "11XXXX" might apply to a particular connector (and
"1XXXXX" would apply to all connectors), etc.
Alter logging to use categories and message codes
--------------------------------------------------
Key: DNA-581
URL:
https://jira.jboss.org/jira/browse/DNA-581
Project: DNA
Issue Type: Task
Components: Common
Affects Versions: 0.7
Reporter: Randall Hauch
Fix For: 1.1
Our logging facility should use message codes that can be used to cross-reference more
information about the message and possible actions to alter the behavior. The logging
should also use categories rather than just using class names.
Ideally this can be done such that the only changes are to the logging class and the I18n
library, and that all other code remains untouched. (Though we'll have to record for
each subproject the message codes in a file so they're durable and documented.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira