logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <pbened...@apache.org>
Subject Re: log4j2.xml in EAR
Date Mon, 03 Nov 2014 21:38:41 GMT
Well I have the classes loading now. I still can't find my log4j2.xml but
at least the "api" and "core" libraries are being exposed to my application.

Okay, so to test this, make sure your "api" and "core" libraries are set to
"provided" scope in Maven. You don't want them already bundled; we want to
use the single copy installed in Wildfly.

My module file looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.3" name="org.apache.log4j2">
        <resource-root path="log4j-api-2.1.jar"/>
        <resource-root path="log4j-core-2.1.jar"/>
        <module name="javaee.api" />

It seems "core" is dependent upon JMX and other EE APIs; so I had to
include a dependency. We can probably figure out which EE modules are
really needed (and slim down), but I don't have the time to prune -- so I
included everything EE.

Next was my jboss-deployment-structure.xml. I have to export the log4j
libraries so my EJB modules can see them:

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
      <module name="org.apache.log4j2" export="true" />

This is where my JBoss/Wildfly knowledge fails me. I don't know why I need
export="true" but I do.

So the only thing left now is to find the log4j2.xml file. Stay tuned.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message