https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
--- Comment #7 from Konstantin Kolinko ---
Some notes from me:
1. If a web application has been stopped (or failed to start), its mappings are
absent from the org.apache.catalina.mapper.Mapper.
That is the key point here. Period.
2.
https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
--- Comment #6 from Mark Thomas ---
(In reply to Michael Osipov from comment #5)
> (In reply to Mark Thomas from comment #4)
> > How to respond when a web application is stopped is very much personal
> > preference. Some administrators will
https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
--- Comment #5 from Michael Osipov ---
(In reply to Mark Thomas from comment #4)
> How to respond when a web application is stopped is very much personal
> preference. Some administrators will want 404, some 403, some something else.
>
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
--- Comment #3 from Christopher Schultz ---
(In reply to Michael Osipov from comment #2)
> I am not convinced by either approach because in any case it would require me
> to deploy a ROOT application with Tomcat privileges to properly fetch
https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
--- Comment #2 from Michael Osipov ---
Chris,
I am not convined by either approach because in any case it would require me to
deploy a ROOT application with Tomcat priviledges to properly fetch the URL and
check whether the application is
https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
--- Comment #1 from Christopher Schultz ---
This can be easily done using the ROOT web application with a custom response
for e.g. /myapp/* which will execute when /myapp/ hasn't deployed properly.
You can even use the status code of your
https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
Michael Osipov changed:
What|Removed |Added
CC||micha...@apache.org
--
You are
