[slf4j-dev] [Bug 74] add getLevel() to Category in log4j-over-slf4j
bugzilla-daemon at pixie.qos.ch
bugzilla-daemon at pixie.qos.ch
Tue May 27 22:22:52 CEST 2008
http://bugzilla.slf4j.org/show_bug.cgi?id=74
------- Comment #8 from michael.newcomb at gdc4s.com 2008-05-27 22:22 -------
That is the problem, I'm using slf4j/logback in my code but a library I'm
required to use, requires log4j. I have no control over what methods they call
on the log4j api.
For a log4j-slf4j bridge to work in these situations, which would be the most
likely case (using a library that requires log4j).
I don't think that a getLevel() that returns getAssignedLevel() would have dire
consequences on a client of the log4j api. The only time something would appear
odd would be if a client called setLevel() then a call to getLevel() would not
obey the contract...
If that is really bad, then maintain a Level and return the result of
setLevel()...
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the slf4j-dev
mailing list