Hi,
I have two applications running on a Bea Weblogic. The first one is a
dbforms 1.1.3 application, the second one uses just some servlets.
I have to deploy the dbforms-app in a war. Thus it is not possible to use
the "log4j.configuration" parameter in the web.xml because the
ConfigServlet.initLogging() method fails trying to get the right configURL
(getServletContext().getRealPath("/") returns null in a war). As a workaround I
commented the
log4j.configuration parameter out and moved the log4j.properties to
WEB-INF/classes (which is the first location where log4j looks for its configuration
file if nothing is specified).
That workaround works fine as long the dbforms-app runs alone on the
Weblogic (and Tomcat). But weird things happen when my second application runs on
the same server:
The log4j configuration of the dbforms-app is ignored and the application
writes its logs into the log4j-logfile of the second application (i.e the
dbforms-applicaton uses the log4j.properties of the second application)!
I don't know what's going on... Do you know another "workaround". Have you
ever experienced similar problems? Any ideas?
Thanks,
Jan.
--
NEU F�R ALLE - GMX MediaCenter - f�r Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gru�, GMX FotoService
Jetzt kostenlos anmelden unter http://www.gmx.net
+++ GMX - die erste Adresse f�r Mail, Message, More! +++
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
