You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lenya.apache.org by bu...@apache.org on 2003/06/20 21:29:25 UTC

DO NOT REPLY [Bug 20967] New: - tomcat-specific path in WAR-file

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20967>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20967

tomcat-specific path in WAR-file

           Summary: tomcat-specific path in WAR-file
           Product: Lenya
           Version: HEAD
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: lenya-dev@cocoon.apache.org
        ReportedBy: A.Kuckartz@ping.de
                CC: lenya-dev@cocoon.apache.org


When starting Jetty with the current WAR file distribution this error is logged:

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: ..\..\build\tomcat\webapps\lenya\WEB-INF\logs\log
4j.log (The system cannot find the path specified)

The tomcat-specific path seems to come from log4j.properties:

log4j.appender.A1.File=../../build/tomcat/webapps/lenya/WEB-INF/logs/log4j.log

Is there an alternative for this path which is not servlet container specific?

---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org