[
https://jira.jboss.org/jira/browse/WBRI-214?page=com.atlassian.jira.plugi...
]
Takeshi Kondo commented on WBRI-214:
------------------------------------
Pete
Before starting a thread about this on slf4j-dev, I want
to know Pete's initial thoughts.
> what is the use case for splitting out the level?
After
commencing operations, I must not almost modify deploying module.
But if system down occurred, I want to look at specified log to investigate system down
cause. In this case , I change log level from debug to info.
> Why doesn't log4j categories and filters not provide enough
control?
Log4j categories and filters are configured by log4j.xml. so I think that
I don't need to control it.
Ceki
To start a thread about this, should I develop initial
thoughts proto type and send it to slf4j-dev?
Separate log message and log level from module.
-----------------------------------------------
Key: WBRI-214
URL:
https://jira.jboss.org/jira/browse/WBRI-214
Project: Web Beans
Issue Type: Feature Request
Reporter: Takeshi Kondo
Assignee: Takeshi Kondo
Attachments: logger_prototype.patch, slf4j-version-logger.patch
Under development , log message is used to dubug the program
So log message internationalization will be broaden the webbeans user base.
And it make easy to document log message.
Under operation, maybe only in Japan, Log message is used to trigger alert.
so I frequently change log level to prevent alert at the last minute operation.
--
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