http://bugzilla.slf4j.org/show_bug.cgi?id=71
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Comment #2 from [EMAIL PROTECTED] 2008-07-30 13:53 -------
Only marking the logger references as transient is not enough.
Deserialized instances would throw NPEs immediately. The transient logger
reference must also be created lazily like in JCL.
I fear the lack of that lazy-init concept is an overall design weakness of
SLF4J. All org.slf4j.Logger implementations (eg. Log4jLoggerAdapter) have these
two problems:
- not Serializable
- eager binding to the actual logging system instead of lazy creation
This makes it impossible to use non-static loggers in serializable classes at
all. Please reconsider the current architecture, it is a severe con against
JCL.
--
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
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
