http://bugzilla.slf4j.org/show_bug.cgi?id=79
Eric Vargo <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #12 from Eric Vargo <[email protected]> 2009-03-05 01:32:13 --- Hi guys, I've been seeing the same issue and have confirmed it is a deserialization issue with the jcl over slf4j SLF4JLocationAwareLog implementation. After looking through the source code (and reading bug #71), I can see that the logger instance variable is transient, but there is no accompanying readResolve method implementation. In contrast, logger implementations in the main slf4j packages, e.g. Log4jLoggerAdapter, extend MarkerIgnoringBase which extends NamedLoggerBase which implements an appropriate readResolve method to recreate a logger after serialization. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dev mailing list [email protected] http://www.slf4j.org/mailman/listinfo/dev
