By changing the isolation level, the J2EE developer or deployer can balance data integrity against performance constraints to performance tune the application.
通过修改隔离级别，J2EE开发人员或部署人员可以在性能的约束下平衡数据完整性，从而对应用程序进行调整。
Three-tier architectures and popular frameworks make this isolation more difficult, because the developer might never see the SQL generated by the framework.
层架构和流行的框架让隔离过程更加困难，因为开发人员可能永远不能看到框架生成的SQL 语句。
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)。
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中不同的访问意图策略将会为所支持的数据库选择一个合适的隔离级，为开发人员减轻了该细节上的不少麻烦。
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中不同的访问意图策略将会为所支持的数据库选择一个合适的隔离级，为开发人员减轻了该细节上的不少麻烦。
应用推荐