To whom it may concern,
On 4/14/12 3:37 PM, Net Dawg wrote:
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-list
welcome-file /
/welcome-file-list
This
2012/4/20 Christopher Schultz ch...@christopherschultz.net:
To whom it may concern,
On 4/14/12 3:37 PM, Net Dawg wrote:
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:
Subject: Re: Welcome file list in web.xml treats index.jsp different from other
filenames
2012/4/13 Net Dawg net.d...@yahoo.com:
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
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:
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
2012/4/13 Net Dawg net.d...@yahoo.com:
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,
See
