Welcome file list in web.xml treats index.jsp different from other filenames
If a file named index.jsp is declared as a welcome and it is not there in the system, tomcat does not allow failover to framework like Tapestry. However, if a file named Bienvenue.jsp is declared as welcome file, the failover is allowed. For details see the following thread: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tc5637647.html - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Welcome file list in web.xml treats index.jsp different from other filenames
Also, please note
This, in the application web.xml, seems to tell Tomcat "there are no welcome
files in this application, do not look for index.jsp etc" ...
However
is ignored and server picks up default values in ${Tomcat.home}/conf/web.xml
Basically, should be enough to tell tomcat the same thing
- "there are no welcome files"
- Original Message -
From: Net Dawg
To: "dev@tomcat.apache.org"
Cc:
Sent: Friday, April 13, 2012 9:08 AM
Subject: Welcome file list in web.xml treats index.jsp different from other
filenames
If a file named index.jsp is declared as a welcome and it is not there in the
system, tomcat does not allow failover to framework like Tapestry. However, if
a file named Bienvenue.jsp is declared as welcome file, the failover is
allowed.
For details see the following thread:
http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tc5637647.html
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Welcome file list in web.xml treats index.jsp different from other filenames
Hi Konstantin,
Thanks for the clarifications. I stand corrected on the failover - could be a
Tapestry issue not Tomcat.
However, bottom line, Tomcat 7 works a bit differently from Tomcat 5 with
respect to welome files, probably respecting the new servlet spec
To your question as to "what point merging algorithms are not followed", please
try this inside your application context and you will probably see the same:
This seems to tell Tomcat 7, in plain English, "there are no welcome files,
don't bother looking for them anywhere" ...
In other words, it is NOT merged with container as intended/indicated below in
your message.
From: Konstantin Kolinko
To: Tomcat Developers List
Sent: Friday, April 13, 2012 9:44 AM
Subject: Re: Welcome file list in web.xml treats index.jsp different from other
filenames
2012/4/13 Net Dawg :
> If a file named index.jsp is declared as a welcome and it is not there in the
> system, tomcat does not allow failover to framework like Tapestry.
It sounds like behaviour that can be controlled by
"resourceOnlyServlets" option in ,
See
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html
The current behaviour is caused by compatibility concerns with earlier
versions of Tomcat. Read the doc for more details.
> However, if a file named Bienvenue.jsp is declared as welcome file, the
> failover is allowed.
Unlikely. You have to provide specific example to confirm that. The
above mentioned option could explain that as well.
> However
> is ignored and server picks up default values in ${Tomcat.home}/conf/web.xml
conf/web.xml is not just default. It is merged with app's web.xml
using the rules for merging web fragments, as specified in the Servlet
3.0 Rev.a specification. If current behaviour contradicts with
specification, please cite what point in merging algorithm is not
followed.
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
