blocks|key|305699|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|305700|“jta数据源”和“资源本地数据源”这两个术语对我来说有点模糊。|blockquote|305701|305702|305703|我猜您实际上指的是jta-datasource和non-jta-datasource元素。简而言之：|offset|length|style|CODE|305704|305705|如果持久性单元的事务类型是JTA，则jta-datasource元素用于声明将用于获取连接的JTA数据源的JNDI名称。这是常见的情况。|unordered-list-item|305706|如果持久性单元的事务类型是资源本地的，则应使用non-jta-data-source来声明非JTA数据源的JNDI名称。|305707|305708|305709|305710|305711|305712|同一数据库可称为jta数据源或资源本地数据源|305713|305714|这是正确的。我在上面没有提到这一点，但一些提供商甚至允许同时声明jta-datasource+和+non-jta-datasource，并使用后者通过非JTA连接进行优化读取(即，这不会与正在进行的JTA事务相关联)。|BOLD|305715|305716|305717|305718|305719|如果提到的是JTA数据源，那么bean/其他类就可以使用JTA。因此，我们使用UserTransaction接口。|305720|305721|第一部分是正确的，最后一部分是不完全正确的。在EJB3.0规范中，使用容器管理的事务界定的13.3.4企业Beans一节：|305722|305723|企业bean的业务方法...不得尝试获取或使用javax.transaction.UserTransaction接口。|305724|305725|305726|和16.12+UserTransaction接口一节|305727|305728|容器不得使UserTransaction接口对不允许使用此接口的企业beans可用。|305729|305730|305731|换句话说，UserTransaction接口对于CMT企业bean是不可用的。|305732|305733|305734|305735|如果数据源是资源本地|305736|，则|305737|无法使用CMT+/+BMT|305738|这里的措辞有点混乱，但我要说这不是严格意义上的正确。在JPA1.0规范中，§5.5节控制事务|305739|305740|应用程序管理的实体管理器可以是JTA实体管理器，也可以是资源本地实体管理器。|305741|305742|..。|305743|JTA实体管理器和资源本地实体管理器都需要在Java+EE+web容器和EJB容器中得到支持。在EJB环境中，通常使用JTA实体管理器。|305744|305745|和第6.2.1.2节事务类型|305746|JTA属性用于指定实体管理器工厂为持久性单元提供的实体管理器必须是|305747|实体管理器还是资源本地实体管理器。此元素的值为JTA或RESOURCE_LOCAL。事务类型的JTA假定将提供JTA数据源-或者由jta-data-source元素指定，或者由容器提供。通常，在Java环境中，RESOURCE_LOCAL的transaction-type假定将提供非JTA数据源。在Java+EE环境中，如果未指定此元素，则缺省值为JTA。|305748|305749|305750|因此，您可以使用应用程序管理的实体管理器，它可以是资源本地的实体管理器(在这种情况下，您必须注入一个EntityManagerFactory才能从它获取EM+)，并且它不会是JTA事务的一部分。参见this+(very+interesting)+discussion。|305751|305752|305753|305754|JTA+|305755|如果作为资源本地数据源提及，则事务不支持。代码可以使用EntityTransaction接口，但不能使用UserTransaction接口|305756|305757|同样，措辞有点令人困惑，但我想说这是正确的。|305758|entityMap|0|LINK|mutability|MUTABLE|url|http://forums.java.net/jive/thread.jspa?messageID=358150&tstart=0^0|0|0|0|0|9|E|O|I|0|0|I|E|0|N|J|0|0|0|0|0|0|0|0|W|E|1D|I|1B|1|0|0|0|0|0|0|0|19|G|0|0|0|1N|N|X|0|0|0|0|Q|0|0|0|16|5|F|0|0|0|0|13|5|F|0|0|0|0|0|A|0|0|2|0|0|D|0|0|1A|0|0|0|12|0|0|0|3|0|0|1W|0|0|0|E|0|0|X|0|0|4Z|N|3|R|E|1T|F|2X|E|3C|G|0|0|0|0|3Q|1E|K|2R|Y|0|0|0|0|0|0|4|0|0|1X|0|0|0|M|0^^$0|@$1|2|3|-4|4|5|6|31|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|32|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|33|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|34|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|35|7|@$H|36|I|37|J|K]|$H|38|I|39|J|K]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|3A|7|@]|8|@]|9|$]]|$1|M|3|N|4|O|6|3B|7|@$H|3C|I|3D|J|K]]|8|@]|9|$]]|$1|P|3|Q|4|O|6|3E|7|@$H|3F|I|3G|J|K]]|8|@]|9|$]]|$1|R|3|-4|4|5|6|3H|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|3I|7|@]|8|@]|9|$]]|$1|T|3|-4|4|C|6|3J|7|@]|8|@]|9|$]]|$1|U|3|-4|4|5|6|3K|7|@]|8|@]|9|$]]|$1|V|3|-4|4|5|6|3L|7|@]|8|@]|9|$]]|$1|W|3|X|4|O|6|3M|7|@]|8|@]|9|$]]|$1|Y|3|-4|4|5|6|3N|7|@]|8|@]|9|$]]|$1|Z|3|10|4|5|6|3O|7|@$H|3P|I|3Q|J|K]|$H|3R|I|3S|J|K]|$H|3T|I|3U|J|11]]|8|@]|9|$]]|$1|12|3|-4|4|5|6|3V|7|@]|8|@]|9|$]]|$1|13|3|-4|4|C|6|3W|7|@]|8|@]|9|$]]|$1|14|3|-4|4|5|6|3X|7|@]|8|@]|9|$]]|$1|15|3|-4|4|5|6|3Y|7|@]|8|@]|9|$]]|$1|16|3|17|4|O|6|3Z|7|@]|8|@]|9|$]]|$1|18|3|-4|4|5|6|40|7|@]|8|@]|9|$]]|$1|19|3|1A|4|5|6|41|7|@$H|42|I|43|J|11]]|8|@]|9|$]]|$1|1B|3|-4|4|5|6|44|7|@]|8|@]|9|$]]|$1|1C|3|1D|4|C|6|45|7|@$H|46|I|47|J|11]|$H|48|I|49|J|K]]|8|@]|9|$]]|$1|1E|3|-4|4|5|6|4A|7|@]|8|@]|9|$]]|$1|1F|3|-4|4|5|6|4B|7|@]|8|@]|9|$]]|$1|1G|3|1H|4|5|6|4C|7|@$H|4D|I|4E|J|11]]|8|@]|9|$]]|$1|1I|3|-4|4|5|6|4F|7|@]|8|@]|9|$]]|$1|1J|3|1K|4|C|6|4G|7|@$H|4H|I|4I|J|11]|$H|4J|I|4K|J|K]]|8|@]|9|$]]|$1|1L|3|-4|4|5|6|4L|7|@]|8|@]|9|$]]|$1|1M|3|-4|4|5|6|4M|7|@]|8|@]|9|$]]|$1|1N|3|1O|4|5|6|4N|7|@$H|4O|I|4P|J|11]|$H|4Q|I|4R|J|K]]|8|@]|9|$]]|$1|1P|3|-4|4|5|6|4S|7|@]|8|@]|9|$]]|$1|1Q|3|-4|4|C|6|4T|7|@]|8|@]|9|$]]|$1|1R|3|-4|4|5|6|4U|7|@]|8|@]|9|$]]|$1|1S|3|1T|4|5|6|4V|7|@$H|4W|I|4X|J|11]]|8|@]|9|$]]|$1|1U|3|1V|4|O|6|4Y|7|@$H|4Z|I|50|J|11]]|8|@]|9|$]]|$1|1W|3|1X|4|5|6|51|7|@$H|52|I|53|J|11]]|8|@]|9|$]]|$1|1Y|3|1Z|4|5|6|54|7|@$H|55|I|56|J|11]]|8|@]|9|$]]|$1|20|3|-4|4|5|6|57|7|@]|8|@]|9|$]]|$1|21|3|22|4|C|6|58|7|@$H|59|I|5A|J|11]]|8|@]|9|$]]|$1|23|3|-4|4|5|6|5B|7|@]|8|@]|9|$]]|$1|24|3|25|4|5|6|5C|7|@$H|5D|I|5E|J|11]]|8|@]|9|$]]|$1|26|3|27|4|5|6|5F|7|@$H|5G|I|5H|J|11]]|8|@]|9|$]]|$1|28|3|-4|4|5|6|5I|7|@]|8|@]|9|$]]|$1|29|3|2A|4|5|6|5J|7|@$H|5K|I|5L|J|11]]|8|@]|9|$]]|$1|2B|3|2C|4|5|6|5M|7|@$H|5N|I|5O|J|11]]|8|@]|9|$]]|$1|2D|3|2E|4|C|6|5P|7|@$H|5Q|I|5R|J|11]|$H|5S|I|5T|J|K]|$H|5U|I|5V|J|K]|$H|5W|I|5X|J|K]|$H|5Y|I|5Z|J|K]|$H|60|I|61|J|K]]|8|@]|9|$]]|$1|2F|3|-4|4|5|6|62|7|@]|8|@]|9|$]]|$1|2G|3|-4|4|5|6|63|7|@]|8|@]|9|$]]|$1|2H|3|2I|4|5|6|64|7|@$H|65|I|66|J|11]|$H|67|I|68|J|K]]|8|@$H|69|I|6A|1|6B]]|9|$]]|$1|2J|3|-4|4|5|6|6C|7|@]|8|@]|9|$]]|$1|2K|3|-4|4|C|6|6D|7|@]|8|@]|9|$]]|$1|2L|3|-4|4|5|6|6E|7|@]|8|@]|9|$]]|$1|2M|3|2N|4|5|6|6F|7|@$H|6G|I|6H|J|11]]|8|@]|9|$]]|$1|2O|3|2P|4|O|6|6I|7|@$H|6J|I|6K|J|11]]|8|@]|9|$]]|$1|2Q|3|-4|4|5|6|6L|7|@]|8|@]|9|$]]|$1|2R|3|2S|4|5|6|6M|7|@$H|6N|I|6O|J|11]]|8|@]|9|$]]|$1|2T|3|-4|4|5|6|6P|7|@]|8|@]|9|$]]]|2U|$2V|$4|2W|2X|2Y|9|$2Z|30]]]]

