从 Wicket 1.3.7 升级到 1.4.9 时有哪些主要优势？
我正在考虑将大型 Web 应用程序从 Wicket 1.3.7 迁移到 Wicket 1.49。由于 1.4 版本中一些基本的事情发生了变化，这将需要相当大的努力。
除了使用泛型之外，升级的主要好处是什么？根据我所读到的内容，我不确定这些好处是否会为迁移工作带来回报。你的意见是什么？
I am thinking about migrating a large web app from Wicket 1.3.7 to Wicket 1.49. As some basic things have changed with version 1.4, this will be quite some effort.
Apart from getting to use generics, what would be the key benefits of upgrading? From what I have read, I am not sure whether the benefits pay off for the migration effort. What is your opinion?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
1.4.0 和 1.4.9 之间的差异主要是错误修复和细微改进，因此您的问题实际上可以归结为从 1.3 到 1.4 的好处。一个警告：
您提到的泛型无疑是最明显的变化，并且可能会发生变化如果您对警告感到恼火，则需要做最多的工作。请参阅有关升级的 Wicket wiki 和 扩展新闻帖子了解更多信息更改的完整列表。
我的工作团队几个月前进行了迁移，并没有注意到任何大的影响，无论好坏。更新仿制药参考确实花了几个小时，但知道您也没有使用过时的技术会让人感到一些安慰。我们在这里不使用 Spring，但据说 1.4 比以前的版本与 Spring 兼容得多。
就您而言，这可能只是您觉得更烦人的事情：花费几个小时来通用化您的代码或使用处于生命周期结束状态的东西。
The differences between 1.4.0 and 1.4.9 are mostly bugfixes and minor improvements, so your question really boils down to the benefits of going from 1.3 to 1.4. One caveat:
Generics, which you mentioned, certainly are the most visible change, and the one that will likely involve the most work if you are annoyed by warnings. See the Wicket wiki on upgrading and the expanded news post for a more comprehensive list of the changes.
My team at work migrated a few months ago and didn't notice any big effects, good or bad. It did take a few hours to update the generics references, but there's some comfort in knowing you're not using past-end-of-life technology, too. We don't use Spring here, but 1.4 is supposedly much more compatible with Spring than previous versions were.
In your case, it may just come down to what you find more annoying: spending a few hours generifying your code or using something that's in end-of-life status.
我已将 Apache Wicket 加载到 Java 上游跟踪器 服务，该服务对所有版本的 Wicket API 执行向后兼容性分析1.3 至 1.4.15 包括 1.3.7 和 1.4.9 版本。
它可以帮助您调查由 Wicket API 中的不兼容更改引起的升级问题。
I have loaded Apache Wicket to Java upstream tracker service that performed backward compatibility analysis for all versions of Wicket API from 1.3 to 1.4.15 including 1.3.7 and 1.4.9 versions.
It may help you to investigate upgrade issues caused by incompatible changes in Wicket API.