"The SLF4JLog and
SLF4JLocationAwareLog classes are now serializable solving
serialization problems encountered with certain libraries which
attempt to serialize JCL log instances."
www.slf4j.org/news.html
So why doesn't org.slf4j.Logger extend java.io.Serializable?
public class SLF4JLog
Implementation of org.apache.commons.logging.Log
interface which
delegates all processing to a wrapped org.slf4j.Logger
instance.
Right, it's definitely not OK if injected loggers just disappear after
passivation.
--
On Fri, Dec 11, 2009 at 11:37 AM, Dan Allen <dan.j.allen@gmail.com> wrote:
> In this case, is the transient keyword not sufficient? I guess the problem
> is injection won't happen again after the object is deserialized.
>
> Why does it always come down to loggers. Loggers are just killing Java. So I
> agree, it is rather embarrassing.
>
> -Dan
>
> On Fri, Dec 11, 2009 at 11:27 AM, Gavin King <gavin.king@gmail.com> wrote:
>>
>> This is kind-of embarrassing:
>>
>> http://www.seamframework.org/Community/InjectLoggerFromSlf4j
>>
>> We really *do* need static injection points....
>>
>> --
>> Gavin King
>> gavin.king@gmail.com
>> http://in.relation.to/Bloggers/Gavin
>> http://hibernate.org
>> http://seamframework.org
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
>
Gavin King
gavin.king@gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
_______________________________________________
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev