On Tue, 16 Feb 1999, Damian Fauth wrote:
> "Brian S. Wallace" wrote:
> >
> > My question is this. I have two zones setup that point to two different
> > directories. The developers want to put class files in different
> > subdirectories. Setting up new repositories every time a developer creates
> > a new subdirectory is really a pain. The documentation suggests that the
> > zone properties file for each zone be put into each developer's directory
> > so that they can edit it themselves. However, after it's edited, the web
> > server has to be restarted, right? This is not practical.
The webserver shouldn't need to be restarted, but it's possible that
that's the case (as noted below, I'd consider this a bug). However, you
should be able to get the same effect (as adding to the repositories line)
either by copying the files (as suggested by Damian) or through symlinks.
Ie. if I've created
com.mycompany.foo.bar
and I've already got a repository w/
com.mycompany.foo
I could go into that directory and create an appropriate symlink.
IMO, lots of repositories lines will be more confusing than using a single
directory with lots of symlinks for each developer...
> > One part of the FAQ's talks about what I want to do with subdirectories,
> > but it's not clear to me on how to make it work: packages. If I create a
> > new subdirectory in a zone, how do I make the classes in that subdirectory
> > accessable? Repositories, packages, what? Please give me a example on how
> > to do this.
>
> I have also struggled with how to do this in a multi-user/multi-zone
> environment such as you might find at an ISP.
>
> In an environment where everything runs a GSP template there is no
> problem once the users zone file is set up as the GSPServlet has its own
> initialisation file and you can force a reload and reinitialisation of
> that class (and hence a reloading of the GSP init file) by 'touch'ing
> the GSP jar file or any other jar file used in this zone.
Actually, if you're seeing this effect from touching the .jar file, you're
seeing the reload through JServ's own reload functionality. If configured
appropriately, we do make GSP reload if you touch its conf file (JServ
doesn't know or care about GSP's conf file, so this is necessary); but for
the classes, we leave that in JServ's hands.
JServ calls destroy servlet and then initializes a new one, which is
basically the same thing which we do when the gsp.conf file changes. (We
simply reinitialize the existing one, since we know that'll work.)
> What I would like to see is some way to force a reinitialisation of the
> relevant JServServletManager object (identifed by the zone name) to
> support similar behaviour for the re-reading of a zone configuration
> file. Developers, is there any chance of getting this sort of
> functionality included? It would be an attractive selling point to any
> ISP considering Apache-JServ as a multi-user shared web application
> environment. How would you signal the JServ class to destroy and
> reconstruct the relevant JServServletManager? Perhaps a configuration
> option to specify that when a 'startup servlet' needs to be reloaded the
> whole zone file should be re-read?
JServ does reloading of the classes in each zone based on its conf file
and based on the contents of the repositoies. Do you mean that JServ
isn't re-reading the (Java .properties) conf file to reinitialize the
JServServletManager?
If that's the case, I'd consider this a bug, which is to say that yes, we
can fix it. :) But if you mean that it doesn't re-initialize from the
Apache .conf files, I'd have to say that this is correct (since it's
consistent w/ standard behavior wrt Apache's .conf files).
Thanks for using GSP & JServ!
hth --
Ed
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://www.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
