JSF - 组件库，迁移还是不迁移? [英] JSF - Component Libraries, migrate or not migrate?

问题描述

我正在使用一个名为 Woodstock 的旧组件库.每当我尝试更改某些内容时，我都会陷入找不到有关该库的足够文档的困境.我正在考虑迁移到另一个库，例如 ICE Faces 或 Prime Faces.但我怀疑迁移到另一个图书馆会在 3-4 年内得到相同的结果，没有文档，不再支持.我应该使用JSF标准库，不再使用组件库，还是有一个库可以使用超过3年

I am using an old component library called Woodstock. Whenever I try to change something I get stuck with not find finding adequate documents about this library. I am thinking about migrating to another library like ICE Faces or Prime Faces. But I suspect that migrating to another library will end up with the same result in 3-4 years, no documents, no support anymore. Should I use JSF standard library and not use component libraries anymore, or is there a library that lasts more than 3 years

推荐答案

伍德斯托克相当独特.Woodstock 组件通常生成 JavaScript 代码而不是 HTML 代码.该 JavaScript 代码反过来在页面加载时生成 HTML DOM 树.毕竟，尤其是自 Firefox 3 发布以来，所有基于 Woodstock 的网站都立即崩溃了，生成的 JavaScript 代码不符合标准.这是伍德斯托克发明者/开发商的一个重大错误.修复它为时已晚.

Woodstock was rather unique. The Woodstock components generates generally JavaScript code instead of HTML code. That JavaScript code in turn generates the HTML DOM tree on page load. After all, especially since the release of Firefox 3 where all Woodstock based websites instantly broke, that generated JavaScript code was not standards compliant. This was a major mistake of the Woodstock inventors/developers. It was too late to fix it.

IceFaces、RichFaces、PrimeFaces 等都有一个强大的组件库，可以生成符合标准的 HTML/JS 代码，其中跨浏览器敏感的 JS 任务被委托给第三方 JS 库，例如 jQuery.目前，这些 JSF 组件库仍在积极维护中.我知道您永远无法事先预测到这一点，但我不希望它们在 5 年内消失.

IceFaces, RichFaces, PrimeFaces, etc have all a robust component library which generate standards compliant HTML/JS code wherein the cross browser sensitive JS tasks are delegated to a 3rd party JS library such as jQuery. Currently those JSF component libraries are still actively maintained. I know that you can never predict this beforehand, but I wouldn't expect them to disappear in 5 years or something.

这篇关于JSF - 组件库，迁移还是不迁移?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！