Re: Log4j configuration on Initialisation

[Berin Lautenbach]

Jem,

I just had a quick look at this.  I'd forgotten that Axl migrated all 
the logging to the commons-logging wrapper API some time back.

So 1.1 simply calls on commons logging objects, and the library does no 
configuration of any logging whatsoever.  Whatever you set up with log4j 
should work with v1.1 of the library.

(Note that 1.1 isn't strictly speaking released, but if you want to see 
what it should look like, have a look at 
http://xml.apache.org/security/1.1/ but note that it *may* change prior 
to public release, as it hasn't been fully reviewed yet.)

Cheers,
        Berin
Jem Mawson wrote:

Hello

I note that the Init class performs Log4j configuration using the
config.xml from within the xml-security.jar. This has the unfortunate
side-effect of removing any Log4j configuration that may have been set
from the application context.
Is it possible to avoid using the configurator if the rootlogger is
already configured with appenders? Or should the Log4j configuration only
occur in the test classes and be omitted from the xml-security library
proper?
Cheers
Jem