Set default home page via in JSF project

by

First of all, the <welcome-file> does not represent the path to the “default home page”. It represents the filename of the physical file contained in the folder which you’d like to serve up as default file when a folder like /, /foo/, /foo/bar/, etc is requested.

So, in JSF 2.x flavor, that would basically be:

<welcome-file-list>
    <welcome-file>index.xhtml</welcome-file>
</welcome-file-list>

This way, if the enduser requests / and you have /index.xhtml, then it will be served. Or, if the enduser requests /foo and you have /foo/index.xhtml, then it will be served, etc. If there is no such file, then a 404 error will be returned.

Now, you appear to have mapped your FacesServlet on a prefix <url-pattern> of /faces/*. This is a leftover from JSF 1.0/1.1 ages and really not recommended these days. Perhaps you were reading an outdated tutorial targeted at JSF 1.x, or a poorly maintained tutorial which was originally written for JSF 1.x and then uncarefully updated for JSF 2.x instead of rewritten from scratch.

That tutorial did also not seem to have explained you some servlet basics. Namely, in order to get JSF components in the XHTML page to run and generate some HTML output, the FacesServlet has to be invoked when the XHTML page is being requested. When you request the XHTML page like so /index.xhtml, while the FacesServlet is being mapped on /faces/*, then it won’t be invoked. The browser would then retrieve the raw unparsed JSF source code instead of the generated HTML output. You can see it by rightclick, View Source in webbrowser. You should have requested the page like so /faces/index.xhtml so that the FacesServlet can run and produce HTML output which the browser can understand and present.

That only doesn’t go well together with welcome files. This totally explains why you get a “clean white” (blank) page when using index.xhtml as welcome file (some inferior webbrowsers like IE would confusingly prompt a download dialog because of missing/wrong content type on the response containing raw XHTML source code). The FacesServlet was simply not being invoked. Just get rid of the old fashioned /faces/* URL pattern and use the JSF 2.x minded *.xhtml URL pattern instead.

<servlet-mapping>
    <servlet-name>facesServlet</servlet-name>
    <url-pattern>*.xhtml</url-pattern>
</servlet-mapping>

This way the welcome files should work and you can just open JSF pages by directly requesting its physical URL without hassling with virtual URLs. This was not possible in JSF 1.x because it would let the FacesServlet run in an infinite loop calling itself and cause a stack overflow.

See also:

As to those warnings, they are unrelated but quite googlable.

More Related Contents:

  1. HTTP Status 404 – The requested resource (/ProjectName/) is not available
  2. java.lang.IllegalArgumentException: The servlets named [X] and [Y] are both mapped to the url-pattern [/url] which is not permitted
  3. Structure for multiple JSF projects with shared code
  4. ClassNotFoundException when using User Libraries in Eclipse build path
  5. Tomcat started in Eclipse but unable to connect to http://localhost:8085/
  6. EL proposals / autocomplete / code assist in Facelets with Eclipse
  7. What does “The APR based Apache Tomcat Native library was not found” mean?
  8. Remote debugging Tomcat with Eclipse
  9. “Server Tomcat v7.0 Server at localhost failed to start” without stack trace while it works in terminal [closed]
  10. Eclipse “Server Locations” section disabled and need to change to use Tomcat installation
  11. HTTP Status 404 – The requested resource (/) is not available
  12. Method must have signature “String method() …[etc]…” but has signature “void method()”
  13. java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
  14. How to use Tomcat 8 in Eclipse?
  15. java.lang.IllegalArgumentException: The main resource set specified […] is not valid
  16. Change Tomcat Server’s timeout in Eclipse
  17. Where is the deployment directory in Eclipse?
  18. Unit-testing servlets [closed]
  19. TOMCAT – HTTP Status 404 [duplicate]
  20. NLS missing message: CANNOT_FIND_FACELET_TAGLIB
  21. how to debug JSF/EL
  22. Multiple contexts with the same path error running web service in Eclipse using Tomcat
  23. Eclipse on-click deploy to remote Tomcat
  24. Running Maven project on Tomcat from Eclipse
  25. Tomcat Not Starting Through Eclipse (Timeout)
  26. How to add a library to an Eclipse project
  27. java.lang.ClassNotFoundException: org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter when starting Simple Struts2 Application
  28. Visual Studio’s keybindings for Eclipse
  29. Eclipse Intellisense?
  30. How to run a batch script (.bat file) from eclipse

Leave a Comment