One thing that I've been wondering about is if you guys have considered creating XML schema files for each of the configuration files? I'm currently using the XML validation for the Web application files which (while slow) is nice if you're making a lot of changes to those files. It would be nice if the same thing existed for the Tomcat specific configuration files as well.
Jon
----- Original Message ----- From: "Shapira, Yoav" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, September 01, 2004 2:16 PM
Subject: RE: <Context path="" docBase="ROOT"... fails in Tomcat 5.5?
Hi, Try removing the "debug" attribute, as that's not in the standard Context in 5.5.0 (Loggers are gone).
In general, if you copy and paste configuration files across release versions, be careful.
Yoav Shapira Millennium Research Informatics
get-----Original Message----- From: Jonathan Eric Miller [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 2:37 PM To: Tomcat Users List Subject: Re: <Context path="" docBase="ROOT"... fails in Tomcat 5.5?
Nope. The same server.xml works fine in Tomcat 5.0.25.
Jon
----- Original Message ----- From: "Shapira, Yoav" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, September 01, 2004 1:29 PM Subject: RE: <Context path="" docBase="ROOT"... fails in Tomcat 5.5?
Hi, Is there another context configured for the "" path?
Yoav Shapira Millennium Research Informatics
error-----Original Message----- From: Jonathan Eric Miller [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 2:20 PM To: Tomcat User List Subject: <Context path="" docBase="ROOT"... fails in Tomcat 5.5?
In Tomcat 4.0 and 5.0, I had the following in my server.xml file.
<Context path="" docBase="ROOT" debug="0" reloadable="true"/>
However, if I try to use this in Tomcat 5.5, I receive the followingin catalina.out. Does anyone know if I need to change something to.jitbeingto work with Tomcat 5.5, or, is this a bug?
Also, is ROOT a special case? I don't see where the ROOT directory isuniqueassigned the the root path in any of the configuration files.
Sep 1, 2004 11:31:36 AM org.apache.catalina.startup.HostConfig deployDirectory SEVERE: Error deploying web application directory ROOT java.lang.IllegalArgumentException: addChild: Child name '' is notat org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase9)ava:749) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73a:at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.javav880)at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j)a:843) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474:3at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1063) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.javaeS10)at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl)upport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1011) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1003) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:42050at org.apache.catalina.core.StandardService.start(StandardService.java:47))at org.apache.catalina.core.StandardServer.start(StandardServer.java:196Method)atorg.apache.catalina.startup.Catalina.start(Catalina.java:545)at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativejaat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.sova:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesrImporg.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)l.java:25) at java.lang.reflect.Method.invoke(Method.java:582) atatorg.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
Jon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]