<blockquote>
 The terms "jta-datasource" and "resouce-local datasource" are a little vague to me.
</blockquote>

I guess you actually refer to the <code>jta-datasource</code> and <code>non-jta-datasource</code> elements. In short:

<ul>
<li>if the transaction type of the persistence unit is JTA, the <code>jta-datasource</code> element is used to declare the JNDI name of the JTA data source that will be used to obtain connections. This is the common case.</li>
<li>if the transaction type of the persistence unit is resource-local, the <code>non-jta-data-source</code> should be used to declare the JNDI name of a non-JTA data source.</li>
</ul>

<blockquote>
 <ul>
 <li>The same database can be referred to as a jta-datasource or as a resource local datasource</li>
 </ul>
</blockquote>

This is correct. And I didn't mention that just above but some providers even allow to declare both a <code>jta-datasource</code> and a <code>non-jta-datasource</code> and use the later for optimized reading through non-JTA connections (i.e. that won't be associated to an ongoing JTA transaction).

<blockquote>
 <ul>
 <li>If mentioned as jta-datasource, then the beans / other classes can use JTA. Hence, UserTransaction interface.</li>
 </ul>
</blockquote>

The first part is correct, the last part not entirely. From the EJB 3.0 spec, section 13.3.4 Enterprise Beans Using Container-Managed Transaction Demarcation: 

