Thanks..worked perfectly :) Also, Is there a way to not show the apache DEBUG messages(without the obvious log4j.properties Thresholod change..?)Nothing major, but it would be good not to see the apache DEBUG messages for my application?? I guess it will be removed when it goes out of beta. -hemanth
-----Original Message----- From: hemant [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 11:02 AM To: Struts Users Mailing List Subject: Re: Problem with Struts 1.1b1 and Log4J 1.2.4 One other thing, Make sure your Startup Servlet does not extend ActionServlet. I made it extend HttpServlet and the problem went away. Thanks hemant ----- Original Message ----- From: "hemant" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, July 02, 2002 11:54 AM Subject: Re: Problem with Struts 1.1b1 and Log4J 1.2.4 > Fabrice and Hemant > > I had this problem too but I overcame it the hard way. Many a times, its the > IDE that causes this kinda confusion. > > Here is what I did, I wrote a startup servlet that starts up logging , > creates the connection pools via poolman, and loads a few other things. > > step1: I loaded this startup servlet "prior" to loading the Action > Servlet.Please see my web.xml below: (<load-on-startup> number ) > step2: Remove log4j property files from your webapp. Let it pick it up from > your IDE environment. (I mean C:/program files/ibm/visual age /yada/yada) > step3: Make sure your WEB-INF/lib has the latest struts libraries. > > But yes, it was almost insulting that the LOG4J error would baffle us like > that. > > LOL > > later... > hemant > > > > //----------------------------------------------------- > <web-app> > <servlet> > <servlet-name>action</servlet-name> > <servlet-class>org.apache.struts.action.ActionServlet</servlet-class> > <init-param> > <param-name>debug</param-name> > <param-value>2</param-value> > </init-param> > <init-param> > <param-name>config</param-name> > <param-value>/WEB-INF/struts-config.xml</param-value> > </init-param> > <init-param> > <param-name>application</param-name> > <param-value>blah.blah...........ApplicationResources</param-value> > </init-param> > <init-param> > <param-name>detail</param-name> > <param-value>2</param-value> > </init-param> > <init-param> > <param-name>validate</param-name> > <param-value>true</param-value> > </init-param> > <load-on-startup>2</load-on-startup> > </servlet> > > > > > <!--Startup Manager--> > > <servlet> > <servlet-name>mpi_startup_manager</servlet-name> > <servlet-class>blah.blah............StartupManager</servlet-class> > <init-param> > <param-name>LOG4J_CONFIG</param-name> > <param-value>/blah/.blah.........../log4j.properties</param-value> > </init-param> > <load-on-startup>1</load-on-startup> > </servlet> > //----------------------------------------------------- > > > ----- Original Message ----- > From: "Hemanth Setty" <[EMAIL PROTECTED]> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Sent: Monday, July 01, 2002 8:53 PM > Subject: Problem with Struts 1.1b1 and Log4J 1.2.4 > > > > Hello, > > > > I have included both the Struts and Log4J packages in a webapp. Things > > worked fine when I was using Struts 1.0.2. After I got the latest beta > > realease of struts(1.1b1)..I get this error > > > > log4j:WARN No appenders could be found for logger > > (org.apache.commons.digester.Digester). > > log4j:WARN Please initialize the log4j system properly. > > > > Does anybody know why this occurs? After digging in a little bit I > realized > > its because of the common-digester.jar file that comes with the struts1.1? > > But why does this error show up? Should I just stick with 1.0.2 of struts > > until a full release of 1.1? > > > > -hemanth > > > > > > -- > > 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]> > -- 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]>
