The configs are maintained per-LoggerRepository. The scope of this depends
on the RepositorySelector implementation that you are using. The default
selector uses classloaders as its scoping mechanism, and thus does work with
the way you want in servlet containers which use seperate classloaders for
each defined web app;ication.
|-----Original Message-----
|From: Lutz Michael [mailto:[EMAIL PROTECTED]]
|Sent: Friday, January 10, 2003 8:54 AM
|To: 'Log4J Users List'
|Subject: Quick question on "the scope of Log4j's
|configuration settings"
|
|
|
|
|Thanks in advance for any feedback.
|
|My organization has a non-negotiable requirement to
|support many customers
|on a given machine. The J2EE servlet standard has rules
|specifying how each
|web application in a servlet container owns its own class
|loader. Thus, in
|the same JVM process space, we are able to support
|multiple customers
|running multiple versions of our code.
|
|The question deals with Log4j's ability to be configured
|differently for
|such customers, given the fact that they may be running in
|the same JVM
|process space, but under different web applications.
|
|So the question is - when Log4j is configured, what is the
|scope of the
|configuration settings? I've looked through the
|documentation (which is
|excellent) and couldn't find this answer (maybe the answer
|is implied and I
|just didn't get it). Is the scope the entire JVM process
|space, thus
|disallowing our scenario? ... or following Ceki's servlet-based
|configuration pattern
|(http://jakarta.apache.org/log4j/docs/manual.html), in
|a servlet world (and if we include the Log4j jar's in each
|Web application),
|can we isolate the effect of configuring Log4j to distinct
|Web applications
|even though they run in the same JVM space?
|
|I'm thinking the question really comes down to - (a) how does Log4j
|internally maintain config settings (statics?), and (b)
|what is the effect
|from a scope perspective of this approach - e.g. can we
|isolate down to the
|web application level inside a single JVM space and
|servlet container.
|
|This question is very important to my organization, thanks
|for your time.
|
|Mike
|
|-----------------------------------------------------------
|--------------------
|This message and any included attachments are from Siemens
|Medical Solutions
|Health Services Corporation 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
|[EMAIL PROTECTED] Thank you
|
|--
|To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
