[jboss-cvs] JBossAS SVN: r72327 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Apr 17 01:21:15 EDT 2008
Author: xhuang at jboss.com
Date: 2008-04-17 01:21:14 -0400 (Thu, 17 Apr 2008)
New Revision: 72327
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
Log:
update
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2008-04-17 05:20:07 UTC (rev 72326)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2008-04-17 05:21:14 UTC (rev 72327)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_EJBs_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-12-03 00:52+0000\n"
-"PO-Revision-Date: 2008-04-16 10:20+1000\n"
+"PO-Revision-Date: 2008-04-17 11:08+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -5217,13 +5217,13 @@
"how to combat these issues. Deadlocking is formally defined and examined. "
"And, finally, we walk you through how to fine tune your system in terms of "
"entity bean locking."
-msgstr ""
+msgstr "本节介绍 entity bean 锁以及如何在 JBoss 里访问和锁定 entity bean。本节也描述使用 entity bean 时会遇到的问题以及如何解决这些问题。我们也会介绍死锁的正式定义。最后，我们将讨论如何根据 entity bean 锁对系统进行调优。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1173
#, no-c-format
msgid "Why JBoss Needs Locking"
-msgstr ""
+msgstr "为什么 JBoss 需要锁"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1174
@@ -5235,7 +5235,7 @@
"so that data is not corrupted by concurrent reads and writes. Databases "
"traditionally provide this sort of functionality with transactional scopes "
"and table and row locking facilities."
-msgstr ""
+msgstr "锁被用来保护数据的完整性。有时候你需要确保在某个时间只能有一个用户可以更新关键信息。而有时候需要序列化访问敏感信息来避免被并发读和写所破坏。传统的数据库用事务性作用域和表以及行锁定机制来提供这种功能。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1177
@@ -5248,13 +5248,13 @@
"with caching, data integrity is a problem, so some form of application "
"server level locking is needed for entity beans to provide the transaction "
"isolation properties that you are used to with traditional databases."
-msgstr ""
+msgstr "Entity bean 为关系型数据提供了很好的面向对象接口。除此以外，它们可以通过缓存和尽量延迟更新来减少数据库负载以提高性能，最大化数据库效率。但是，缓存对于数据完整性来说是个问题，所以我们需要某种形式的服务器级别的锁来提供和传统数据库一起使用的事务隔离属性。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1183
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Entity Bean Lifecycle"
-msgstr "EJB 3.0 里的 Entity Bean"
+msgstr "Entity Bean 生命周期"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1184
@@ -5264,7 +5264,7 @@
"a given entity bean in memory at one time. This applies for every cache "
"configuration and every type of <literal>commit-option</literal>. The "
"lifecycle for this instance is different for every commit-option though."
-msgstr ""
+msgstr "根据缺省的 JBoss 配置，给定的 Entity Bean 在某一时间内存里只有一个活动的实例。这适用于每个缓存配置和每个 <literal>commit-option</literal> 类型。然而对于每个 commit-option 类型这个实例都有不同的生命周期。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1189
@@ -5272,7 +5272,7 @@
msgid ""
"For commit option <emphasis>A</emphasis>, this instance is cached and used "
"between transactions."
-msgstr ""
+msgstr "对于提交选项 <emphasis>A</emphasis>，这个实例将被缓存并在事务间使用。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1194
@@ -5282,7 +5282,7 @@
"between transactions, but is marked as dirty at the end of a transaction. "
"This means that at the start of a new transaction <literal>ejbLoad</literal> "
"must be called."
-msgstr ""
+msgstr "对于提交选项 <emphasis>B</emphasis>，这个实例将被缓存并在事务间使用，但在事务结束时被标记为脏（dirty）状态。这意味着新事务开始时，<literal>ejbLoad</literal> 必须被调用。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1199
@@ -5291,7 +5291,7 @@
"For commit option <emphasis>C</emphasis>, this instance is marked as dirty, "
"released from the cache, and marked for passivation at the end of a "
"transaction."
-msgstr ""
+msgstr "对于提交选项 <emphasis>C</emphasis>，这个实例将标记为脏（dirty）状态，从缓存里释放并在事务结束时标记为钝化状态。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1204
@@ -5302,6 +5302,8 @@
"cache. Otherwise, this option works in the same way as <emphasis>A</"
"emphasis>."
msgstr ""
+"对于提交选项 <emphasis>D</emphasis>，后台的 refresh 进程将定期地调用缓存里驻留的 bean 的 <literal>ejbLoad</literal>。除此以外，这个选项和 <emphasis>A</"
+"emphasis> 完全相同。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1209
@@ -5312,7 +5314,7 @@
"passivates beans that have been placed in the passivation queue. A bean is "
"pulled out of the passivation queue and reused if the application requests "
"access to a bean of the same primary key."
-msgstr ""
+msgstr "当 bean 被标记为钝化状态时，这个 bean 被置于钝化队列里。每个 entity bean 容器都有一个钝化进程定期地将钝化队列里的 bean 进行钝化。如果应用程序请求对具有相同主键的 bean 进行访问时，这个 bean 将被提出钝化队列并重新使用。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1212
@@ -5322,13 +5324,13 @@
"out of cache entirely. It is not put into the passivation queue and is not "
"reused by an instance pool. Except for the passivation queue, there is no "
"entity bean instance pooling."
-msgstr ""
+msgstr "在发生异常或事务回滚时，entity bean 实例会完全从缓存里抛出。它不会被放入钝化队列也不会被实例池重新使用。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1218
#, no-c-format
msgid "Default Locking Behavior"
-msgstr ""
+msgstr "缺省的锁定行为"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1219
@@ -5339,7 +5341,7 @@
"Because there is only one allowed instance of a given entity bean active at "
"one time, JBoss employs two types of locks to ensure data integrity and to "
"conform to the EJB spec."
-msgstr ""
+msgstr "Entity bean 锁完全和 entity bean 实例分离。锁的逻辑完全独立且由单独的锁对象管理。因为在某一时间给定的 entity bean 只能允许一个实例，JBoss 采用两种类型的锁来确保数据完整性并遵循 EJB 规格。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1224
@@ -5348,7 +5350,7 @@
"<emphasis role=\"bold\">Method Lock</emphasis>: The method lock ensures that "
"only one thread of execution at a time can invoke on a given Entity Bean. "
"This is required by the EJB spec."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Method Lock</emphasis>：方法锁（method lock）确保在某一时刻只能有一个执行线程调用给定的 Entity Bean。这是 EJB 规格所要求的。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1229
@@ -5364,13 +5366,13 @@
"if any method at all is invoked on an entity bean within a transaction, no "
"other transaction can have access to this bean until the holding transaction "
"commits or is rolled back."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Transaction Lock</emphasis>：事务锁（transaction lock）确保在某一时刻只能有一个事务可以访问给定的 Entity Bean。这确保了应用服务器级别的事务的 ACID 属性。既然在缺省情况下，任何 entity bean 在某一时刻只能有一个活动实例，JBoss 必须保护这个实例不被脏读或写。所以，缺省的 entity bean 锁定行为将在事务期间锁定这个 bean，直至事务结束。这意味着如果任何方法在一个事务内被调用，其他任何事务都不能访问这个 bean，直至前者提交或回滚。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1237
#, no-c-format
msgid "Pluggable Interceptors and Locking Policy"
-msgstr ""
+msgstr "可插拔的拦截器和锁定策略"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1238
@@ -5381,7 +5383,7 @@
"descriptor. Let's look at the <literal>container-interceptors</literal> "
"definition for the <emphasis>Standard CMP 2.x EntityBean</emphasis> "
"configuration."
-msgstr ""
+msgstr "<literal>standardjboss.xml</literal> 描述符定义的容器配置定义了基本的 entity bean 生命周期和行为。让我们来看看 <emphasis>Standard CMP 2.x EntityBean</emphasis> 配置的 <literal>container-interceptors</literal> 定义。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1241
@@ -5452,7 +5454,7 @@
"The interceptors shown above define most of the behavior of the entity bean. "
"Below is an explanation of the interceptors that are relevant to this "
"section."
-msgstr ""
+msgstr "上面展示的拦截器定义这个 entity bean 的大部分行为。下面是对和本节相关的拦截器的解释。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1247
@@ -5462,7 +5464,7 @@
"interceptor's role is to schedule any locks that must be acquired before "
"the invocation is allowed to proceed. This interceptor is very lightweight "
"and delegates all locking behavior to a pluggable locking policy."
-msgstr ""
+msgstr "<emphasis role=\"bold\">EntityLockInterceptor</emphasis>：这个拦截器的作用是调度任何必须在调用被允许处理前所需获得的锁。这是一个非常轻量级的拦截器，它把所有的锁定行为都委托给可插拔的锁定策略。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1252
@@ -5472,11 +5474,12 @@
"this interceptor is to find the entity bean within the cache or create a new "
"one. This interceptor also ensures that there is only one active instance of "
"a bean in memory at one time."
-msgstr ""
+msgstr "<emphasis role=\"bold\">EntityInstanceInterceptor</emphasis>：这个拦截器的作用是找到缓存里的或创建新的 entity bean。这个拦截器也要确保在某一时刻某个 bean 在内存里只有一个获得实例存在。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1257
#, no-c-format
+#, fuzzy
msgid ""
"<emphasis role=\"bold\">EntitySynchronizationInterceptor</emphasis>: The "
"role of this interceptor is to synchronize the state of the cache with the "
@@ -5489,7 +5492,7 @@
"emphasis>, <emphasis>B</emphasis> and <emphasis>C</emphasis> of the "
"specification are taken care of here as well as the JBoss specific commit-"
"option <emphasis>D</emphasis>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">EntitySynchronizationInterceptor</emphasis>："
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1265
More information about the jboss-cvs-commits
mailing list