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
--- Jem Mawson <[EMAIL PROTECTED]> wrote:
> Thanks iksrazal
>
> So you've reversed the problem by calling Init prior
> to initialising the
> correct configurator, thereby overwriting the
> xml-security configuration
> with your own. Is this right?
More or less. I prefer to do the xml-security In
Thanks iksrazal
So you've reversed the problem by calling Init prior to initialising the
correct configurator, thereby overwriting the xml-security configuration
with your own. Is this right?
I still have my doubts about the xml-security library requiring its own
log4j configuration. Can anyone c
--- Jem Mawson <[EMAIL PROTECTED]> 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 con
