JSF 实现和组件库 [英] JSF implementations and component libraries
问题描述
我刚刚开始使用 JSF，我有三个与 JSF 实现和组件库相关的问题.
I have just started using JSF and I have three questions related to JSF implementations and component libraries.
JSF 实现和组件库之间有什么区别?
What is the difference between JSF Implementations and Component Libraries?
有哪些可用的 JSF 实现(例如 Eclipse Mojarra 和 Apache MyFaces)，它们之间的区别是什么?
What are the various JSF implementations (like Eclipse Mojarra and Apache MyFaces) that are available and what is the difference between each one of them?
有哪些可用的 JSF 组件库(如 PrimeFaces、ICEfaces 和 RichFaces)，它们之间的区别是什么?
What are the various JSF component libraries (like PrimeFaces, ICEfaces and RichFaces) that are available and what is the difference between each one of them?
提供有关此确切信息的任何相关链接也会有所帮助.
Any relevant links giving the exact information on this would also be helpful.
推荐答案
JSF 实现和组件库有什么区别?
JSF 实现实现JSF API规范.它们至少包含标准组件以显示任何可用的基本(普通")HTML 元素.
JSF implementations implement the JSF API Specification. They contains at least the standard components to display any of the available basic ("plain vanilla") HTML elements.
JSF 组件库只是在基本实现之上添加了额外的，通常具有更多的外观、ajaxability、增强性等，因此您只需使用单个组件而不是一堆组件即可对其进行编程组件或自定义组件，最终连同一堆相关的 JS/CSS 代码.
JSF component libraries just adds that extra on top of the basic implementation, often with more skinnability, ajaxability, enhanceability, etcetera, so that you can just program it with a single component instead of a bunch of components or custom components, eventually along with a bunch of related JS/CSS code.
有哪些可用的 JSF 实现(例如 Eclipse Mojarra 和 Apache MyFaces)，它们之间的区别是什么?
目前有两个(主要)JSF 实现，即 Eclipse Mojarra 和Apache MyFaces.技术上没有太大区别，因为它们都只需要遵守 JSF API 规范.而是查看稳健性、文档的可用性、支持级别、维护级别(增强速度、错误修复、发布等)等.另请参阅:Mojarra 和 MyFaces 之间的区别.
There are as far two (major) JSF implementations, namely Eclipse Mojarra and Apache MyFaces. There's technically not much difference as they both just have to adhere the JSF API Specification. Rather look at robustness, availability of documentation, level of support, grade of maintenance (speed of enhancements, bugfixes, releasing, etc), etcetera. See also: Difference between Mojarra and MyFaces.
有哪些可用的 JSF 组件库(如 PrimeFaces、ICEfaces 和 RichFaces)，它们之间的区别是什么?
有很多，我将限制自己使用最常用/最知名的库.如果您想要更多换肤功能，请查看 PrimeFaces (演示), ICEfaces(演示)，ButterFaces (演示)或BootsFaces(演示).RichFaces 自 2016 年起停产.如果您想要更多 ajaxical 功能(除了标准 JSF 已经提供的功能)，请查看 PrimeFaces、ICEfaces 或 BabbageFaces.如果您想要更专业/增强的组件，请查看 PrimeFaces、ICEFaces、PrimeFaces Extensions (PrimeFaces Extensions="https://www.primefaces.org/showcase-ext/views/home.jsf" rel="nofollow noreferrer">演示) 或 多巴哥(演示).不同之处主要在于可用的组件集和可定制程度.
There are lot of them, I'll limit myself to the most used / well known libraries. If you want more skinning capabilities, look at PrimeFaces (demo), ICEfaces (demo), ButterFaces (demo) or BootsFaces (demo). RichFaces is EOL since 2016. If you want more ajaxical capabilities (other than what standard JSF already provides), look at PrimeFaces, ICEfaces or BabbageFaces. If you want more specialized/enhanced components, look at PrimeFaces, ICEFaces, PrimeFaces Extensions (demo) or Tobago (demo). The difference is mainly to be found in the available set of components and the degree of customizability.
此外还有 JSF 实用程序库.您可能会意识到自己每次都在重新发明/重写一些 FacesUtil、JSFUtils 等类和/或自定义标签/组件来解决典型的和重复出现的 JSF 特定问题.OmniFaces(演示) 和 DeltaSpike 提供可重用的 JSF 实用程序标准库，可与任何 JSF 结合使用实现和组件库.
Further there are also JSF utility libraries. You'll probably recognize yourself reinventing/rewriting some FacesUtil, JSFUtils, etc classes everytime and/or custom tags/components to solve typical and recurring JSF-specific problems. OmniFaces (demo) and DeltaSpike provide a reuseable standard library of JSF utilities which can be used in combination with any JSF implementation and component library.
这篇关于JSF 实现和组件库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
