http://bugzilla.slf4j.org/show_bug.cgi?id=142
Ceki Gulcu <lis...@qos.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #2 from Ceki Gulcu <lis...@qos.ch> 2009-07-29 11:57:55 ---
>Would it be possible to improve the Serialization implementation of
>SLF4JLocationAwareLog either retrieve the LocationAwareLogger on
>readResolve() or simply check for a null logger instead of throwing an
>NPE?
Upon de-serialization, the readResolve() method in the
SLF4JLocationAwareLog class returns fully initialized logger
[1]. There is also a test case checking for correct
serialization/de-serialization [2].
Since the NPE is a given. You are either using an older version of
slf4j on one or the other side of serialization. Alternatively, the
SLF4J bindings are not the same, e.g. slf4j-simple on one end and
slf4j-log4j one the other end of serialization.
Given the information available thus far, I suspect that the issue is
with your setup rather than a bug in SLF4J. However, I might be
wrong.
[1]
http://slf4j.org/xref/org/apache/commons/logging/impl/SLF4JLocationAwareLog.html
[2]
http://slf4j.org/xref-test/org/apache/commons/logging/impl/SerializationTest.html
--
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
