Java EE6 优于 EE5?

发布于 2024-08-10 20:50:34 字数 402 浏览 9 评论 0原文

我们即将获得Java EE6(以 Glassfish v3 作为参考实现)。计划发布时间为 12 月 9 日。虽然仍有相当多的公司正在努力将其代码库从早期版本迁移到 EE5,但我们处于开始开发新产品的有利条件,并且可以选择使用 EE6 作为平台。这可能避免后期的迁移工作,并受益于 EE6 中的所有调整大小的功能。

相反或很少有问题(当在前沿做事时,又名使用 EE6):

  • 还没有太多专业知识(博客、书籍、论坛、您自己,..)
  • 很快不会有任何其他 EE6 应用程序服务器(测试版可能还早) /明年中旬?)
  • 第 3 方库/框架可能尚未针对 EE6 进行验证或测试。

这是一个一般性问题,不会产生具体答案,但也许您对此主题的看法?

斯文

We are at the edge of getting Java EE6 (with Glassfish v3 as reference implementation). Planned release is December 09. While still quite a number of companies are struggling to move their codebase to EE5 (from earlier versions), we are in the luxurious situation to start development of a new product and could choose to do it with EE6 as platform. That potentially avoids the migration effort at a later stage and benefit from all the rightsized features in EE6.

Contra or few of the problems (when doing things at the bleeding edge, aka using EE6):

  • not much expertise around yet (blogs, books, forums, yourself,..)
  • there wont be any other EE6 application server soon (beta's maybe early/mid next year ?)
  • 3rd party libraries/frameworks are maybe not verified or tested against EE6 yet.

A generic question that would not result in a specific answer, but maybe your take on the topic ?

Sven

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

反目相谮 2024-08-17 20:50:34

如果您有条件使用 EE6 启动一个项目,那么我建议您先行。

不仅整体体验会在短时间内变得重要(假设 EE6 将在不到两年的时间内成熟并广泛使用,想象一下当所有公司都会转向时有一群 Java EE6 专家),而且 EE6 比 EE5 简单得多,因此,如果团队中的成员只有一点 Java EE 经验,那么您可能会更快地完成工作。

已经有一本关于使用 Glassfish v3 的 Java EE6 的书,其基础知识与之前的版本并没有什么不同(也就是说,如果您坚持从 EE5 中学到的知识,那么您在很长一段时间内都会没问题)时间)。如果您需要 Java EE6 的 RI,Glassfish v3 就非常合适。

您需要什么样的第三方库?

If you are in a luxurious situation to start a project with EE6, then I'd suggest to pioneer.

Not only the overall experience will matter in a short time (let's say EE6 will be mature and widely used in less than two years, imagine a bunch of Java EE6 experts when all the companies will switch), but EE6 is just plain simpler than EE5, so if you have members in the team that have only a little experience in Java EE, you'll probably get your job done faster.

There's already a book on Java EE6 with Glassfish v3, and the basics is not that different from the previous version (ie. if you stick to what you know from EE5, you'll be fine for a long time). Glassfish v3 is quite okay if you need the RI for Java EE6.

What kind of 3rd party libraries do you need?

你与清晨阳光 2024-08-17 20:50:34

该项目有多大、有多重要?你们有截止日期吗?我真的很渴望新技术或框架,但我宁愿建议从 Java EE 5 开始,然后逐渐迁移到 Java EE 6。Java EE 这是一个很大的技术堆栈,在发布时,其中一些技术将得不到第三方的足够支持派对供应商。所以我的建议是:使用 Java EE 6 中目前已经成熟并且得到其他供应商大力支持的这些部分。

How big and important is the project? Do you have any deadlines? I'm really eager to new technologies or frameworks but I rather suggest to begin with Java EE 5 and gradually migrate to Java EE 6. Java EE it's a big stack of technologies and in release time some of them will have not enough support from third party vendors. So my advice is: use these part of Java EE 6 that are mature at this time and have strong support from others vendors.

静若繁花 2024-08-17 20:50:34

在完成之前,Java EE 7 无论如何都会发布。去做吧,并在这个过程中学习。

Before you are done Java EE 7 will be out anyway. Go for it, and learn in the process.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文