> From: Mikolaj Rydzewski [mailto:m...@ceti.pl] > Subject: Re: JNDI: Name java:comp is not bound in this Context > > So I rather think, that Tomcat fills JNDI information > after webapp deployment.
Not really after, just during. I'm still looking through the code, but the logger for the webapp is initialized very early in the process, which makes sense. > But anyway, why does log4j initialization takes place > before JNDI context is ready? The JNDI context is specific to the webapp; if errors occur during its population, having the webapp's logger around to record them would be beneficial. One or the other has to come first, and the spec gives no guidance with respect to loggers, so it appears Tomcat chose to initialize the webapp's logger first. Seems quite reasonable to me. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
