You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Steve Downey <st...@netfolio.com> on 2001/03/02 21:44:12 UTC

[PATCH] Bug 841 - JSPC stack fault on NT

Under NT (and presumably any OS where File.sep != '/') JspC has a stack
underflow at baseDirStack.peek() in ParserController.java. This patch
converts from '\' to '/' for those cases. It also sets the package name for
the class based on the URI, so that the java file is distinguished from
others with the same name.
 
 
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named.  Any use, copying or disclosure by any other person is strictly
prohibited.  If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>
  

Re: [PATCH] Bug 841 - JSPC stack fault on NT

Posted by Nick Holloway <Ni...@pyrites.org.uk>.
steve.downey@netfolio.com (Steve Downey) writes:
> Under NT (and presumably any OS where File.sep != '/') JspC has a stack
> underflow at baseDirStack.peek() in ParserController.java. This patch
> converts from '\' to '/' for those cases. It also sets the package name for
> the class based on the URI, so that the java file is distinguished from
> others with the same name.

The problem with '\' as the filename seperator instead of '/' also
causes problems with "<jsp:include>", relative paths and JspC (see
Bugzilla #412).

I suggested there that it might be possible to just convert the '\'
into '/' before passing into CommandLineContext (in JspC).  This is
really what happens when running within Tomcat -- the path passed into
JspEngineContext has '/', not the local file seperator.

Unfortunately, I don't have a patch, as I'm not organised enough to get
a build environment running so I can test.

-- 
 `O O'  | Nick.Holloway@pyrites.org.uk
// ^ \\ | http://www.pyrites.org.uk/