logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject RE: NDC.DiagnosticContext bug ?
Date Mon, 25 Mar 2002 22:36:05 GMT

Can you send me a patch?

At 17:12 25.03.2002 -0500, you wrote:
>My aim isn't to serialize the NDC itself, but the NDC stack (obtained by
>calling NDC.cloneStack()).  The NDC Stack contains DiagnosticContext
>objects.  In the scenario you mentioned, I would have to extract the Stack
>from the NDC, then recursively get the DiagnosticContexts from the Stack,
>convert the DiagnosticContexts to Strings and then add the strings to a
>Collection for transport.  This is not an optimal solution because of the
>overhead involved in converting to Strings.  Furthermore, my intent is to
>inherit the Stack into another NDC after transport, and inheriting a Stack
>of Strings instead of DiagnosticContext objects will likely cause problems.
>
>
>The DiagnosticContext inner class is a pretty simple class.  I don't see any
>reason why it shouldn't be serializable.
>
>-----Original Message-----
>From: Ceki Gülcü [mailto:ceki@qos.ch]
>Sent: Monday, March 25, 2002 4:58 PM
>To: Log4J Users List
>Subject: Re: NDC.DiagnosticContext bug ?
>
>
>
>We do not serialize the NDC but it's string form. Isn't the string form
>enough for your needs?
>
>At 16:37 25.03.2002 -0500, you wrote:
> >Hello All,
> >
> >NDC (Nested Diagnostic Context) is a serializable class, but it's inner
> >class DiagnosticContext does not implement Serializable.  I am attempting
>to
> >serialize the NDC Stack object (which contains DiagnosticContext objects)
> >for transport and exceptions are being thrown because DiagnosticContext is
> >not serializable.
> >
> >I think this is a bug.  Please confirm and I'll submit a bug report.
> >
> >Regards..
> >
> >
> >***************************************************************
> >Confidentiality note: This e-mail contains information from the
> >GFI Group Inc. and/or its affiliates, including GFInet inc.,
> >that is confidential and/or legally privileged.   This
> >information is intended only for the use of the individual or
> >entity named on this e-mail.  This e-mail and its content may
> >not be reproduced or retransmitted without the express written
> >permission of The GFI Group.
> >***************************************************************
> >
> >
> >--
> >To unsubscribe, e-mail:
><mailto:log4j-user-unsubscribe@jakarta.apache.org>
> >For additional commands, e-mail:
><mailto:log4j-user-help@jakarta.apache.org>
>
>--
>Ceki
>
>My link of the month: http://java.sun.com/aboutJava/standardization/
>
>
>--
>To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>
>
>
>***************************************************************
>Confidentiality note: This e-mail contains information from the
>GFI Group Inc. and/or its affiliates, including GFInet inc.,
>that is confidential and/or legally privileged.   This
>information is intended only for the use of the individual or
>entity named on this e-mail.  This e-mail and its content may
>not be reproduced or retransmitted without the express written
>permission of The GFI Group.
>***************************************************************
>
>
>--
>To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

--
Ceki

My link of the month: http://java.sun.com/aboutJava/standardization/


--
To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>


Mime
View raw message