> The Java compiler used by Tomcat doesn't have any > problems compiling the > sources that are currently being generated. What > compiler are you trying > to use that has problems with it? That's where your > problem really > appears to lie. >
Yes, because the magic class loader has the tricky work done. Still, the package name of the generated class and the directory it resides are not consistent. It makes debug impossible. Here's what Sysdeo - a tomcat plugin for eclipse, says how to debug jsp. (http://www.sysdeo.com/eclipse/tomcatPlugin.html) Workaround 1 : install our Tomcat 4.x patch. Workaround 2 (from Gabriel Krupa) : if your jsp is /myjspdir/myjsp.jsp, generated servlet will be in work/org/apache/jsp/myjspdir, change package definition from org.apache.jsp to org.apache.jsp.myjspdir, to debug your jsp access it from your browser with the following URL : http://myhost:8080/myapplication/servlets/org.apache.jsp.myjspdir.myjsp$jsp Workaround 3 : use Tomcat 3.3 (servlet 2.2 and JSP 1.1), with Tomcat 3, package definition is compliant with file location. Yunfeng Hou _________________________________________________________ Do You Yahoo!? 新鲜到底,娱乐到家 - 雅虎推出免费娱乐电子周报! http://cn.ent.yahoo.com/newsletter/index.html -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