<blockquote>
 The enterprise bean’s business methods [...] must not attempt to obtain or use the <code>javax.transaction.UserTransaction</code> interface.
</blockquote>

And section 16.12 UserTransaction Interface:

<blockquote>
 The container must not make the <code>UserTransaction</code> interface available to the enterprise beans that are not allowed to use this interface. 
</blockquote>

In other words, the <code>UserTransaction</code> interface is not available to CMT enterprise beans.

<blockquote>
 <ul>
 <li>Cannot use CMT / BMT if the datasource is resource local </li>
 </ul>
</blockquote>

The wording is a bit confusing here but I'd say that this not strictly correct. From the JPA 1.0 specification, section § 5.5 Controlling Transactions:

<blockquote>
 An application-managed entity manager may be either a JTA entity manager or a resource-local entity manager.
 
 ...
 
 Both JTA entity managers and resource-local entity managers are required to be supported in Java EE web containers and EJB containers. Within an EJB environment, a JTA entity manager is typically used.
</blockquote>

And section 6.2.1.2 transaction-type

<blockquote>
 The <code>transaction-type</code> attribute is used to specify whether the entity managers provided by the entity manager factory for the persistence unit must be JTA entity managers or resource-local entity managers. The value of this element is <code>JTA</code> or <code>RESOURCE_LOCAL</code>. A transaction-type of JTA assumes that a JTA data source will be provided — either as specified by the <code>jta-data-source</code> element or provided by the container. In general, in Java EE environments, a <code>transaction-type</code> of <code>RESOURCE_LOCAL</code> assumes that a non-JTA datasource will be provided. In a Java EE environment, if this element is not specified, the default is JTA. 
