[EMAIL PROTECTED] wrote:
Sebastiaan van Erk [EMAIL PROTECTED] wrote:
2) It would be nice to have formatting of log messages as SLF4J has with
the MessageFormat api. In combination with varargs (java5); this makes
for a really flexible logging mechanism which makes the code much more
with the Object[]'s instead of varargs would
still be immensely useful though.
Just some thoughts,
Sebastiaan van Erk.
Boris Unckel wrote:
Hello,
I have seen the recent discussions on JCL 2.0.0 and a version without
autodiscovery.
Someone stated to stop any further development (with good reasons
[
http://issues.apache.org/jira/browse/LOGGING-110?page=comments#action_12450996
]
Sebastiaan van Erk commented on LOGGING-110:
I don't understand how this is something that cannot be implemented for certain
libraries
[
http://issues.apache.org/jira/browse/LOGGING-110?page=comments#action_12450998
]
Sebastiaan van Erk commented on LOGGING-110:
One more comment on the implementation using only the commons logging API
itself: this need only
Affects Versions: 1.0.4
Reporter: Sebastiaan van Erk
The Log API does not have a generic log method and there is no generic Level
class. Since the levels which commons logging provides are fixed and since it
would not break backwards compatibiliy I would like to suggest
.
Why are the 3 lines marked with the * necessary anyway? The very next thing
called after these lines is the _conn.close() method, which in the case of
a DelegatingConnection calls passivate() immediately anyway!
Greetings,
Sebastiaan van Erk
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED
