Yes, the new release of the manual will cover wrappers. It should come out early next week or so.

At 09:20 13.11.2002 -0800, you wrote:
Thanks for the clarification.  So the existing book covers how to write a
'correct' wrapper class?  I was under the impression that this new
information was covered by a post-2003 manual.  Apologies for the
confusion...  -Dave

-----Original Message-----
From: Ceki Gülcü [mailto:ceki@;qos.ch]
Sent: Wednesday, November 13, 2002 2:10 AM
To: Log4J Developers List
Subject: Re: New Log4j book?




There is no "new" log4j book. I am just continuing to work on the existing
draft of the "complete manual." It is available here
http://jakarta.apache.org/log4j/docs/documentation.html (just click on the
image with the feathered dinosaur).

If you purchase the manual now you get all future updates. You can expect to
receive updates until early 2003 after which I will stop updating the
manual.

Hope this helps,

At 15:59 12.11.2002 -0800, you wrote:
>Ceki,
>
>Is there any ETA on your new Log4J book?  I'm struggling with some
>wrapper issues in a pretty complex project, and would be one of the
>first purchasers of the book.  :)  Are you looking for pre-release
>reviewers?  ;-)
>
>-Dave

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from others. --
Jon Postel, RFC 793



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

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

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



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

Reply via email to