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 2003/03/11 15:36:25 UTC
DO NOT REPLY [Bug 17878] New: -
JSPC not working properly with package names
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=17878>.
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=17878
JSPC not working properly with package names
Summary: JSPC not working properly with package names
Product: Tomcat 4
Version: 4.1.22
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper 2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: jakarta@trollingers.com
JSPC is creating .java files with package names based on directory structure,
but when I go to a jsp page via my web app it still wants the package to be
org.apache.jsp so I get an error will all jsp pages. If I set the package to
be "org.apache.jsp" in jspc then it just prepends that to the rest of the
package name so
/test/test.jsp becomes org.apache.jsp.test.test_jsp.java
is there a way around this without mapping all my jsp pages in the web.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org