Thank you Jake for your help. My options are now clear.
Jan
"Jacob Kjome" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Quoting jan_bar <[EMAIL PROTECTED]>:
>
> > Thanks for your extensive answer, see inline..
> >
> > > Well, when you are using a repository selector, the idea is t
Quoting jan_bar <[EMAIL PROTECTED]>:
> Thanks for your extensive answer, see inline..
>
> > Well, when you are using a repository selector, the idea is that you
> > have Log4j in a position where it is not part of your app, but part
> > of the server; otherwise there's no point to using a reposito
Thanks for your extensive answer, see inline..
> Well, when you are using a repository selector, the idea is that you
> have Log4j in a position where it is not part of your app, but part
> of the server; otherwise there's no point to using a repository
> selector. In order for a server wide ins
Well, when you are using a repository selector, the idea is that you
have Log4j in a position where it is not part of your app, but part
of the server; otherwise there's no point to using a repository
selector. In order for a server wide instance of Log4j to service
many apps without each o
Hi,
what is the purpose of the guard in setRepositorySelector()? I miss a
possibility to reset the LogManager repository selector to it's default
value (including resetting the guard). Why? I deploy my application in
JBoss. I want to have separate logging for my application so I use the
setReposit