DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28147>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28147 JasperException for jsp files that are symbolic links [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-04-02 18:23 ------- No, no, no. There resource, chError.jsp is local. Except that when compiling this project, this file is physically located in a different location, and referenced by a symlink. for example: > ls -l index.jsp chError.jsp --> ../common_files/chError.jsp For some reasons, Jasper treats a symbolic link file differently then a regular file. I have a good number of applications and all of them contain chError.jsp. I do not want to make copies of this file so I use symbolic link in each application to link chError.jsp to a common location. Jasper seems to have trouble with that. Once again, this is meant to be a local resource, not something outside of the application. I also don't know what you were referring to when you mentioned "allowLinking". I am using JspC with Jasper2. I don't see such an option documented. Thanks, --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
