Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In a web-module you can place the log4j.properties on the classpath and log4j’s default initialization procedure will use the config, same in a standalone app, no problems here.
I have though trouble getting it to work in the ejb-module (javaee 1.4) in a EAR-app without programmatic configuration.
So my question is, where to put the log4j.properties file in a ejb-module to avoid programmatic config?
You should be able to put the Log4J configuration file into the root of the EJB JAR archive. This should work fine.
However I recommend to configure the logging globally for the application server our are using. This makes more sense and you won’t run into any configuration conflicts this way.