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/12/17 15:36:16 UTC

DO NOT REPLY [Bug 15442] New: - missing java package in compiled jsp according to jsp directory

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=15442>.
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=15442

missing java package in compiled jsp according to jsp directory

           Summary: missing java package in compiled jsp according to jsp
                    directory
           Product: Tomcat 4
           Version: 4.1.12
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: andreas.granzer@wave-solutions.com


We are using tomcat 4.0.6 with Jasper. When a JSP gets compiled in java source 
the package ist set to some prefix and the relative path of the jsp file to web-
root is used as java package. 
e.g.  package jsp_servlet._buecher._login;  public class __login extends ....

Tomcat 4.1.12 with jasper2 creates
package org.apache.jsp;  public class Login_jsp extends ...

Now we have serveral hundred JSP in different directories. Mapping them all to 
the same java package results in name clashes.
duplicate class: org.apache.jsp.Login_jsp

Why was ths behaviour changed and how can i come around this problem?

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>