Joern Huxhorn created LOG4J2-179:
------------------------------------
Summary: Logger interface is lacking methods for logging at
variable level
Key: LOG4J2-179
URL: https://issues.apache.org/jira/browse/LOG4J2-179
Project: Log4j 2
Issue Type: Improvement
Affects Versions: 2.0-beta4
Reporter: Joern Huxhorn
The interface org.apache.logging.log4j.Logger contains the method boolean
"isEnabled(Level level)" which is very nice.
I would have expected it to also contain the following methods:
boolean isEnabled(Level level, Marker marker);
void log(Level level, Marker marker, Message msg);
void log(Level level, Marker marker, Message msg, Throwable t);
void log(Level level, Marker marker, Object message);
void log(Level level, Marker marker, Object message, Throwable t);
void log(Level level, Marker marker, String message);
void log(Level level, Marker marker, String message, Object... params);
void log(Level level, Marker marker, String message, Throwable t);
void log(Level level, Message msg);
void log(Level level, Message msg, Throwable t);
void log(Level level, Object message);
void log(Level level, Object message, Throwable t);
void log(Level level, String message);
void log(Level level, String message, Object... params);
void log(Level level, String message, Throwable t);
(i.e. every method defined for an explicit level but just with an Level as the
first argument)
That way it would be easier to log at a variable level in cases where the level
to be used can only be determined at runtime.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
