Hey Stephen,
These are great!
We have instructions on our web site on how to config VC 3 and JRun
(courtesy of another user, actually). Would you mind if I added your
instructions as an updated version for VC 4? I would credit you in the
Knowledge Base article.
Scott Stirling
Allaire Corp.
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Williams, Stephen
Sent: Tuesday, May 02, 2000 5:40 PM
To: [EMAIL PROTECTED]
Subject: Re: How to configure Visual cafe to run the Jrun engine
We have successfully configured Visual Cafe 4 Expert Edition to run the JRun
engine (version 2.3.3 build 157). Below are the details of what we did to
get this working. The instructions are long, but it's really not that
difficult, and it's great to be able to debug your servlets and even JSPs.
Please let me know if you have any questions.
Note: Whenever you see "..." in a pathname, you'll need to put in the
appropriate path to the installed product (Visual Cafe or JRun) on your
machine. For instance, on my machine, I installed Visual Cafe and JRun in
E:\, so I replace "..." with "E:\".
1. Replaced Visual Cafe's version of jsdk.jar with the one from Sun's Java
Servlet Development Kit 1.0.1 (JSDWK1.0.1). I belive this was necessary
because we are using JSP 1.0, but the jsdk.jar shipped with Visual Cafe was
for JSP 0.92. This file is located in:
...\VisualCafe\Java\lib\jsdk.jar
2. Modified the classpath used by Visual Cafe's JVM's to include everything
from the classpath used by the JRun engine. This is necessary so that
Visual Cafe can find all of the classes used by the JRun engine. The JRun
classpath that I added can be found in the "java.classpath" property in the
following JRun property file:
...\JRun\jsm-default\properties\jsm.properties
On my machine, the JRun classpath starts with the directory
"e:/JRun/classes" and contains 20+ paths. Note that I converted some of the
directory paths to use forward slashes ("/") instead of escaped backslashes
("\\") since backslashes only work on Windows boxes and then only with some
JVMs.
This JRun classpath must be added to two classpaths in Visual Cafe:
"Classpath for the VM" and "Classpath for the Compiler". Both of those can
be set under "Tools->Options->Virtual Machines". I prepended the JRun
classpath to the existing ones in Visual Cafe. You'll need to restart
Visual Cafe after you do this for the changes to take effect.
3. In order for JSP pages to compile properly when running JRun in Visual
Cafe, you'll need to modify the "compiler" property in the jsp.properties
property file to contain an absolute path instead of a relative one. Note
that this file exists in two places, depending upon whether you are running
the JRun engine with the JRun web server or with any other web server (e.g.,
Apache, IIS, NES, etc.). For safety, change the value in both copies:
...\JRun\jsm-default\services\jse\properties\jsp.properties
...\JRun\jsm-default\services\jseweb\properties\jsp.properties
The original value for the "compiler" property will probably start with
"..\\bin\\jikesw.exe". That needs to be changed to something like
"E:\\JRun\\bin\\jikesw.exe".
This step is necessary because the JRun engine expects to be started up with
the current directory set to ...\JRun\jsm-default. However, Visual Cafe
runs programs with the current directory set to wherever your Visual Cafe
project file is located. I haven't found a way to tell Visual Cafe how to
run programs in a different directory.
4. Configure your project in Visual Cafe to run the appropriate JRun class
when debugging. This is done by setting your project options in Visual Cafe
as follows:
- Select "Project->Options"
- Select the "Project" tab.
- Set the Project Type to Application
- Set the Main Class to com.livesoftware.jrun.service.ServiceManager
- Set the Program Arguments to E:\JRun\jsm-default (assuming that JRun is
installed in "E:\").
That's it. Now, when you select "Project->Run in Debugger" in Visual Cafe,
it will start up the JRun engine. You can set breakpoints in your servlets
and any other Java classes just like a non-servlet Java application.
--
Stephen A. Williams
HNC Telecommunications Solutions
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
