On 23/10/2024 23:13, Mark Foley wrote:
On Wed, 23 Oct 2024 19:13:44 Mark Thomas <ma...@apache.org> wrote:
<snip/>
That won't work. What will work is renaming:
$CATALINA_HOME/webapps/myapp
to
$CATALINA_HOME/webapps/myapp#subapp/
Mark
Hmmm ... what I was attempting was splitting many webapps into multiple
directories. I have a top-level organization which would be like:
$CATALINA_HOME/webapps/GrandWaterBuffalo/
Then subordinate to that would be sub-orgs like:
$CATALINA_HOME/webapps/GrandWaterBuffalo/districtA
$CATALINA_HOME/webapps/GrandWaterBuffalo/districtB
$CATALINA_HOME/webapps/GrandWaterBuffalo/districtC
etc. Perhaps 30+ at this level. Then sub-orgs for each of these like:
$CATALINA_HOME/webapps/GrandWaterBuffalo/districtA/Chapter1
$CATALINA_HOME/webapps/GrandWaterBuffalo/districtA/Chapter2
$CATALINA_HOME/webapps/GrandWaterBuffalo/districtA/Chapter3
etc. Probably around 10-ish "Chapters" per District. As you can see, this
could result in many webapps. I was trying not to put them all under one
$CATALINA_HOME/webapps/ directory level, but your example effectively does that.
So, no way around this?
You can move the webapps all out of $CATALINA_HOME/webapps but then
you'll still have 100s of context.xml files in
$CATALINA_HOME/catalina/localhost or (worse) 100s of <Context .../>
entries in server.xml to reference the external locations.
What do hosting sites do that may have several hundred
webapps for different customers?
I don't know. I suspect a lot have moved to 1 container per customer.
Which may just move the problem.
Just put everything under $CATALINA_HOME/webapps?
With a sensible naming convention that is probably the approach I'd take.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
