blocks|key|3253488|text|我不知道TomEE+--我想如果您只是想部署到一个不同的J2EE容器中，那么您应该已经这样做了&不需要修改代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3253489|也就是说，这意味着您想要远离EE。|3253490|除非您有或将需要“分布式事务”或消息传递支持(例如，来往于IBM大型机)，否则我的观点是J2EE在很大程度上是一个失败的架构。|3253491|Tomcat、Spring和Hibernate基本上都是它自己的(不使用JPA包装器或API，它们大多只是从Hibernate最初的成功中复制出来的一个额外的山寨层)。|3253492|如果你使用HB+config的注解，你可以在代码中使用Hibernate+API时使用/组合JPA注解(有时它们有更清晰的语法)。|3253493|干杯，希望这能帮上忙。|3253494|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I don't know about TomEE -- I expect if you just wanted to deploy into a different J2EE container, you'd do that already &amp; not be needing to modify the code.

That said, the implication is that you want to move away from EE.

Unless you have or will need 'distributed transactions' or messaging support (eg, to/from IBM mainframes) my opinion is that J2EE is largely a failed architecture.

Tomcat, Spring &amp; Hibernate pretty much on it's own (not using the JPA wrappers or API, which are mostly just an extra rip-off layer copying from Hibernate's original success) are what I recommend.

If you go annotations for HB config, you can use/combine the JPA ones (sometimes they have clearer syntax) while using the Hibernate API in code.

Cheers, hope this helps.

blocks|key|5930050|text|以下是一些要点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5930051|5930052|Hibernate是一个JPA实现，是三个实现之一。Hibernate的创建者Gavin+King在JPA上付出了令人难以置信的努力。从应用程序中移除所有JPA使用是向后移动，而不是向前移动。|unordered-list-item|5930053|您可以在带有或不带有TomEE的Tomcat中使用JPA。|5930054|5930055|就痛恨Java+EE并想要远离它而言，这真的成为一项不可能完成的任务。所有这些技术都是Java+EE的一部分：|5930056|5930057|Servlets|5930058|JSP|5930059|JSF|5930060|JPA|5930061|EJB|5930062|CDI+/+@Inject|5930063|JAX-RS|5930064|JAX-WS|5930065|JMS|5930066|Bean+Validation|5930067|5930068|将它们中的一些标记为JavaEE，另一些标记为非JavaEE，这是一种否认形式。它们都是作为JavaEE的一部分创建和发布的。|5930069|要理清一些反JavaEE营销所造成的混乱几乎是不可能的。真正具有破坏性的是，几乎不可能找到一个不使用3种或更多JavaEE技术的“非JavaEE”应用程序。|5930070|为了回答“繁重”和“太多”的问题，在2010年创建了Web配置文件，以便可以在不牺牲可移植性的情况下创建较小的运行时。它包括：|5930071|5930072|5930073|5930074|5930075|5930076|EJB+(lite)|5930077|CDI+/+@Inject|5930078|Bean+Validation|5930079|5930080|没有分布式事务，也没有繁重的东西。如果堆叠Tomcat、Hibernate和Spring，您将包括：|5930081|5930082|5930083|5930084|5930085|@Inject|5930086|Bean+Validation|5930087|5930088|无论您是否选择使用这些API，它们都将存在。|5930089|使用实现本身而不使用标准API的价值太小了。这是一场虚假的胜利。您将仍然使用相同的运行时代码，只是没有可移植性。|5930090|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|25|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|27|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|28|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|29|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|2A|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|2C|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|2D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|2E|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|2F|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|2G|8|@]|9|@]|A|$]]|$1|V|3|W|5|E|7|2H|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|2I|8|@]|9|@]|A|$]]|$1|Z|3|10|5|E|7|2J|8|@]|9|@]|A|$]]|$1|11|3|12|5|E|7|2K|8|@]|9|@]|A|$]]|$1|13|3|14|5|E|7|2L|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2N|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1D|3|M|5|E|7|2R|8|@]|9|@]|A|$]]|$1|1E|3|O|5|E|7|2S|8|@]|9|@]|A|$]]|$1|1F|3|Q|5|E|7|2T|8|@]|9|@]|A|$]]|$1|1G|3|S|5|E|7|2U|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|E|7|2V|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|E|7|2W|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|E|7|2X|8|@]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|30|8|@]|9|@]|A|$]]|$1|1R|3|M|5|E|7|31|8|@]|9|@]|A|$]]|$1|1S|3|O|5|E|7|32|8|@]|9|@]|A|$]]|$1|1T|3|S|5|E|7|33|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|E|7|34|8|@]|9|@]|A|$]]|$1|1W|3|1X|5|E|7|35|8|@]|9|@]|A|$]]|$1|1Y|3|-4|5|6|7|36|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|6|7|37|8|@]|9|@]|A|$]]|$1|21|3|22|5|6|7|38|8|@]|9|@]|A|$]]|$1|23|3|-4|5|6|7|39|8|@]|9|@]|A|$]]]|24|$]]

