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 2002/10/16 05:25:42 UTC
DO NOT REPLY [Bug 11891] -
JspC does not work for webapps
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=11891>.
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=11891
JspC does not work for webapps
------- Additional Comments From mbrodzia@erggroup.com 2002-10-16 03:25 -------
I am unclear as to whether this problem is approaching a resolution. I am also
suffering from the same issue in relation to the lack of class packaging for
files with the same name. Surely this is a prevalent problem, as a lot of
people must use 'index.jsp' throughout their directory structure.
The release notes for Tomcat 4.1 ($Id: RELEASE-NOTES-4.1.txt,v 1.21 2002/09/23
00:32:46 billbarker Exp $) refer to this bug, and indicate the fix as being
the '-webapp' option. I don't believe that this resolves the issue.
Whilst I can both precompile the classes into .java as well as compile
into .class using the compile="true" switch, this does not suffice for
deployment; I am deploying into JBoss 3.0.3 / Tomcat 4.1.12 bundle, and this
gets translated into the Apache directory structure. Because there are
several 'org.apache.jsp.index_jsp' class files located within different
directories in the WEB-INF/classes directory of the WAR file, this confuses the
class loader and stops deployment.
I believe that instead a fixed package which I believe is currently the case,
the generated code should contain packages that reflect the JSP directory
structure such as the following:
/index.jsp
Java file: com.my.package.index_jsp
Generated to: /generated/com/my/package/index_jsp.java
/hello/index.jsp
Java file: com.my.package.hello.index_jsp
Generated to: /generated/com/my/package/hello/index_jsp.java
instead of what currently happens, which is
/index.jsp
Java file: com.my.package.index_jsp
Generated to: /generated/com/my/package/index_jsp.java
/hello/index.jsp
Java file: com.my.package.index_jsp
Generated to: /generated/com/my/package/hello/index_jsp.java
Has somebody already contributed a patch to correctly package the generated
java source code (and when I say package, I reiterate that I mean 'package xxx'
within the Java source, not simply by locating the source in a sub-directory)?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>