I have realized the problem now. The difference between what the user is doing in that link is that he is deploying inside an EAR. I have several EARs which I would like to all share logging configurations. Therefore, I am deploying my jboss-logging.xml file at the root level. This is probably the same level that the current jboss-logging.xml file exists on. Perhaps I can not override the already existing logging xml with my own. Does anyone know if it is possible? Will I have to deploy a jboss-logging.xml with each of my EARs to get the result I am looking for?
1 of 1 people found this helpful
Why not add your configurations to the existing JBOSS_HOME/server/<servername>/deploy/jboss-logging.xml since you want it to be shared with all your .ear applications?
I have done that since my original post. It works fine on my local machine. However, when I deploy the set of EARs to the dev box it will not be the only service deployed there. Therefore, I can not assume what levels the loggers should be set at for them.
Even if I can not change the loggers that arleady exist in the root jboss-logging.xml file it would be nice if I could simply add a logger to it or even better add an appender and a logger to it.
I realized that my previous statement does not make any since. If I change the levels of the root loggers then of course I would be changing for other services running on the AS.
I am still interested to know if it would be possible to add a logger for my app's domain to the root logger upon deployment.
The only options I see at this time is to include a jboss-logging.xml inside each of my EAR's or edit the jboss-logging.xml inside the JBoss deploy folder. Is that the only two options?