> From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Subject: Re: Log4j logging doesn't work when a web application is moved > outside Tomcat/webapps directory > > You want this: > > webapps/abc > webapps/abc/ROOT <-- this is your "abc" webapp > webapps/abc/ROOT/META-INF > webapps/abc/ROOT/META-INF/context.xml > webapps/xyz > webapps/xyz/ROOT <-- this is your "xyz" webapp > webapps/xyz/ROOT/META-INF > webapps/xyz/ROOT/META-INF/context.xml
No, you don't want the above. That has overlapping appBase directories. As pointed out by both André and myself, keep them separate, at the same level of the directory hierarchy: webapps webapps/ROOT webapps/examples ... webapps-abc webapps-abc/ROOT <-- this is your "abc" webapp webapps-abc/ROOT/META-INF webapps-abc/ROOT/META-INF/context.xml webapps-xyz webapps-xyz/ROOT <-- this is your "xyz" webapp webapps-xyz/ROOT/META-INF webapps-xyz/ROOT/META-INF/context.xml The above will preserve your existing Tomcat webapps. > Set up two <Host>s: > <Engine defaultHost="abc"> > <Host name="abc" appBase="webapps/abc" autoDeploy="true"> > <Alias>abc.local</Alias> > </Host> > <Host name="xyz" appBase="webapps/xyz" autoDeploy="true"> > <Alias>xyz.local</Alias> > </Host> > </Engine> This destroys access to the Tomcat-supplied webapps, so don't do that. Add the two new <Host> elements, but don't replace the existing one, and don't change what defaultHost points to - unless you really, really want the replacement to be the default. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
