tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Stevens <>
Subject Re: classreloading and 4.x
Date Thu, 04 Jan 2001 00:39:43 GMT
on 1/3/2001 3:37 PM, "Craig R. McClanahan" <>

> * Put the "scarab" webapp directory somewhere other than in
> $CATALINA_HOME/webapps, and set your docBase
> parameter above to an absolute path to it -- or at least
> a path that is relative to the "appBase" directory of the <Host>.

yuck. no absolute paths. I want ppl to be able to use Scarab without having
to edit properties files to get things working on their boxes.

> * Call your "scarab" directory "ROOT" instead (which is the
> name used when auto-deploying the root webapp).  Because
> it will have already been initialized by your <Context>, no
> second webapp will be created.

I don't want to screw up others ROOT directories.

> * Turn off auto-deploy support.  Hmm, there's no configuration
> setting for that just yet, so it doesn't help right now, but
> that will get fixed.

This sounds like my only solution, but isn't available yet. :-(

> * Define your webapp with context path "/scarab" instead
> of context path "".  I don't know what that would do to Turbine's
> internal request URI processing, but it should be possible.  It
> works (from the Catalina perspective) for the same reason that
> option 2 would -- it won't deploy two webapps on the same
> context path.

This doesn't work. I get that "Turbine isn't a servlet" error.

Any other ideas on solving this problem? What do others do? Is there
something I can define in my web.xml? I'm sorry, but my knowledge of web.xml
and server.xml manipulation is very limited currently.

> One other thing that bit me when testing this -- I normally have a
> environment variable set.  If you follow the indicated directions
> (./bin/ run), you will be running the copy in CATALINA_HOME, not in
> the Scarab build directory.  You might want to add a startup script that
> explicitly unsets CATALINA_HOME and then does the usual "run" or "start".

I added better documentation to the README.txt file for now.

> PS:  Thanks for the good test case!

Thanks. That is why I feel it is so important to have a working sandbox that
is easy for people to get up and running quickly with.


Honk if you love peace and quiet.

View raw message