http://bugzilla.slf4j.org/show_bug.cgi?id=79





--- Comment #16 from Ceki Gulcu <lis...@qos.ch>  2009-03-05 19:25:24 ---
(In reply to comment #12)
> 
> 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.

It looks like you have identified the problem quite precisely. Would you care
supplying a patch? 


-- 
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
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev

Reply via email to