Howdy,
>Cool. I'll check the stuff in and let you add the documentation. BTW,
do
>you agree with the packages I suggested? Ceki seemed to have some
>reservations with the o.a.l.appender package. What else should I use?
I don't have a problem with the package names, don't really care what
they are ;) Perhaps calling it org.apache.log4j.contrib.appender for
now and reconsidering later (if/when submitted into log4j core) will
appease your both? Or maybe org.apache.log4j.servlet.appender as this
really is only applicable to servlets.
>Yeah, I thought about this as well. I guess it is a matter of choosing
>something both unique and predictable. It has to be predictable if we
are
>going to add it to a configuration file. Maybe we could just write the
>context path name and obtain it from getResource("/") like you
suggested,
>but format the result to be simply "MyContext". That way, we can just
>write the name of the context in configuration.
What configuration file are you referring to? I thought the map of
servlet context "name" (or hashcode etc.) to appender is going to exist
only in memory?
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
