[
https://jira.jboss.org/browse/JBAS-8224?page=com.atlassian.jira.plugin.sy...
]
Remy Maucherat resolved JBAS-8224.
----------------------------------
Resolution: Rejected
I have rejected this many times for Tomcat. Although this looks like a great idea on
paper, it cannot actually work in many cases. So use a physical marker file.
Servlet container should allow welcome file to be a servlet path (not
just a physical file)
-------------------------------------------------------------------------------------------
Key: JBAS-8224
URL:
https://jira.jboss.org/browse/JBAS-8224
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: 6.0.0.M3
Reporter: Dan Allen
Assignee: Remy Maucherat
Priority: Minor
It appears that the Servlet engine is looking for the existence of the welcome file in
the web context before forwarding to it. This causes problems if you want to use a JSF
view as your welcome file. In JSF, a translation occurs between the actual Servlet path
and the view that gets rendered (the view ID). So if my welcome path is index.jsf, then
the file is going to be index.xhtml (or whatever the default suffix is for JSF).
The way I think it should work is that when the last welcome file is being processed, if
that file cannot be located, assume it's a servlet path and just forward to it.
(While I agree the concept of a welcome file should probably be rethought in the Servlet
spec, GlassFish supports the requested feature and therefore we should offer it as
"add-on" as well).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira