Summary: | warn if appBase is not existing as a File or directory | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Ralf Hauser <hauser> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | Nightly Build | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | All | ||
Attachments: |
HostConfig.java.patch
HostConfig.java.patch2 HostConfig.java.patch3 |
Description
Ralf Hauser
2005-05-25 10:03:08 UTC
Created attachment 15162 [details]
HostConfig.java.patch
a little bit more user-friendly
Created attachment 15163 [details]
HostConfig.java.patch2
yet more user-friendliness (and an error less)
I don't understand: your patches actually remove logging statements, yet the title of this issue asks to add a warning, no? Created attachment 15742 [details]
HostConfig.java.patch3
corrected - now using
diff -u HostConfig.java.orig HostConfig.java
Specifying a non-existing appBase is not necessarily invalid. By default, Tomcat 7 will create the appBase if it does not already exist. I have tweaked the tests Tomcat does in case a file is specified as an appBase. I do not propose back-porting this to Tomcat 5 or 6. |