tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Net Dawg <>
Subject Re: Welcome file list in web.xml treats index.jsp different from other filenames
Date Sat, 14 Apr 2012 19:37:19 GMT
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: 


     <welcome-file />

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 <Context>,

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

Unlikely. You have to provide specific example to confirm that. The
above mentioned option could explain that as well.

> However     <welcome-file-list />
> 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

Best regards,
Konstantin Kolinko

To unsubscribe, e-mail:
For additional commands, e-mail:
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message