Yes, technically it does, however the source map that it returns to the JSP debugger is extremely vague and lacks many details that allow for successful breaking and stepping through the code. Because of this if you are doing JSP debugging on JRun you will most likely notice flaky stepping behavior, unfortunately there is nothing we can do about this as the lack of details in the source map itself is the problem. This is an example of a JSP page used to debug:
<%@ page language="java" import="java.util.*" pageEncoding="UTF-8"%>
<%
String path = request.getContextPath();
String basePath =
request.getScheme()+"://"+request.getServerName()+":"+request.getServerPort()+path+"/";
%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<base href="<%=basePath%>">
<title>My JSP '13MyJsp.jsp' starting page</title>
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="cache-control" content="no-cache">
<meta http-equiv="expires" content="0">
<meta http-equiv="keywords" content="keyword1,keyword2,keyword3">
<meta http-equiv="description" content="This is my page">
<link rel="stylesheet" type="text/css" href="styles.css">
-->
</head>
<body>
This is my JSP page.
<%
Date date = new Date();
System.out.println("Date is: " + date);
%>
</body>
</html>
And this is the source map returned by Tomcat:
SMAP
_13MyJsp_jsp.java
JSP
*S JSP
*F
+ 0 13MyJsp.jsp
13MyJsp.jsp
*L
1,6:43
6,5:49
11:54,3
12,17:57
29,3:75
31,4:78
*E
And the source map returned by JRun
SMAP
/13MyJsp.jsp
JSP
*S JSP
*F
+ 0 13MyJsp.jsp
13MyJsp.jsp
*L
3#0,2:50,3
28#0,3:57,3
*E
As you can see there is signifigantly less information comming back from the JRun4 source maps, this does not allow the MyEclipse debugger to perform an accurate debugging session of a JSP page currently.
NOTE: Information on how to read source maps can be found here: http://jcp.org/aboutJava/communityprocess/final/jsr045/index.html
-
This topic was modified 10 years, 1 month ago by
support-tony. Reason: Minor edits