Oh, and for some context, the JndiContextSelector can be useful if you
install your log4j2.xml config into JNDI and make it available throughout
your cluster. Then you don't even need to copy the file to each deployment
(and could potentially update it at runtime as well without, again,
redeploying
>From what I remember, you can add log4j-api and log4j-core (and any other
logging bridges) to your EE server's shared lib folder (or install as a
module in JBoss for example), though if it's all in one ear, you could just
make it a normal library in there.
As for a shared configuration, you can p
