Craig,
>>
Add the JAR files to your system CLASSPATH, before you run the
"startserver" script. The script adds on the extra class path settings
that are needed to run the engine itself, and the associated examples.
In a Java2 environment, you also have the choice of installing JAR files as
system extensions, by putting them in the following directory (where
{JDK_HOME} is the base directory of your Java2 install:
{JDK_HOME}/jre/lib/ext
<<
Thanks for your comments. Adding the servlet JAR to the class path works
but this solution may only be well suited for a small number of shared
archives. In case of servlets, this method is limited since you cannot add
every servlet JAR to the class path because of length restrictions. I'm
really amazed that JSWDK does not offer a more elegant and unrestricted
method for invoking servlets from JARs.
Take a servlet engine like ServletExec 2.1 for example and you know how
easy this can be. Just put your classes and JARs into the \Servlets
directory, that's all. If the servlet to invoke matches the name of a JAR,
ServletExec opens it and searches for the class file in the JAR.
Heinz Wehner
(Karlsruhe, Germany)
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
