旧 Java Studio Creator 项目到 Icefaces 的迁移选项
我们的项目当前使用非常旧的 Java Studio Creator 框架，现在对未来的部署有新的要求和计划，要求应用程序最终删除 JSC 并迁移到 IceFaces 1.8.x 或 2.0。 对我来说，迁移到 1.8.x 似乎是最安全、最可靠的选择。推迟而不接受迁移 JSF 2.0 的挑战是否有意义，或者应该直接迁移到 IceFaces 2.0？
Our project currently uses the very old Java Studio Creator framework and now has new requirements and plans for future deployments which require the application to finally remove JSC and migrate to either 1.8.x or 2.0 of IceFaces.
A migration to 1.8.x seems to be the safest and most reliable option to take to me. Would delaying and not taking on the challenge of a migration JSF 2.0 make sense or should a migration directly to IceFaces 2.0 be used instead?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
该
我个人建议您只采用 ICEFaces 迁移路径。这是有据可查的。另外，当您迁移到“普通”JSF 2.0 时，您必须重做整个外观，因为“普通”JSF 组件不附带任何捆绑的 CSS。使用 ICEFaces 1.8 或 2.0 并不那么重要。要利用 ICEFaces 2.0 背后的新 JSF 2.0 功能，您只需要随后更改许多其他内容，但即使没有这些，您也应该已经有了一个工作项目。
That
<webuijsf:xxx>component library is called "Woodstock". Now you have new and solid keyword. ICEFaces was officially been pointed as recommended replacement of Woodstock projects when Woodstock was officially been abandoned and discontinued.I personally recommend you to just take the ICEFaces migration path. It's well documented. Also, when you migrate to "plain" JSF 2.0, you'll have to redo the entire look'n'feel as "plain" JSF components does not ship with any bundled CSS. Going to ICEFaces 1.8 or 2.0 doesn't really matter that much. To take advantage of new JSF 2.0 features behind ICEFaces 2.0 you'll only have to change a lot of other things afterwards, but even without that, you should already have a working project.