Workaround for integrating Tomcat 5 with JBuilder X

By: Christopher Moeller

Abstract: Step-by-step procedure for integrating Tomcat 5 with JBuilder X

Workaround for integrating Tomcat 5 with JBuilder X

Workaround for integrating Tomcat 5 with JBuilder X

Information in this Brief applies to:

  • JBuilder X Developer or Enterprise
  • Any platform


Step-by-step procedure for integrating Tomcat 5 with JBuilder X



This is not a supported or tested configuration. This is just a workaround to get the server running in JBuilder X. JSP debugging will not work with this solution.


1. Tools | Configure Servers, select the Tomcat 4.1 server and click the Copy button. Change the name to Tomcat 5.0. Next, set the home directory to the root of the Tomcat 5.0 installation, and remove the entry in the Class list and add <TOMCAT_5.0_HOME>/bin/bootstrap.jar.


2. File | New Project. Set server to Tomcat 5.0 and create a web module. This will trigger generation of the Tomcat 5.0 Servlet library.


3. Tools | Configure Libraries. Edit the Tomcat 5.0 Servlet library and add the following jars :


Make a backup of this library (in your user home directory) as it gets regenerated when you create a new web module/JSP/servlet. Please make sure that you replace the library when you use any of the web gallery wizards.


4. Set server for the project to Tomcat 5.0.


5. If a "Tomcat" folder is not present under the project's root directory, create one (e.g. ../jbproject/untitled1/Tomcat). Next, create a directory named "conf" under this directory (e.g. ../jbproject/untitled1/Tomcat/conf). and create an XML file named server8080.xml. Sample server8080.xml is below. Please modify the appBase, docBase, and workDir, etc. according to your web module properties:


<?xml version="1.0" encoding="UTF-8"?>
<!--This comment marks this file as generated, so it may be deleted and regenerated at any time. To preserve manual changes to this file, delete this comment.-->
<Server debug="0" port="8081" shutdown="SHUTDOWN">
<Service name="Catalina">
<Connector acceptCount="10" connectionTimeout="60000" debug="0" maxThreads="75" minSpareThreads="5" port="8080"/>
<Engine debug="0" defaultHost="localhost" name="Catalina">
<Host appBase="C:Documents and Settings<user name>jbprojectuntitled1Tomcatwebapps" debug="0" name="localhost" unpackWARs="true">
<Context debug="0" docBase="C:Documents and Settings<user name>jbprojectuntitled1WebModule1" path="/WebModule1" reloadable="true" workDir="C:Documents and Settings<user name>jbprojectuntitled1TomcatworkWebModule1"/>


6. Start the server in JBuilder. This should use the modified server8080.xml


You should be able to compile JSPs using this workaround but not debug. You should be able to debug any java code. You will see a number of exceptions for the admin, manager, balancer services which do not get started when you normally run the server in JBuilder. Please ignore these exceptions. The server should function normally without these services.


Server Response from: ETNASC03