----- Original Message -----
From: Greg McPherson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 11, 1999 6:41 AM
Subject: Servlets vs JARs
> Ok, a very basic question.
> I've got a servlet working fine using .class files, but I'd like to
package
> the thing up into a single JAR (It's a multipurpose bit of code... either
a
> command line application, a Swing GUI app, or a servlet). I dislike the
> idea of having to hardwire paths into the System CLASSPATH, it's not the
> most user friendly part of the Java framework. Is this the only way to
make
> a JAR servlet work, or am I really forced to stick with class files?
>
Hi Greg,
it all depends on your setup of course but the Servlet engine tends to have
its own classpath rather than using the system one. This has obvious
advantages
of course.
If you want to package things in a jar file you will need to find out where
the
engine has its classpath set.
In JRun this is in the jsm.properties file or you can set the classpath
using the Admin
tool.
Hope this helps
Andy Bailey
___________________________________________________________________________
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
