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=18477>. 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=18477 JspC: unable to precompile linked jsp files ------- Additional Comments From [EMAIL PROTECTED] 2003-12-05 16:21 ------- We have the same problem in our development environment. I wanted to precompile our JSPs (for performance), but our version control system creates all files in the workarea as symbolic links to another area of the disk hence our JSPs couldn't be compiled. (As an aside it also got thrown by the JARs in WEB- INF/lib being symbolic links as well). I remember there was an earlier bug (#12049) related to symbolic links and security seemed to be the problem (which I can understand, in a real webapp you wouldn't want symbolic links to other parts of the disk where files could be tampered with), but for standalone precompilation it shouldn't be a problem. I would have thought that Tomcat (or whatever server you are using) should really handle the issue of symbolic links being allowed or not but I'm not that well up on it really. I found 3 places in JspC.java that were using getCanonicalPath() that caused me problems - initClassLoader() for the JARs, locateUriRoot() only used if you don't specify -uriRoot, execute() where the pathnames for the JSPs are converted to URIs relative to uriRoot. I've patched our system locally to allow us to compile these links (security isn't a problem since its only for precompiling in our development area), I'll tidy that up a bit and submit it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
