http://bugzilla.slf4j.org/show_bug.cgi?id=51
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Comment #2 from [EMAIL PROTECTED] 2007-06-25 21:32 -------
Hi Robert,
SLF4J indeed restricts the type of the message to String instead of Object.
This restriction paves the way for parameterized logging which is not possible
when the message type is Object.
For logging systems such as logback that natively implement the SLF4J API, you
can write
logger.debug("{}", myObject);
Logback has access to myObject directly and your custom appender could handle
it
as an object instead of string.
As there are technical reasons for the SLF4J being the way it is, I am afraid I
cannot fix this bug.
My apologies for the inconvenience,
--
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.
_______________________________________________
dev mailing list
[email protected]
http://www.slf4j.org/mailman/listinfo/dev
