You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "McEligot, Sean (contractor)" <Mc...@MTMC.ARMY.MIL> on 2002/06/19 15:16:52 UTC
RE: [PATCH] Bug 9462 make default initialization available as a p
ubli c method
> Making runDefaultInitialization callable from a public method
> is the same
> as exporting it. :-)
I don't understand your response. LogManager.runDefaultInitialization is
package private. Category.runDefaultInitialization is public. This doesn't
expose LogManager at all. If you wanted to get replace LogManager with a
different implementation, the callers of Category.runDefaultInitialization
would never know.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [PATCH] Bug 9462 make default initialization available as
a p ubli c method
Posted by Ceki Gülcü <ce...@qos.ch>.
Sorry, if I was not clear. The default intialization mechanism is an
internal log4j matter. It is not intended to be called directly by
users.
At 09:16 19.06.2002 -0400, you wrote:
> > Making runDefaultInitialization callable from a public method
> > is the same
> > as exporting it. :-)
>
>I don't understand your response. LogManager.runDefaultInitialization is
>package private. Category.runDefaultInitialization is public. This doesn't
>expose LogManager at all. If you wanted to get replace LogManager with a
>different implementation, the callers of Category.runDefaultInitialization
>would never know.
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>