For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 6 replies, 3 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
I’m having a problem with JSP debugging in WLS 8.1. I have set up weblogic.xml correctly and the if I set a breakpoint in my JSP then it of catches. However, in the Debug View, under the relevant suspended thread, there is no “MyJSP.jsp line: 24” row like I would expect. Instead the first row in the stack is “_myjsp(JspBase).service(ServletRequest, ServletResponse) line: 34”
Can anyone shed any light on this?
Thanks in advance,
Lawrie.Lawrie,
Your JSP pages are compiled to Servlets (translation process) and then compiled to classes by the server. The debugger view is showing you the generated servlet information. You should be able to step through your page though and see your attr values in the variable view however.When debugging a JSP deployed to Tomcat or JBoss I get a “MyJSP.jsp line: 24” row under the suspended thread in the debug view and I can step through the JSP line by line. With WLS 8.1 I’m not getting sny of this (or any seemingly useful info). Debugging for WebLogic should work the same as Tomcat or JBoss, no?
Should debugging a JSP with WebLogic 8.1 not behave exactly the same way as with JBoss???
I would really like to know whether this is the case…
Regards,
LawrieLawrie,
My appologies, I had forwarded your question off to a member of the dev team that I just realized was out of the office for a few days, he should be back in, I’ll re-ping him.Should debugging a JSP with WebLogic 8.1 not behave exactly the same way as with JBoss???
No, actually it should not at this time. The difference is that Tomcat (which JBoss uses for its we container) implements the JSR-045 debugging specification that allows MyEclipse to translate both the file names and line numbers between the generated servlet’s Java name/line numbering to the original JSP’s. Weblogic 8.1 does not provide this information. However, due to our experience with what Weblogic does do, we’ve managed to make JSP debugging work properly, but just can’t effectively translate the debug stack since that’s provided by the JVM. Hope that clears things up.
