Remote debugging OpenCms with Eclipse and Netbeans

(Difference between revisions)
Jump to: navigation, search
m (jsp debugging help added)
Line 1: Line 1:
 
'''Keywords''': opencms, eclipse, source, jsp, remote, tomcat
 
'''Keywords''': opencms, eclipse, source, jsp, remote, tomcat
  
see the posting on the opencms-dev mailinglist for details: http://www.nabble.com/Remote-debugging-OpenCms-with-Eclipse-tf3038442.html
+
== Remote JSP Debugging (Eclipse) ==
 +
In order to make JSP debugging work you first have to set a breakpoint into the desired JSP and debug the application. As soon as the breakpoint is hit Eclipse will ask you for the JSP source path. You have to choose the path of the web application where OpenCms is deployed. Eclipse will then display the JSP source and you will be able to step through it within the debugger. The source used is the one found in WEB-INF/jsp/.
 +
 
 +
See the posting on the opencms-dev mailinglist for details: http://www.nabble.com/Remote-debugging-OpenCms-with-Eclipse-tf3038442.html

Revision as of 18:16, 26 April 2007

Keywords: opencms, eclipse, source, jsp, remote, tomcat

Remote JSP Debugging (Eclipse)

In order to make JSP debugging work you first have to set a breakpoint into the desired JSP and debug the application. As soon as the breakpoint is hit Eclipse will ask you for the JSP source path. You have to choose the path of the web application where OpenCms is deployed. Eclipse will then display the JSP source and you will be able to step through it within the debugger. The source used is the one found in WEB-INF/jsp/.

See the posting on the opencms-dev mailinglist for details: http://www.nabble.com/Remote-debugging-OpenCms-with-Eclipse-tf3038442.html

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox