Java Server Pages

 

Creating JSP projects

You can use the New project wizard to create jsp applications. Choose the Project | New... menu entry and select the Web application (JSP) project type. CodeGuide fully supports source code analysis (error detection, code completion, etc.) in JSP files.

 

 

 

After creating the project you can test the sample Java Server Page by choosing Project | Run. The servlet engine startup message will be displayed in the Output Window:

 

 

The servlet engine is started on the local machine port 8080.

 

Point your browser to http://localhost:8080 and follow the link to access the sample Java Server Page. The sample JSP web application has the same functionality as the sample servlet web application.

 

 

Configuration

It is necessary to correctly set the Web application path in the Project Settings to the root directory of your web application (usually something like  .../webapps/mywebapp). Otherwise Taglib support and support for the JSP include directive might not work.

 

 

Debugging Java Server Pages

The debugger integrated in CodeGuide is a Java debugger. Thus you cannot step through the source of the Java Server Pages. But you can step through the generated source files which reside in work/localhost/$webapp$.

 

After creating the sample project and starting it for the first time you have to access the JSP page so that the Java source code generated and compiled by the servlet engine.

 

A good way to get started debugging Java Server Pages is to set a breakpoint in the _jspService() method.

 

 

As soon as the Java Server Page is accessed the debugger stops at the breakpoint.

 

Please note that the browser can time-out waiting for the response from the servlet engine when you step through the generated code.

 

 

Taglib support

CodeGuide supports JSP custom actions which are usually supplied using taglibs.

 

Requirements