We use Log4j in jboss without any incident--until recently. we just copy our log4j.properties into our conf directory: c:/projects/devtools/JBoss-2.4.6_Tomcat-4.0.3/jboss/conf/<our-app>
The problem arose (see my post from yesterday) when I attempted to use a custom renderer. Since Jboss initializes log4j when it starts up, it doesn't have access to the renderer defined in my application, i.e. classes in the WARs file aren't available yet to jboss. The solution I'm told is to make your classes available to JBOSS by modifying the start up script (run.bat/run.sh and adding your jar to JBOSS_CLASSPATH). This didn't work for me, however, though I haven't had time to investigate. It would follow that this will apply to any classes defined in the jboss configuration files--appenders, renderers, etc. -----Original Message----- From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 11:14 AM To: Log4J Users List Subject: Re: Final conclusion on how to use Log4J in JBoss Larry, The question is somewhat ambiguous because, as far as I know, JBoss itself uses log4j for its own logging. Can you please clarify your question? At 17:48 23.07.2002 +0200, Larry wrote: >Please could someone tell me if they have a working solution on how to >log using log4J in an EJB server. > >Is the conclusion to use JBoss's own logging? > >Thanks >Larry -- Ceki For complete log4j documentation, please see http://qos.ch/log4jBook.html -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
