Re: Welcome file list in web.xml treats index.jsp different from other filenames
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 seems to tell Tomcat 7, in plain English, there are no welcome files, don't bother looking for them anywhere ... You probably aren't getting a response because you didn't answer the question. Your opinion of how things should work isn't really relevant, here. Konstantin asked where Tomcat's behavior violates the servlet spec and you replied by telling him what you think ought to happen. That's not an answer, so you're being ignored. Can you find a place where your seems to tell scenario above is actually supported by language in the servlet specification? If so, tell us where. If the spec isn't clear on a subject, usually the safest thing to do is not change anything because users have become reliant on certain behavior. If and when the spec is clarified, a change will be made. -chris signature.asc Description: OpenPGP digital signature
Re: Welcome file list in web.xml treats index.jsp different from other filenames
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: welcome-file-list welcome-file / /welcome-file-list This seems to tell Tomcat 7, in plain English, there are no welcome files, don't bother looking for them anywhere ... You probably aren't getting a response because you didn't answer the question. Your opinion of how things should work isn't really relevant, here. Konstantin asked where Tomcat's behavior violates the servlet spec and you replied by telling him what you think ought to happen. That's not an answer, so you're being ignored. Can you find a place where your seems to tell scenario above is actually supported by language in the servlet specification? If so, tell us where. If the spec isn't clear on a subject, usually the safest thing to do is not change anything because users have become reliant on certain behavior. If and when the spec is clarified, a change will be made. 1. According to XSD, and as illustrated in Figure 14-9 on page #153 (175 of 230) of Servlet 3.0 Rev.a specification, welcome-file-list should contain at least one welcome-file element. 2. welcome-file type is xsd:string and said contains file name to use as a default welcome file. So an empty string formally passes the XSD, but I nowhere see an explicit saying on how to handle it. It certainly is not a file name, but it passes the restriction of not having leading or trailing '/'. The algorithm in ch. 10.10 may work with empty strings (running a fruitless loop - looking for a resource that is already known to not exist), but I am not sure that it is a well-defined behaviour. I'd be nice to have this clarified from the specification team (elsewhere). 3. According to chapter 8.1.6 (page #64, 86/230) of the same spec, welcome file list defaults to contain index.htm(l) and index.jsp. Best regards, Konstantin Kolinko - 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:
welcome-file-list
welcome-file /
/welcome-file-list
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 knst.koli...@gmail.com
To: Tomcat Developers List dev@tomcat.apache.org
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 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
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 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
followed.
Best regards,
Konstantin Kolinko
-
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
welcome-file-list
welcome-file /
/welcome-file-list
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 welcome-file-list /
is ignored and server picks up default values in ${Tomcat.home}/conf/web.xml
Basically, welcome-file-list / should be enough to tell tomcat the same thing
- there are no welcome files
- Original Message -
From: Net Dawg net.d...@yahoo.com
To: dev@tomcat.apache.org 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
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
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 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
followed.
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
