[
https://issues.apache.org/jira/browse/LOG4J2-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729619#comment-13729619
]
Neale Upstone commented on LOG4J2-293:
--------------------------------------
Beta 8, as I said:
> Just updated my Log4j2 branch to beta8
Apols that I omitted to clarify that the linked Tomcat issue is a Servlet 2.5
issue, i.e. that I'm using 2.5 so fragments are not relevant.
I'm now confused. For some reason {{classloader:}} seemed to be the scheme
when I last looked and this seems to pick up the correct handler stepping
through the code, but your docs (which seem to be different from the ones I
remember) say {{classpath:}}.
Could you please read my bullets and confirm the expected behaviour when
{{getLogger()}} has already been called by another {{Listener}}? This silent
skipping of config is not helpful.
I'll check whether 1.2 exhibited that behaviour as you'll really need to jump
one way or the other on it: reconfigure or fail, not silently proceed with
defaults, as is happening at the moment.
> classloader URI scheme broken or insufficient when using Log4jContextListener
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-293
> URL: https://issues.apache.org/jira/browse/LOG4J2-293
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-beta7
> Reporter: Neale Upstone
> Assignee: Nick Williams
> Labels: documentation
>
> I'm trying to migrate to Log4j2, and things looked promising when I spotted
> Log4jContextListener.
> However, there are too many holes.
> Firstly, I tried using classpath: as a scheme, and nothing blew up, so I
> assumed I'd got it right.
> Then I *looked at the code* (which shouldn't be how we find out) and
> eventually discovered some code relating to a 'classloader' scheme.
> Still silent failure. It seems that the classpath is not being searched,
> perhaps just the WAR classloader, not the JARs in WEB-INF/lib.
> Next I tried omitting the / (i.e. using classloader:log4j2.xml) and got a
> NullPointerException.
> Can you please document what schemes are supported and what you expect them
> to do, and *not fail silently* when a configuration file is specified, but
> nothing happens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
