Jsp-debugging: breakpoints wont work!

Question

hi,
i am trying to enable jsp-debugging with eclipse 3, lomboz 3.0.0 and tomcat 5.5.4 (both working
as an eclipse plugin).
What happens so far is:
i write an jsp using lomboz, the jsp is converted to a servlet and stored / copied to a folder
called j2src in the eclipse workspace (the folder j2src is created by lomboz).
if i now call the url http://localhost:8080/mywebmodule/jsptest.jsp the jsp is executed faultless
and in the j2src-folder the corresponding class file appears.
so, everything works fine, the problem that i now have, is that i can set breakpoints for debugging
purposes in eclipse in the generated servlet-file under j2src, but this breakpoints are simply ignored, which means the
servlet is fully executed regardless of where i set the breakpoints, and i really dont get it why, since
my tomcat works completely in the eclipse workspace.
do i have to configure the tomcat to enable jsp-debugging?
i thought i had already done so, here is my deployment descriptor:
<?xml version='1.0' encoding='utf-8'?>
<Context docBase="E:\development\tutorial\eclipse_3\eclipse\workspace\testproject2\testmodulezwei" path="/testmodule" reloadable="true" workDir="E:\development\tutorial\eclipse_3\eclipse\workspace\testproject2\j2src" debug="0"/>
here is what i inserted into the web.xml (in the conf-directory):
<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>classdebuginfo</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>xpoweredBy</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>
any ideas / suggestions?.......i am out of ideas right now....
thx in advance, timo

Answer 1

If you're using a debugger in a JSP or servlet, I'd say you're really in trouble.
I never use a debugger like that for servlets or JSPs. If I have problems I depend on the logger to help me out. Just log statements until you narrow the problem down.
This might be "clumsy", but it works even in those cases where you don't have a debugger available (like on a client's installation site).
If your servlet or JSP is doing so much stuff that you have to debug, I'd say they're both doing too much. JSPs are for display; servlets for control. Complex business logic belongs in POJOs that you can debug or EJBs.
Maybe you should rethink your design.
%