Hema,
The log4j logging configuration *within* jetspeed can/is only be used for *within* the jetspeed context. While the current configuration file still contains definitions for struts, myfaces etc., this is obsolete since we removed the global commons-logging and log4j jars (in $Tomcat/shared/lib for example).
For your own portlet applications you must provide your own logging setup like putting log4j (and commons-logging if you want) in WEB-INF/lib and also provide your own log4j.properties/xml in WEB-INF/classes.
I'm going over the jetspeed log4j.properties right now and will clean out several of these obsolete definitions as they definitely give the wrong signal. Thanks for bringing this up ;-) It'll be another small improvement of the M2 release.
Remark: I do think it would be nice if we *could* provide a generic logging service for the portlet applications, but without getting into classloader problems on different platforms, right now I don't have a solid solution ready (although I have an idea which might work but it'll have to wait for now).
Regards, Ate
Hema Menon wrote:
I wanted to enable the logging for struts portal bridges. I added a new log4j category for org.apache.portals with DEBUG level and also added a logfile definition . I find the log file is created but is empty. Forgive my ignorance, but is there some other configurations that I am missing? Any help very much appreciated.
Thanks, Hema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hema Menon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
