[
https://issues.apache.org/jira/browse/LOG4J2-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916392#comment-13916392
]
Russell J. Nile commented on LOG4J2-554:
----------------------------------------
I am poking around for something like that. We are using WildFly and have a
lot of jboss variables that point to the basic location....but I am looking for
something a tad more elegant. In this case my application would have to know
about how the appserver is going to deploy it (although it is a pretty safe
assumption). It would look like this for me:
${jboss.server.base.dir}/deployments/CTMSApplicationServices.war/WEB-INF/config/log4j2.xml.
The use of the Servlet context may work...but then there is some web-app
specific notion inside log4j...dunno if that is something you want to avoid.
> No easy way to point to a configuration file in the WEB-INF folder
> ------------------------------------------------------------------
>
> Key: LOG4J2-554
> URL: https://issues.apache.org/jira/browse/LOG4J2-554
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-beta9
> Environment: WildFly 8.0.0, JDK 1.7.0_45, WIn7
> Reporter: Russell J. Nile
> Priority: Minor
>
> I am trying to put all of my configuration files under WEB-INF/config folder
> but there is no way (other than an explicit reference to my file system) to
> set the log4jConfiguration to point to that. It also does not report any
> errors when it can't find the file log4jConfiguration (unless there is a URI
> reference error) so you are scratching your head when it does nothing.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
