使用JSF、PrimeFaces与WebSphere无法访问首页，疑web.xml配置有误

Hey there! Let's break down why you're seeing that "page not found" error after launching your WebSphere server. While your web.xml snippet is cut off, there are several common issues to check—starting with configuration, then moving to project structure and server setup.

1. Verify Faces Servlet Mapping in web.xml #

JSF relies on the FacesServlet to route requests to your XHTML pages. If this isn't configured correctly, the server won't know how to handle your page requests. Here's what a proper configuration looks like:

<servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <!-- Map to your page suffix—most commonly *.xhtml -->
    <url-pattern>*.xhtml</url-pattern>
</servlet-mapping>

Double-check that:

• The url-pattern matches the suffix of your actual pages (e.g., if you use *.jsf but your files end with .xhtml, this will break).
• The FacesServlet is set to load on startup (<load-on-startup>1</load-on-startup>) to ensure it's initialized when the server starts.

2. Confirm Web App Context Root #

WebSphere uses a context root to identify your application. If your URL doesn't include this correctly, you'll get a 404.

• For Maven projects, the context root is often derived from the <finalName> in your web module's pom.xml:

  <build>
      <finalName>your-app-context-root</finalName>
  </build>
  

• You can also verify/set it directly in WebSphere's admin console: Go to Applications > Application Types > WebSphere enterprise applications > [Your App] > Context Root for Web Modules.
• Your full access URL should look like: http://localhost:[port]/your-app-context-root/your-page.xhtml

3. Check PrimeFaces and JSF Compatibility with WebSphere #

WebSphere comes with its own bundled JSF implementation, which might conflict with the version you're using in your Maven project. To force WebSphere to use your project's JSF/PrimeFaces libraries, add these context parameters to web.xml:

<!-- Use project's JSF implementation instead of WebSphere's bundled one -->
<context-param>
    <param-name>com.ibm.ws.jsf.JSF_IMPL_CLASSLOADER_POLICY</param-name>
    <param-value>PARENT_LAST</param-value>
</context-param>
<!-- Optional: Enable development mode for easier debugging -->
<context-param>
    <param-name>javax.faces.PROJECT_STAGE</param-name>
    <param-value>Development</param-value>
</context-param>

Also, make sure your PrimeFaces version is compatible with your JSF version (e.g., PrimeFaces 10 works with JSF 2.3, PrimeFaces 8 with JSF 2.2).

4. Validate Multi-Module Maven Structure #

Since you have a two-module project:

• Ensure your web module is packaged as a war (check <packaging>war</packaging> in its pom.xml).
• Confirm that any dependent modules (e.g., EJBs or utility jars) are correctly included in the web module's WEB-INF/lib directory after building. Missing dependencies can cause initialization failures that lead to 404 errors.

5. Check Page Placement #

Your XHTML pages should be placed in the root of your web module (src/main/webapp/) or a subdirectory under it—not inside WEB-INF (files in WEB-INF are not directly accessible via URL). For example, if your page is at src/main/webapp/index.xhtml, the URL should be http://localhost:[port]/context-root/index.xhtml.

Quick Debugging Steps #

• Check WebSphere's SystemOut.log (usually in [profile]/logs/server1/) for any startup errors—look for exceptions related to JSF initialization, missing classes, or configuration issues.
• Test with a simple index.xhtml page first to rule out complex page logic as the cause:

  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE html>
  <html xmlns="http://www.w3.org/1999/xhtml"
        xmlns:h="http://xmlns.jcp.org/jsf/html">
  <h:head>
      <title>Test Page</title>
  </h:head>
  <h:body>
      <h1>Hello from JSF!</h1>
  </h:body>
  </html>
  

内容的提问来源于stack exchange，提问作者user3198205