但是，在使用ObjectContainer上的commit方法提交显式事务之前，它不会进行实际更新。
It doesn't do the actual update until the implicit transaction is committed, however, using the commit method on the ObjectContainer.
JMS客户端可以任意的显式控制该事务，比如在同一个消息传递系统中，协同处理从一个队列接收消息和向另一个队列发送消息。
The JMS client can optionally control this transaction explicitly, such as to coordinate receiving a message from one queue with sending a message on another queue in the same messaging system.
因此，流程描述本身将不会显式利用规范中列出的协调和事务服务。
Thus, the process description itself will not explicitly utilize the coordination and transaction services outlined within the specifications.
运行于非受管环境下的应用程序必须显式提交或回滚事务。
An application running in a non-managed environment must explicitly commit or rollback transactions.
完成一个事务的时间（以毫秒计）在单节点上是：常规锁——1877，显式写入锁——1225，而使用“脏接口”的话是181。
The time (microseconds) to perform the transaction for a single node were 1877 with regular locking, 1225 with an explicit write lock, and 181 using a "dirty interface".
Bean管理的事务是由组件使用usertransaction类显式启动和结束的。
Bean-managed transactions are started and ended explicitly by a component using the UserTransaction class.
如果服务和引用不使用binding.ws，则事务意图不需要显式策略集附加。
The transaction intents do not need an explicit policy set attachment if the services and references are not using binding.ws.
如果结果集是在前一个事务中生成的，那么隐式或显式的提交会关闭这个结果集。
If the result set was produced in the previous transaction, an implicit or explicit commit closes the result set.
事务时间包括从应用程序的声明活动开始，直到一条提交或回滚命令隐式或显式地结束事务为止。
The transaction time includes the time at which an application's statement activity begins until a commit or rollback implicitly or explicitly ends the transaction.
必须显式管理事务上下文将增加JPA编程模型的复杂性。
Having to explicitly manage the transactional context would add complexity to the JPA programming model.
即使WLM没有显式地使用服务类(即数据库管理员没有定义任何服务类)，所有用户事务都是在预定义的服务类上下文中执行的。
Even if WLM is not explicitly used (that is, no service classes are defined by the database administrator), all user transactions are executed within the context of the predefined service class.
任何用于与MQ交换消息的WebSphere mq函数都必须在一个事务中显式或隐式地调用。
When you invoke any WebSphere MQ function exchanging a message with MQ, you must be within a transaction, implicit or explicit.
LINQ toSQL同样支持显式设置上下文的事务，所以您可以获取上下文的数据库连接，然后打开它，开启一个事务，并在上下文中设置。
LINQ to SQL also supports explicitly setting the transaction on the context, so you could get the connection from the context, open it, start a transaction, and set it on the context.
然而，您没有注意到，如果没有在事务上下文中使用JPA实体，则需要显式保存到EntityManager以保存任何更改。
However, you failed to note that if you don't use the JPA entity within a transactional context, you need to do an explicit save to the EntityManager to persist any changes.
尽管缓存事务内部依赖于缓存锁，但Hibernate不会显式调用任何的缓存锁函数。
Hibernate doesn't explicitly call any cache lock function although cache transactions internally rely on cache locks.
虽然图2中的2100万个事务处理似乎太多了，但要注意，这是自dpar启动以来或自该统计数字被显式重置以来的总数。
While the 21 million transactions in figure 2 looks like a lot, remember that this is the total since the DPAR was started or since this statistic was explicitly reset.
因此，当使用(或可能使用)客户机模式时，建议使用事务处理会话和代码显式commit和rollback方法调用。
It is therefore recommended to use transacted sessions and code explicit commit and rollback method calls when client mode is (or might be) used.
SQL分布式事务涉及的会话并不获取可以传递给另一个会话的事务对象，从而也不能将其显式登记在分布式事务中。
The sessions involved in Transact-SQL distributed transactions do not get a transaction object they can pass to another session for it to explicitly enlist in the distributed transaction.
当我们怀疑活动对象参与了回滚事务，我们必须显式刷新我们的活动对象。
We will have to explicitly refresh our live objects when we suspect they may have participated in a rollback transaction.
没有事务名称或保存点名称的ROLLBACK语句总是将语句回退到最外层的BEGINTRANSACTION(显式或隐式)语句，并且取消整个事务。
ROLLBACK statement without a transaction or savepoint name always rolls back statements to the outermost BEGIN transaction (explicit or implicit) statement, and cancels the entire transaction.
没有事务名称或保存点名称的ROLLBACK语句总是将语句回退到最外层的BEGINTRANSACTION(显式或隐式)语句，并且取消整个事务。
ROLLBACK statement without a transaction or savepoint name always rolls back statements to the outermost BEGIN transaction (explicit or implicit) statement, and cancels the entire transaction.
应用推荐