Different access intent policies trigger different physical connections to be allocated.
不同的访问意图策略触发不同的物理连接分配。
The access intent policies discussed in this article apply to Container Managed Persistence (CMP) 2.x beans only.
在本文中讨论的访问意图策略只能在容器管理持久性(CMP) 2 .xbean上应用。
The following sections describe the main components that make up an access intent policy in WebSphere Application Server V5.1.
以下部分将描述WebSphereApplicationServer中访问意图策略的主要组成。
In addition, a WebSphere Studio Application Developer example shows how to set access intent and isolation level in a resource reference.
此外，一个WebSphereStudioApplication Developer示例将展示如何在资源引用中设置访问意图(access intent)和隔离级别(isolation level)。
So, deployment descriptor properties such as isolation levels, access intent, security, method permissions, and so on cannot be set for such problem methods.
所以，就无法为这类问题方法设置隔离级别（isolation level）、访问目的（access intent）、安全性（security）和方法许可（method permission）等这些部署描述符属性。
An access intent policy in WebSphere Application Server includes a few other properties which are only modifiable in the Enterprise edition, where policies can be customized.
WebSphereApplicationServer中的访问意图策略还包含了一些其他属性，这些属性只能在可实现策略定制的Enterprise版本上才能被更改。
Therefore, leave the default access intent policies until you are able to run the load test to determine whether or not there are data integrity, deadlock, or performance problems.
因此，在您有能力运行负载测试来确定是否有数据完整性、死锁或性能问题之前，请保留缺省访问目的策略不变。
However each access intent policy in WebSphere Application Server will choose an appropriate isolation level for supported databases, relieving the developer from this level of detail.
然而WebSphereApplicationServer中不同的访问意图策略将会为所支持的数据库选择一个合适的隔离级，为开发人员减轻了该细节上的不少麻烦。
So, I don't think the Access Intent errors are related to the JNDI problem.
所以，我认为Access Intent错误与JNDI问题没有关系。
So, I don't think the Access Intent errors are related to the JNDI problem.
所以，我认为Access Intent错误与JNDI问题没有关系。
应用推荐