You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/05/07 14:58:16 UTC

DO NOT REPLY [Bug 19725] New: - jsp compiler fails on windows if context docbase is too long

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=19725>.
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=19725

jsp compiler fails on windows if context docbase is too long

           Summary: jsp compiler fails on windows if context docbase is too
                    long
           Product: Tomcat 4
           Version: 4.1.24
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: pcasado@absamail.co.za


On a windows OS, a long path in a docbase for a context configured in 
server.xml results in the following error when trying to compile a jsp file:

ERROR: Unable to compile class for JSP

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
    [javac] Since fork is true, ignoring compiler setting.
    [javac] Compiling 1 source file
    [javac] Since fork is true, ignoring compiler setting.
    [javac] javac: invalid flag: C:\Documents
    [javac] Usage: javac  
    [javac] where possible options include:
    [javac]   -g                        Generate all debugging info
    [javac]   -g:none                   Generate no debugging info
    [javac]   -g:{lines,vars,source}    Generate only some debugging info
    [javac]   -nowarn                   Generate no warnings
    [javac]   -verbose                  Output messages about what the compiler 
is doing
    [javac]   -deprecation              Output source locations where 
deprecated APIs are used
    [javac]   -classpath          Specify where to find user class files
    [javac]   -sourcepath         Specify where to find input source files
    [javac]   -bootclasspath      Override location of bootstrap class files
    [javac]   -extdirs            Override location of installed extensions
    [javac]   -d             Specify where to place generated class files
    [javac]   -encoding       Specify character encoding used by source files
    [javac]   -source          Provide source compatibility with specified 
release
    [javac]   -target          Generate class files for specific VM version
    [javac]   -help                     Print a synopsis of standard options



Here is my config that causes the error:

<Context path="/vendir" docBase="C:\Documents and Settings\Pablo Casado\My 
Documents\Projects\vendir\head\build-home" workDir="C:\Documents and 
Settings\Pablo Casado\My Documents\Projects\vendir\head\work\org\apache\jsp" />

Here is one that works for the same app:

<Context path="/vendir" docBase="C:\Documents and Settings\vendir" 
workDir="C:\Documents and Settings\work" />

So my guess is that large path length for the docBase/workDir is the cause for 
the error. The problem does not occur on my suse linux box with a similarly 
long path name.

Note that this error does not occur in Tomcat version 4.0.x, so it was 
introduced in 4.1.x

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