本文介绍了在JSF 2中,faces-config.xml的用途是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在JSF 2对注释的大力支持之后,我想知道将faces-config.xml用于什么.现在它的重要性是什么?

After the JSF 2 big support for annotations, I'm wondering what I would use the faces-config.xml for. What is its importance now?

换句话说,只能通过faces-config.xml而不通过注释完成的配置是什么?

In other words, what are the configurations that can only be done through faces-config.xml and not via annotations?

现在我所使用的只是声明Spring的EL解析器.

Right now all what I am using it for is to declare Spring's EL resolver.

<?xml version="1.0" encoding="UTF-8"?>
<faces-config
    xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
    http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"
    version="2.0">

    <application>
        <el-resolver>
            org.springframework.web.jsf.el.SpringBeanFacesELResolver
        </el-resolver>
    </application>
</faces-config>

推荐答案

它仍然用于许多无法注释的内容.例如.自定义JSF验证消息:

It's still to be used for many things which can't be annotated. E.g. custom JSF validation messages:

<application>
    <message-bundle>com.example.i18n.messages</message-bundle>
</application>

全局i18n捆绑包(因此您无需在每个视图中声明<f:loadBundle>):

A global i18n bundle (so that you don't need to declare <f:loadBundle> in every view):

<application>
    <resource-bundle>
        <base-name>com.example.i18n.Text</base-name>
        <var>text</var>
    </resource-bundle>
</application>

明确支持的i18n语言环境(即使存在消息包或资源包,未声明的区域也将被忽略):

Explicitly supported i18n locales (so that the not-declared ones will be ignored even though there's a message bundle or resource bundle for it):

<application>
    <locale-config>
        <default-locale>en</default-locale>
        <supported-locale>nl</supported-locale>
        <supported-locale>es</supported-locale>
        <supported-locale>de</supported-locale>
    </locale-config>
</application>

自定义视图处理程序:

<application>
    <view-handler>com.example.SomeViewHandler</view-handler>
</application>

阶段监听器(目前尚无注释):

Phase listeners (there's still no annotation for that):

<lifecycle>
    <phase-listener>com.example.SomePhaseListener</phase-listener>
</lifecycle>

无法注释的托管bean(以下一个给出了#{now}上的当前Date):

Managed beans which can't be annotated (the below one gives current Date on #{now}):

<managed-bean>
    <description>Current date and time</description>
    <managed-bean-name>now</managed-bean-name>
    <managed-bean-class>java.util.Date</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
</managed-bean>

自定义工厂,例如自定义异常处理程序工厂(它还允许 FacesContext ExternalContext LifeCycle 等,以便您可以提供自定义实现):

Custom factories, such as custom exception handler factory (it also allows factories for FacesContext, ExternalContext, LifeCycle and many more so that you can provide your custom implementation):

<factory>
    <exception-handler-factory>com.example.SomeExceptionHandlerFactory</exception-handler-factory>
</factory>

仅列出常用名称.如果您的IDE中具有faces-config.xml标记自动补全功能,则可以全部找到它们.借助新的注释和隐式导航,不再需要托管的Bean,验证器,转换器,组件,渲染器和点对点导航用例.

To name only the commonly used ones. If you have faces-config.xml tag autocompletion in your IDE, you can find them all out. Only the managed beans, validators, converters, components, renderers and point-to-point navigation cases are not needed anymore thanks to the new annotations and implicit navigation.

这篇关于在JSF 2中,faces-config.xml的用途是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-03 03:08