登录
当前位置： 首页 > 知识库问答 >
问题：

在WEB-INF中使用错误页的FacesExceptionFilter OmniFaces

乐正涵意
2023-03-14

我需要一些帮助在使用一个OmniFaces功能。

我有以下web.xml配置

<?xml version="1.0" encoding="UTF-8"?>

<display-name>xxxxx</display-name>

<session-config>
    <session-timeout>1</session-timeout>
</session-config>

<welcome-file-list>
    <welcome-file>pages/secured/main.xhtml</welcome-file>
</welcome-file-list>

<servlet>
    <servlet-name>facesServlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>

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

<context-param>
    <param-name>javax.servlet.jsp.jstl.fmt.localizationContext</param-name>
    <param-value>resources.application</param-value>
</context-param>

<context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>client</param-value>
</context-param>

<context-param>
    <param-name>contextConfigLocation</param-name>
    <param-value>/WEB-INF/spring-application-context.xml</param-value>
</context-param>

<context-param>
    <param-name>facelets.DEVELOPMENT</param-name>
    <param-value>true</param-value>
</context-param>

<context-param>
    <param-name>javax.faces.FACELETS_REFRESH_PERIOD</param-name>
    <param-value>2</param-value>
</context-param>

<context-param>
    <param-name>primefaces.THEME</param-name>
    <param-value>mytheme</param-value>
</context-param>

<context-param>
    <param-name>javax.faces.FACELETS_LIBRARIES</param-name>
    <param-value>/WEB-INF/springsecurity.taglib.xml</param-value>
</context-param>

<context-param>
    <param-name>javax.faces.SEPARATOR_CHAR</param-name>
    <param-value>_</param-value>
</context-param>

<listener>
    <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>

<listener>
    <listener-class>com.bdo.corpsoa.utilities.security.listeners.impl.CorpSoaSessionListener</listener-class>
</listener>

<filter>
    <filter-name>facesExceptionFilter</filter-name>
    <filter-class>org.omnifaces.filter.FacesExceptionFilter</filter-class>
</filter>

<filter-mapping>
    <filter-name>facesExceptionFilter</filter-name>
    <servlet-name>facesServlet</servlet-name>
</filter-mapping>


