You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2007/01/27 06:43:53 UTC
DO NOT REPLY [Bug 40784] - Level per user
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40784>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40784
genman@noderunner.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From genman@noderunner.net 2007-01-26 21:43 -------
One solution is to create your own Logger subclass and specify a new
LoggerFactory in your configuation that does the direct filtering checks that
you want. This is a new feature in 1.3. Essentially what you could do is
create a Logger that has a filter chain and has a method to evaluate if a
message will be logged.
Another is to utilize lazy initialization of your messages, i.e. by creating an
Object where Object.toString() renders the message.
Assuming one of these solutions is adequate, this will be closed in a few months
as INVALID.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org