You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Lutz Michael <mi...@siemens.com> on 2003/06/11 16:50:41 UTC
seeking guidance - wrapping Log4j
I receive regular questions from internal customers asking why it is
recommended to wrap Log4j through aggregation as opposed to inheritance.
I am familiar with the ClassCastException issue found in
http://jakarta.apache.org/log4j/docs/TROUBLESHOOT.html#cce.
I have purchased the Log4j Full Manual, and will search for information in
this regard. I've noted there is a section in the book covering wrapping
Log4j.
In addition, would someone please comment on the technical reasons
aggregation is recommended, as opposed to sub-classing?
Thanks for your time.
Mike
-------------------------------------------------------------------------------
This message and any included attachments are from Siemens Medical Solutions
USA, Inc. and are intended only for the addressee(s).
The information contained herein may include trade secrets or privileged or
otherwise confidential information. Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful. If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to CSOffice@smed.com. Thank you
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org