<context-param>
    <param-name>org.omnifaces.FACES_VIEWS_SCAN_PATH</param-name>
    <param-value>/*.xhtml</param-value>
</context-param>

<context-param>
    <param-name>org.omnifaces.FACES_VIEWS_PATH_ACTION</param-name>
    <param-value>REDIRECT_TO_SCANNED_EXTENSIONLESS</param-value>
</context-param>

<!-- <filter> <filter-name>springSecurityFilterChain</filter-name> <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class> 
    </filter> <filter-mapping> <filter-name>springSecurityFilterChain</filter-name> 
    <url-pattern>/*</url-pattern> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> 
    </filter-mapping> -->

<error-page>
    <exception-type>javax.faces.application.ViewExpiredException</exception-type>
    <location>/WEB-INF/pages/errors/viewExpired.xhtml</location>
</error-page>

<error-page>
    <exception-type>java.lang.RuntimeException</exception-type>
    <location>/WEB-INF/pages/errors/unHandled.xhtml</location>
</error-page>

<error-page>
    <error-code>404</error-code>
    <location>/WEB-INF/pages/errors/pageNotFound.xhtml</location>
</error-page>

<error-page>
    <exception-type>java.io.FileNotFoundException</exception-type>
    <location>/WEB-INF/pages/errors/pageNotFound.xhtml</location>
</error-page>

然而，当异常发生时，用户只会被重定向到默认的500错误页面。

只有当我将错误页移出WEB-INF文件夹/WEB-INF/pages/errors/pagenotfound.xhtml-->/pages/errors/pagenotfound.xhtml时，重定向才会起作用

但这意味着现在可以直接访问错误页。但在Omnifaces展示中，这应该是可能的。我不知道我错过了什么请帮帮我...

下面是Omnifaces展示案例的web.xml，它显示WEB-INF中的错误页面是可能的。

<?xml version="1.0" encoding="UTF-8"?>

    <display-name>OmniFaces Showcase</display-name>


    <!-- Standard JSF settings. -->

    <context-param>
            <param-name>javax.faces.FACELETS_BUFFER_SIZE</param-name>
            <param-value>65535</param-value> <!-- 64KB. -->
    </context-param>
    <context-param>
        <param-name>javax.faces.FACELETS_REFRESH_PERIOD</param-name>
        <param-value>0</param-value> <!-- Should be -1 for production. -->
    </context-param>
    <context-param>
            <param-name>javax.faces.FACELETS_LIBRARIES</param-name>
            <param-value>/WEB-INF/showcase.taglib.xml</param-value>
    </context-param>
    <context-param>
            <param-name>javax.faces.FACELETS_SKIP_COMMENTS</param-name>
            <param-value>true</param-value>
    </context-param>


    <!-- Mojarra/RI specific settings. -->

    <context-param>
            <param-name>com.sun.faces.defaultResourceMaxAge</param-name>
            <param-value>3628800000</param-value> <!-- 6 weeks. -->
    </context-param>


    <!-- MyFaces specific settings. -->

    <context-param>
            <param-name>org.apache.myfaces.RESOURCE_MAX_TIME_EXPIRES</param-name>
            <param-value>3628800000</param-value> <!-- 6 weeks. -->
    </context-param>
    <context-param>
            <!--
                    MyFaces and Mojarra don't agree on the default setting for actually serializing state
                    in the session as opposed to just storing a reference. Mojarra's default is false, but
                    can be switched to true. MyFaces' default is true, and can be switched to false, which
                    we thus do below. See http://arjan-tijms.omnifaces.org/p/jsf-22.html#1127
             -->
            <param-name>org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</param-name>
            <param-value>false</param-value>
    </context-param>


    <!-- OmniFaces specific settings. -->

    <context-param>
            <param-name>org.omnifaces.CACHE_SETTING_SESSION_MAX_CAPACITY</param-name>
            <param-value>6</param-value>
    </context-param>
    <context-param>
            <!--
                    All files in the 3 paths defined below will be scanned and made available
                    as extensionless JSF views. Since no explicit extension is given for scanning,
                    these paths should contain ONLY JSF (Facelets) files.
             -->
            <param-name>org.omnifaces.FACES_VIEWS_SCAN_PATHS</param-name>
            <param-value>/showcase,/etc,/demo</param-value>
    </context-param>
    <context-param>
            <!--
                    Redirects the faces views scanned /showcase/[PAGE].xhtml to /[PAGE].
                    A 404 would normally be preferred (and this is thus the default), but the showcase app
                    already has published /showcase/[PAGE].xhtml
            -->
            <param-name>org.omnifaces.FACES_VIEWS_PATH_ACTION</param-name>
            <param-value>REDIRECT_TO_SCANNED_EXTENSIONLESS</param-value>
    </context-param>


    <!-- Servlets and filters. -->

    <servlet>
            <servlet-name>facesServlet</servlet-name>
            <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
            <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
            <servlet-name>facesServlet</servlet-name>
            <url-pattern>*.xhtml</url-pattern>
    </servlet-mapping>

    <filter>
            <filter-name>characterEncodingFilter</filter-name>
            <filter-class>org.omnifaces.filter.CharacterEncodingFilter</filter-class>
    </filter>
    <filter-mapping>
            <filter-name>characterEncodingFilter</filter-name>
            <url-pattern>/*</url-pattern>
    </filter-mapping>

    <filter>
            <filter-name>facesExceptionFilter</filter-name>
            <filter-class>org.omnifaces.filter.FacesExceptionFilter</filter-class>
    </filter>
    <filter-mapping>
            <filter-name>facesExceptionFilter</filter-name>
            <servlet-name>facesServlet</servlet-name>
    </filter-mapping>

    <filter>
            <filter-name>gzipResponseFilter</filter-name>
            <filter-class>org.omnifaces.filter.GzipResponseFilter</filter-class>
    </filter>
    <filter-mapping>
            <filter-name>gzipResponseFilter</filter-name>
            <url-pattern>/*</url-pattern>
            <dispatcher>REQUEST</dispatcher>
            <dispatcher>ERROR</dispatcher>
    </filter-mapping>


    <!-- Welcome files, error pages and mime types. -->
    
    <session-config>
            <cookie-config>
                    <http-only>true</http-only>
            </cookie-config>
            <tracking-mode>COOKIE</tracking-mode>
    </session-config>

    <welcome-file-list>
            <!--
                    Note that an extension is used here, since the index file resides within the
                    root which has not been configured for FacesViews scanning.
            -->
            <welcome-file>index.xhtml</welcome-file>
    </welcome-file-list>

    <error-page>
            <exception-type>javax.faces.application.ViewExpiredException</exception-type>
            <location>/WEB-INF/errorpages/expired.xhtml</location>
    </error-page>
    <error-page>
            <exception-type>java.sql.SQLException</exception-type>
            <location>/WEB-INF/errorpages/database.xhtml</location>
    </error-page>
    <error-page>
            <exception-type>java.lang.RuntimeException</exception-type>
            <location>/WEB-INF/errorpages/bug.xhtml</location>
    </error-page>
    <error-page>
            <error-code>500</error-code>
            <location>/WEB-INF/errorpages/500.xhtml</location>
    </error-page>
    <error-page>
            <error-code>404</error-code>
            <location>/WEB-INF/errorpages/404.xhtml</location>
    </error-page>

    <mime-mapping>
            <!--
                    Silence WebLogic's annoying "JSF1091: No mime type could be found for file" warning.
            -->
            <extension>xhtml</extension>
            <mime-type>text/html</mime-type>
    </mime-mapping>
  1. 如果在WEB-INF之外，重定向到错误页可以工作。
  2. Showcase显示这应该是可能的。
  3. 我需要帮助...

谢谢你抽出时间

编辑

   <?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
    xmlns:ui="http://java.sun.com/jsf/facelets"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:p="http://primefaces.org/ui">

<h:body>
    <h1>#{"XXXXXXXX"}</h1>

</h:body>
</html>

即使在WEB-INF之外，也不会显示此错误页。这将导致默认的404页面

 <?xml version="1.0" encoding="ISO-8859-1" ?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"
        xmlns:ui="http://java.sun.com/jsf/facelets"
        xmlns:h="http://java.sun.com/jsf/html"
        xmlns:f="http://java.sun.com/jsf/core"
        xmlns:p="http://primefaces.org/ui">
    
    <h:body>
        <h1>ZZZZZZZZZ</h1>
    
    </h:body>
    </html>

共有1个答案

景令秋
2023-03-14

由于某些原因，此错误页将无法工作，并将生成默认的404页。

<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
    xmlns:ui="http://java.sun.com/jsf/facelets"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:p="http://primefaces.org/ui">

<h:body>
    <h1>ZZZZZZZZZ</h1>
</h:body>
</html>

然而，此错误页将工作。

 <?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
    xmlns:ui="http://java.sun.com/jsf/facelets"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:p="http://primefaces.org/ui">

<h:body>
    <h1>#{"XXXXXXXX"}</h1>
</h:body>
</html>
 类似资料：
  • Tomcat和Spring上/WEB-INF URI的自定义错误页

    我通过一个自定义的Spring错误页面来处理所有的404错误。这很好，但有一个例外。URI/WEB-INF首先被Tomcat拦截。将显示默认的Tomcat错误页面。 如何将URI/WEB-INF重定向到另一个URI，例如/404，或者简单地阻止Tomcat拦截它？ 谢谢你！

  • ClassNotFoundException错误，即使jar文件存在于WEB-INF/lib目录中

    我正在尝试设置tomcat服务器，使所有常见的spring jar都进入tomcat lib目录，因为我有很多web应用程序使用spring。然而，我的一个web应用程序也使用了带有quartaz jar的spring batch。当所有JAR都位于app1/web-INF/lib目录中时，这个web应用程序工作正常。然而，当我试图将所有常见的spring jar移动到tomcat/lib目录以及

  • Spring配置错误WEB-INF/servlet-context.xml FileNotFoundException

    我有一个非常简单的Spring测试应用程序。但我得到了例外，即使一切似乎都井然有序。我可能漏掉了什么。请检查pic查看项目结构和web.xml文件中包含的内容以及异常：- eFinitionStoreException：IOException从类路径资源[WEB-INF/servlet-context.XML]解析XML文档；嵌套异常是java.io.FileNotFoundException：无

  • 使用maven将webapp/WEB-INF/lib中的JAR复制到web-INF/lib下的war

    我在webapp/WEB-INF/lib/文件夹下添加了一个依赖项。 当我使用maven构建时，我希望在war中将它复制到WEB-INF/lib，而不是WEB-INF/classes/WEB-INF/lib。我正在寻找这是使用maven本身来完成的。 我已经在pom文件中提到了打包作为战争，但是依赖项没有被复制。我是不是在pom文件里漏掉了什么。我已经复制了下面的pom： 附上战争内容截图。

  • 使用Maven pom.xml在WAR中创建除WEB-INF&META-INF以外的目录

  • WEB-INF是否在CLASSPATH中？

    问题内容： 该文件夹位于Java Web应用程序的中吗？ 问题答案： 我假设您要引用Web应用程序文件夹结构根 目录 中的目录。 不，它不在类路径中。 不过在classpath上，中的JAR文件也是如此。

相关问答

使用Maven pom.xml在WAR中创建除WEB-INF&META-INF以外的目录WEB-INF在JavaEE Web应用程序中用于什么？Web App中Java动态错误页面？使用SpringBoot、SpringMVC和Maven的WebApp中不包含WEB-INF在ColdFusion WEB-INF库中更改JAR文件

相关文章

如何在Eclipse的web-inf / lib文件夹中添加JAR文件？使用：=给出未使用的错误，但是使用=不在Go中如何处理HTML5 Web Worker中的错误？Javawar / WEB-INF文件夹中资源的文件路径？为什么WEB-INF文件夹内的jsp文件可以工作，而不能放在WEB-INF下的文件夹下？

相关阅读

Lua 错误处理MySQL错误日志SLF4J错误消息VBA错误处理中国移动在线营销中心 web前端岗

相关工具

中间翻页Tcl Web应用框架webGemini WebSOCKO WEB

相关文档

Web Hacking 101 中文版Spring Web Services 中文文档百度 Web Uploader 中文文档Agile Web Development with Rails 4 中文版Sass for Web Designers
快捷导航： 新手教程 算法原理 架构设计 Java进阶 数据库进阶 大厂专栏 面试经验 编程笔记 编程问答 所有专题 文档资料 工具软件 电子书籍 小牛导航
在线工具： 房贷计算器 个税计算器 Linux命令查询 Json格式化 正则表达式 颜色转换 AES加解密 SHA1加密 MD5加密 毒鸡汤 字数统计 随机密码生成 进制转换 Base64编解码 励志句子
Copyright © 2019-2024 小牛知识库@xnip.cn. All Rights Reserved.