Some points:

<ul>
<li>Hibernate is a JPA implementation, one of three. Gavin King, creator of Hibernate, worked incredibly hard on JPA. Removing all JPA usage from an application is moving backwards, not forwards. You only lose portability for no gain.</li>
<li>You can use JPA in Tomcat with or without TomEE.</li>
</ul>

In terms of hating Java EE and wanting to move away from it, it really becomes an impossible task. All these technologies are part of Java EE:

<ul>
<li>Servlets</li>
<li>JSP</li>
<li>JSF</li>
<li>JPA</li>
<li>EJB</li>
<li>CDI / @Inject</li>
<li>JAX-RS</li>
<li>JAX-WS</li>
<li>JMS</li>
<li>Bean Validation</li>
</ul>

To label some of them as JavaEE and some as not JavaEE is a form of denial. They're all created and released as part of JavaEE.

It's near impossible to untangle the mess some of the anti-JavaEE marketing has caused. The truly damaging thing is that it's also near impossible to find a "not JavaEE" application that doesn't use 3 or more JavaEE technologies.

To answer the "heavy" issue and the "too much" issue, in 2010 the Web Profile was created so that smaller runtimes could be created without sacrificing portability. It includes:

<ul>
<li>Servlets</li>
<li>JSP</li>
<li>JSF</li>
<li>JPA</li>
<li>EJB (lite)</li>
<li>CDI / @Inject</li>
<li>Bean Validation</li>
</ul>

There are no distributed transactions and no heavy stuff. If you stack Tomcat, Hibernate and Spring, you'll be including:

<ul>
<li>Servlets</li>
<li>JSP</li>
<li>JPA</li>
<li>@Inject</li>
<li>Bean Validation</li>
</ul>

Those APIs will be there whether or not you chose to use them.

There's just so little value in using the implementations themselves but not using the standard APIs. It's a false victory. You'll still be using the same runtime code, you'll just have no portability.

blocks|key|3253585|text|spring框架或JavaEE现在已经足够接近，可以根据您的喜好进行选择(就个人而言，这是JavaEE，但是您更喜欢宝马还是梅赛德斯？:p)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3253586|也就是说，JPA规范并不是最好的规范，您可以很容易地使用特定的行为链接到hibernate/openjpa/eclipselink，甚至隐藏在javax.persistence包后面。|3253587|这就是说，一旦学到了Java开发，它就会简化很多|3253588|所以我的建议是:使用TomEE，如果你发现一些真正阻塞的东西，重写你不想要的东西，但是我相信你会浪费时间的|3253589|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

well spring framework or JavaEE are today close enough to choose depending on what you prefer (personnally that's Java EE but well do you prefer a BMW or a Mercedes? :p)

That's said JPA specification is not the best one and you easily use specific behavior link to hibernate/openjpa/eclipselink even hidden behind javax.persistence package

That's said it eases a lot the Java development once learnt

So my advice: go with TomEE and if you find something really blocking rewrite what you don't want but IMO you'll loose time

I have an EJB-based library that needs to be modified to be compatible with Tomcat application server (i.e. no JaveEE). I browsed a bit on Hibernate and got rather confused.

Apparently, there's the natural Hibernate branch that uses a .cfg file as base which is Java SE compliant and then there's a JPA-based Hibernate branch that conditionally depends on Java EE. One thing I also find annoying is that some interfaces are apparently not supported - CriteriaQuery for instance. 

So I'd imagine, I would have to go the natural Hibernate branch to achieve the goal of ridding myself of Java EE (which is annoying given the differences). OTOH, there's also TomEE available that's Tomcat compliant and presumably let me keep most of my code unchanged

It's be nice if I can get some feedback. Thanks.

Using Hibernate or TomEE?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个基于EJB的库，需要修改它才能与Tomcat应用服务器兼容(即没有JaveEE)。我在Hibernate上浏览了一下，感到很困惑。显然，有一个自然的Hibernate分支，它使用Java兼容的.cfg文件作为基础，然后还有一个基于JPA的Hibernate分支，它有条件地依赖于Java。还有一件事让我很恼火，那...

问使用Hibernate还是TomEE？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Hibernate还是TomEE？EN