I haven't gotten any help on my initial question, but I have found more info. In
the class JspCompilationContext, the constructor munges the incoming URI to
enforce a trailing '/':
this.baseURI = jspUri.substring(0, jspUri.lastIndexOf('/') + 1);
// hack fix for resolveRelativeURI
if (baseURI == null) {
baseURI = "/";
} else if (baseURI.charAt(0) != '/') {
// strip the basde slash since it will be combined with the
// uriBase to generate a file
baseURI = "/" + baseURI;
}
if (baseURI.charAt(baseURI.length() - 1) != '/') {
baseURI += '/';
}
There is similar code in other places in the class, so I am not sure which one
is specifically responsible for my problem yet. Unfortunately, when running from
Windows, this screws any paths that are entered in source code, by placing an
extra '/' at the end of the compile path. Any idea how I can get around this?
Shouldn't the code be using the path.separator property?
--
Bradford Holcombe
c/o Triveni Digital
40 Washington Road
Princeton Junction, NJ 08550
609.716.3504
[EMAIL PROTECTED]
www.trivenidigital.com
AIM: colbadhombre (aim:AddBuddy?ScreenName=colbadhombre)
Yahoo!: bradfordholcombe
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
