[
https://issues.jboss.org/browse/WFCORE-878?page=com.atlassian.jira.plugin...
]
James Perkins commented on WFCORE-878:
--------------------------------------
I tested on WildFly 8.2.0.Final and 9.0.1.Final and the logging deployment unit processors
definitely weren't executed. I put my {{jboss-deployment-structure.xml}} in
{{WAR/WEB-INF}}.
{code:title=jboss-deployment-structure.xml}
<jboss-deployment-structure>
<deployment>
<!-- exclude-subsystem prevents a subsystems deployment unit processors running
on a deployment -->
<!-- which gives basically the same effect as removing the subsystem, but it
only affects single deployment -->
<exclude-subsystems>
<subsystem name="logging"/>
</exclude-subsystems>
</deployment>
</jboss-deployment-structure>
{code}
jboss-deployment-structure.xml does not exclude-subsystem named
logging
-----------------------------------------------------------------------
Key: WFCORE-878
URL:
https://issues.jboss.org/browse/WFCORE-878
Project: WildFly Core
Issue Type: Bug
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.15#6346)