</blockquote>

So you CAN use an application managed entity manager which can be a resource-local entity manager (you must inject an <code>EntityManagerFactory</code> to get the EM from it in that case) and it won't be part of a JTA transaction. See <a href="http://forums.java.net/jive/thread.jspa?messageID=358150&amp;tstart=0" rel="noreferrer">this (very interesting) discussion</a>.

<blockquote>
 <ul>
 <li>If mentioned as resource local datasource, transactions are not JTA aware. Code can use EntityTransaction interface but not UserTransaction interface</li>
 </ul>
</blockquote>

Again, the wording is a bit confusing but I'd say that this is correct.

The terms "jta-datasource" and "resource-local datasource" are a little vague to me. I'm putting down what I am understanding ( or assuming ) and I'd like you to say where I'm right / wrong.

<ul>
<li>The same database can be referred to as a jta-datasource or as a resource local datasource</li>
<li>If mentioned as jta-datasource, then the beans / other classes can use JTA. Hence, UserTransaction interface</li>
<li>Cannot use <a href="http://docs.oracle.com/javaee/6/tutorial/doc/bncij.html" rel="noreferrer">CMT</a> / <a href="http://docs.oracle.com/javaee/6/tutorial/doc/bnciy.html" rel="noreferrer">BMT</a> if the datasource is resource local </li>
<li>If mentioned as resource local datasource, transactions are not JTA aware. Code can use EntityTransaction interface but not UserTransaction interface</li>
</ul>

Thanks!

Difference between a "jta-datasource" and a " resource-local " datasource?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

“jta数据源”和“资源本地数据源”这两个术语对我来说有点模糊。我写下了我所理解的(或假设的)，我希望你能说出我是对的/错的。同一数据库可以被称为jta-datasource或资源本地数据源如果被提到为jta-datasource，那么bean/其他类就可以使用JTA。因此，如果数据源是资源本地interfaceCan...

“jta数据源”和“资源本地”数据源之间的区别？-腾讯云开发者社区-腾讯云

问“jta数据源”和“资源本地”数据源之间的区别？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问“jta数据源”和“资源本地”数据源之间的区别？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问“jta数据源”和“资源本地”数据源之间的区别？
EN