Another trick is that when you make a change through the administrator site, that change in the bluedragon.xml is somehow reloaded by that webapp. But the other webapps on the same tomcat instance don't get notified, so they retain the configuration they had the last time tomcat was started. I'm going to see if there's something easy I can do that will tell it to notify all webapps, but I doubt they have that kind of communication between them.
On Jul 15, 12:41 pm, Colin MacAllister <[email protected]> wrote: > So I have a symlink (ln -s) pointing to a central location for the WEB- > INF/bluedragon/ directory (which contains bluedragon.xml), and that > worked fine *without* using the autoFollowLinks tag in context.xml > like the conversation at that URL suggests. But sharing anything else > breaks it. > > Also as in the conversation I leave out the "path" attribute, so that > each webapp defaults to its own path. > > On Jul 14, 1:20 pm, "Peter J. Farrell" <[email protected]> wrote: > > > Colin MacAllister said the following on 13/07/10 15:23:> My admittedly > > brief foray down that path didn't work. ln -s WEB-INF to > > > a central dir for two different virtual hosts yielded a 503 error > > > (Tomcat didn't start up properly.) > > > Actually, you have to configure Tomcat to follow symlinks -- there is an > > option one of the XML files. I'm sure Matt's link shows that. > > > .pjf > > -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon online manual: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
