[
https://issues.jboss.org/browse/WFLY-4439?page=com.atlassian.jira.plugin....
]
Gerry Matte commented on WFLY-4439:
-----------------------------------
UPDATE: After moving jboss-deployment-structure.xml from WEB-INF/classes up to WEB-INF,
and removing the tag add-logging-api-dependencies tag from standalone-full.xml, I
confirmed that the problem still occurs.
Although the server.log indicates that logback is being loaded with my webapp, my webapp
logging is not processed by logback. My application logging is handled by the logging
subsystem instead of logback.
I was required to re-insert the tag add-logging-api-dependencies tag into the logging
subsystem in standalone-full.xml. and also to rename the jboss-deployment-structure.xml
to jboss-deployment-structureXXX.xml
jboss-deployment-structure.xml does not exclude-subsystem named
logging
-----------------------------------------------------------------------
Key: WFLY-4439
URL:
https://issues.jboss.org/browse/WFLY-4439
Project: WildFly
Issue Type: Bug
Affects Versions: 8.2.0.Final
Environment: Microsoft Windows 7, Oracle JDK 7, Eclipse Luna
Reporter: Gerry Matte
Assignee: James Perkins
Priority: Minor
While attempting to use logback logging in a web application, I tried to use a
jboss-deployment-structure.xml in my WEB-INF/classes folder to exclude the logging
subsystem so that I could use logback configured in my webapp. UPDATE: After moving
jboss-deployment-structure.xml from WEB-INF/classes up to WEB-INF, and removing the
That method failed to prevent the logging subsystem from being excluded from my
deployment.
However, when I added the tag add-logging-api-dependencies value="false" to the
logging subsystem, logback began to work.
I'm not sure if this solution would cause problems with other webapps - I would have
preferred to use jboss-deployment-structure.xml instead so as to make the smallest change
to my wildfly configuration.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)