head	1.4;
access;
symbols;
locks
	nobody:1.4; strict;
comment	@# @;


1.4
date	99.08.17.20.03.38;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.08.17.20.03.20;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.08.17.20.02.53;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.08.17.20.02.42;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.4
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 166
IDependOn-Set: 2
IDependOn-Set: 285
IDependOn-Set: 29
IDependOn-Set: 7
LastModifiedSecs: 934920218
Parent: 166
SequenceNumber: 2
Title: Starting the system from the command line, does that change how things work?
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 934920218
Type: monospaced
Lines: 61
----------
From: "Craig R. McClanahan" <cmcclanahan@@mytownnet.com>
To: Java Apache Users <java-apache-users@@list.working-dogs.com>
Subject: Re: Starting JServ from the command line and auto-reloading classes
Date: Tue, Aug 17, 1999, 8:25 AM

Nimret Sandhu wrote:

> hello all -
>
> if i start a JServ instance from the command line, does JServ only use one
> classloader to load all classes or does it load the classes specified in the
> repository param of the zone file in the auto-reloading ( adaptive?!)
> classloader?
>

Apache JServ uses a class loader per zone.  The "class path" for this loader is
the set of directories and ZIP/JAR files you list as "repositories=xxx" entries
in that zone configuration file.

Starting Apache JServ from the command line or automatically does not matter in
this regard.  The only difference between the two is how the system class path
is set:

* If you start Apache JServ from the command line,
  it is passed in the CLASSPATH environment variable
  (or can be overridden on the command line).

* If you start Apache JServ automatically when Apache
  starts, the CLASSPATH environment variable is ignored.
  Instead, the class path entries are set by using
  "wrapper.classpath" properties in the JServ config file.

The zone class loader (an instance of the AdaptiveClassLoader class) implements
automatic reloading, but it can only do so for classes loaded from the
repositories -- not from the system class loader.

>
> it appears to do the former. when i setup my classpath from the command line
> to exclude my servlets and try to run them, i get the ol' 'cannot scan
> servlet headers' error. but, when i add the path specified by the repository
> entry to the classpath and restart jserv from the command line, it finds the
> servlets and works fine.
>

Every class you want to load has to be on either the system class path (defined
as described earlier) or the repositories list for the zone you use it in.  No
classes should appear on both lists.  Automatic reloading only works for
classes found in the repositories -- not for classes found in the system class
path.

>
> anyone else come across this problem?
> software: Apache 1.3.6, JServ 1.0 and NT Server 4.0
> regs,
>

What you are describing is the normal operation of the system.  So tell me
again what the problem is?  :-)

Craig McClanahan
EndPart: 0
@


1.3
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 934920198
d9 1
a9 1
SequenceNumber: 1
d11 68
@


1.2
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 934920161
d9 2
a10 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d5 1
@
