Problems deploying and running JSPs

Problems deploying JSPs can be specific to a particular JSP server. PowerBuilder provides an interface for deployment of JSPs to Tomcat and to EAServer, but you can also use the command line tool to deploy JSPs to other servers that support the JSP 1.2 specification.

For more information, see “Custom command line deployment”.

Problem running JSPs deployed to Tomcat

After you deploy a JSP application to Tomcat, you might need to shut down the Tomcat server and restart it before you can run the application from a client browser.

If you are using the JSP in a Tomcat server with a component running in EAServer, you might need to change the HTTP listener port for EAServer or Tomcat before you restart Tomcat. Both servers use port 8080 as the default HTTP listener port. If you do not change the HTTP listener port on either server, you can still run both servers, but you must restart the Tomcat server before starting or restarting EAServer.

Integer parsing problem

When deploying JSPs to EAServer, it is possible to run into problems creating Integers. The issue is that in a JSP file the following code fails to compile in EAServer:

Integer doesNotWork = new Integer (0);

To fix this issue, the JSP should contain:

Integer doesWork = new Integer ("0");

Quotation marks are required around the integer (0) in the construction of the Integer.

Problems deploying after setting a target exception page

If you specify an exception class (as opposed to an HTML error code) in the Error Mapping pane of the Deployment Configuration Properties dialog box for a JSP target, you must change the default value in the Error column from "Y" to "N". Otherwise, you will not be able to deploy your target to EAServer or run your target application on a different JSP server.

For more information about JSP target deployment properties, see “Editing a JSP deployment configuration”.

Problems deploying to an upgraded version of EAServer

PowerBuilder installs easclient.jar and easj2ee.jar files to the Sybase\Shared\Web Targets directory. These JAR files must be compatible with the EAServer to which you deploy your JSP target, or you will have problems deploying to the server. If you are using a version of EAServer that is different from the version supplied with the PowerBuilder installation, you should replace these JAR files with the easclient.jar and easj2ee.jar files from the Sybase\EAServer\Java\Lib directory.