[jboss-cvs] JBossAS SVN: r73670 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun May 25 08:33:17 EDT 2008
Author: xhuang at jboss.com
Date: 2008-05-25 08:33:17 -0400 (Sun, 25 May 2008)
New Revision: 73670
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po
Log:
update
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po 2008-05-25 10:32:08 UTC (rev 73669)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_HTTP.po 2008-05-25 12:33:17 UTC (rev 73670)
@@ -9,13 +9,14 @@
"Project-Id-Version: Clustering_Guide_HTTP\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-05-19 03:42+0000\n"
-"PO-Revision-Date: 2008-05-15 11:35+1000\n"
+"PO-Revision-Date: 2008-05-26 08:32+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: <en at li.org>\n"
+"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.4\n"
+"X-Generator: KAider 0.1\n"
+"Plural-Forms: nplurals=2; plural=n != 1;\n"
#. Tag: title
#: Clustering_Guide_HTTP.xml:5
@@ -204,8 +205,7 @@
msgid ""
"Next, create a new file named <literal>APACHE_HOME/conf/mod-jk.conf</"
"literal>:"
-msgstr ""
-"然后，建立一个叫 <literal>APACHE_HOME/conf/mod-jk.conf</literal> 的文件。"
+msgstr "然后，建立一个叫 <literal>APACHE_HOME/conf/mod-jk.conf</literal> 的文件。"
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:51
@@ -586,8 +586,7 @@
msgid ""
"A non-loadbalanced setup with a single node requires a <literal>worker."
"list=node1</literal> entry."
-msgstr ""
-"单节点的非负载平衡的设立需要设置 <literal>worker.list=node1</literal> 条目。"
+msgstr "单节点的非负载平衡的设立需要设置 <literal>worker.list=node1</literal> 条目。"
#. Tag: title
#: Clustering_Guide_HTTP.xml:118
@@ -907,7 +906,7 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:178
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">CacheMode</emphasis> controls how the cache is "
"replicated. The valid values are <literal>REPL_SYNC</literal> and "
@@ -923,11 +922,15 @@
"is much slower."
msgstr ""
"<emphasis role=\"bold\">CacheMode</emphasis> 控制缓存的复制模式。其有效值是 "
-"<literal>REPL_SYNC</literal> 和 <literal>REPL_ASYNC</literal>。"
+"<literal>REPL_SYNC</literal> 和 <literal>REPL_ASYNC</literal>"
+"。不管使用哪个模式，客户端请求线程都会用当前会话内容更新本地缓存，然后向群集里的其他成员里的缓存发送消息，通知它们进行相同的修改。如果使用 "
+"REPL_ASYNC（缺省模式），只要往网络发送了更新信息，请求线程就马上返回。而如果使用 "
+"REPL_SYNC，在获得所有群集成员的回复消息、通知它更新已成功完成前，请求线程将一直阻塞。使用同步复制确保了在 web "
+"请求完成前，在整个群集里应用了所有的修改。然而，同步复制较为缓慢。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:182
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ClusterName</emphasis> specifies the name of the "
"cluster that the cache works within. The default cluster name is the the "
@@ -936,8 +939,7 @@
msgstr ""
"<emphasis role=\"bold\">ClusterName</emphasis> 指定了缓存所服务的群集的名字。"
"缺省的群集名是 \"Tomcat-\" 后面跟着当前的 JBoss 分区名。所有节点都应该使用相"
-"同的群集名。虽然会话复制能够和 JBoss 的其他群集服务共享同一通道（多点传送地址"
-"和端口），复制还是应该有自己的群集名。"
+"同的群集名。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:187
@@ -979,15 +981,15 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:199
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">SyncReplTimeout</emphasis> sets the maximum number "
"of milliseconds to wait for a response from all nodes in the cluster when a "
"synchronous replication message is sent out. The default value is 20000; "
"should be a few seconds longer than LockAcquisitionTimeout."
msgstr ""
-"<emphasis role=\"bold\">LockAcquisitionTimeout</emphasis> 设置以毫秒为单位的"
-"等待所锁定捕获（lock acquisition）的最长时间。它的缺省值是 15000。"
+"<emphasis role=\"bold\">SyncReplTimeout</emphasis> 设置以毫秒为单位的"
+"等待所有节点同步复制返回前等待的最长时间。它的缺省值是 20000；它应该比 LockAcquisitionTimeout 的值更长。"
#. Tag: title
#: Clustering_Guide_HTTP.xml:207
@@ -1071,18 +1073,18 @@
#. Tag: para
#: Clustering_Guide_HTTP.xml:214
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>replication-trigger</literal> element determines what triggers "
"a session replication (i.e. when is a session is considered <literal>dirty</"
"literal> and in need of replication). It has 4 options:"
msgstr ""
"<literal>replication-trigger</literal> 元素决定用什么触发状态复制（或什么时候"
-"会话被认为是 dirty 的）。它有四个选项："
+"会话被认为是 <literal>dirty</literal> 且需要进行复制）。它有四个选项："
#. Tag: para
#: Clustering_Guide_HTTP.xml:218
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">SET</emphasis>: With this policy, the session is "
"considered dirty only when an attribute is set in the session (i.e., "
@@ -1094,13 +1096,13 @@
"that object may not be replicated."
msgstr ""
"<emphasis role=\"bold\">SET</emphasis>：在这个选项下，只有在会话里设置了属"
-"性，会话才被认为是 dirty。如果你的应用程序总把改变的写回到会话里，从性能角度"
-"来讲这个选项可能是最优化的。如果只从会话里取出一个对象而不把它写回到会话里，"
-"对这个对象的修改将不会被复制。"
+"性（例如，调用了 HttpSession.setAttribute() 方法），会话才被认为是 "
+"dirty。如果你的应用程序总把改变的值写回到会话里，从性能角度"
+"来讲这个选项可能是最优化的。如果只从会话里取出一个对象而不把它写回到会话里，会话管理者将不会知道这个属性是 dirty 的，对这个对象的修改将不会被复制。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:221
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">SET_AND_GET</emphasis>: With this policy, any "
"attribute that is get or set will be marked as dirty. If an object is "
@@ -1112,7 +1114,7 @@
msgstr ""
"<emphasis role=\"bold\">SET_AND_GET</emphasis>：如使用这个策略，所有 get 或 "
"set 的属性都会被标记为 ditry。如果从会话里取出一个对象并修改它，但没有写回到"
-"这个会话里，这些修改也将被复制。这个选项对性能有比较大的影响。"
+"这个会话里，这些修改也将被复制。这个选项的缺点是对性能有比较大的影响，甚至即使从会话里读取不变的对象（如字符串、数字）时，它也会将其标记为需要复制。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:224
@@ -1129,10 +1131,15 @@
"setting avoids the downside of SET while reducing the performance impact of "
"SET_AND_GET. It is the default setting."
msgstr ""
+"<emphasis role=\"bold\">SET_AND_NON_PRIMITIVE_GET</emphasis>：这个策略和 "
+"SET_AND_GET 策略相似，除了返回原始类型值的 get 操作不会把属性标记为 "
+"dirty。原始的系统类型（如字符串、整型、长整型等）是不可变的，所以没有理由仅仅对其进行了读取而把这样的类型标记为 dirty。如果 get "
+"操作返回的时非原始类型的对象，会话管理者并没有简单的方法来判断这个对象是否可变，所以它将假定其为可变的且将其标记为 dirty。这个设置避免了 SET "
+"策略的缺点，同时降低了 SET_AND_GET 策略对性能的影响。它时缺省的设置。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:227
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ACCESS</emphasis>: This option causes the session to "
"be marked as dirty whenever it is accessed. Since a the session is accessed "
@@ -1152,10 +1159,11 @@
msgstr ""
"<emphasis role=\"bold\">ACCESS</emphasis>：这个选项表示：只要会话被访问，就把"
"会话标记为 ditry。因为在每个 HTTP 请求的过程中，会话都会被访问，所以会话每次"
-"都会被复制。会话实例里的时间戳也会相应地更新。由于复制并没有包括时间戳，其他"
-"群集节点的时间戳可能不会被更新。如果 HTTP 请求没有取出或修改任何会话属性，其"
+"都会被复制。ACCESS 的目的时确保最后访问会话的时间戳在群集里保持同步。既然使用其他的 replication-trigger "
+"选项时，由于不进行复制，其他群集节点里的时间戳可能不会被更新，那么如果 HTTP 请求没有取出或修改任何会话属性，其"
"他节点的会话就可能会先于活动节点过期。当设置了这个选项，会话的时间戳将在所有"
-"群集节点中同步。注意采用这个选项对性能影响很大，需要小心行事。"
+"群集节点中同步。注意采用这个选项对性能影响很大，需要小心行事。在使用其他 replication-trigger 选项时，如果会话已经进行了其有效期的 "
+"80% 而未必复制，为安全起见，其时间戳无论如何都会被复制。所以，只有在上述安全保证未被充分考虑的特殊情况下，ACCESS 才被使用。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:230
@@ -1236,13 +1244,13 @@
#. Tag: title
#: Clustering_Guide_HTTP.xml:259
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Using FIELD level replication"
msgstr "使用字段级（FIELD level）的复制"
#. Tag: para
#: Clustering_Guide_HTTP.xml:260
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"FIELD-level replication only replicates modified data fields inside objects "
"stored in the session. Its use could potentially drastically reduce the data "
@@ -1253,8 +1261,7 @@
msgstr ""
"字段级复制只复制存储在会话里的对象内部的被修改的数据字段。它能够极大地减少群"
"集节点之间的数据通信，也因此提高了整个群集系统的性能。为了使用字段级复制，你"
-"首先得用 Java 类来指出哪个字段要被复制。它是通过在 JavaDocs 嵌入的 JDK 1.4 风"
-"格的注解（annotations）来完成的。"
+"首先得准备好 Java 类（也就是 bytecode enhance），允许会话缓存检测什么时候缓存对象里的字段已经被修改并需要进行复制。"
#. Tag: para
#: Clustering_Guide_HTTP.xml:262
@@ -1262,7 +1269,7 @@
msgid ""
"The first step in doing this is to identify the classes that need to be "
"prepared. This is done via annotations. For example:"
-msgstr ""
+msgstr "要实现这一点，第一步时确认需要准备的类。这通过注解来完成。例如："
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:266
@@ -1291,6 +1298,8 @@
"annotate an interface with InstanceofAopMarker and all of its implementing "
"classes will be annotated. For example:"
msgstr ""
+"如果你用 InstanceAopMarker 注解了一个类，那么它所有的子类都将自动进行注解。相似地，你可以用 InstanceofAopMarker "
+"注解一个接口，则所有实现它的类也都会被注解。例如："
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:271
@@ -1332,6 +1341,9 @@
"need to build their projects using JDK 1.4. In this case, annotating classes "
"can be done via JDK 1.4 style annotations embedded in JavaDocs. For example:"
msgstr ""
+"你不需要注解 <literal>Student</literal>。因为它是 <literal>Person</literal> "
+"的子类，它将被自动注解。Jboss AS 4.2 的运行需要 JDK 5，但某些用户可能仍需要用 JDK 1.4 "
+"构建应用程序。在这种情况下，注解的类可以通过嵌入在 JavaDocs 里的 JDK 1.4 风格的注解来完成。例如："
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:278
@@ -1359,7 +1371,7 @@
#: Clustering_Guide_HTTP.xml:281
#, no-c-format
msgid "The anologue for <literal>@InstanceAopMarker</literal> is:"
-msgstr ""
+msgstr "<literal>@InstanceAopMarker</literal> 的语法是："
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:283
@@ -1664,7 +1676,7 @@
#. Tag: programlisting
#: Clustering_Guide_HTTP.xml:345
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<Valve className=\"org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn\" /"
">"
@@ -2044,6 +2056,8 @@
"<![CDATA[<depends>jboss.ha:service=HASingletonDeployer,type=Barrier</"
"depends>]]>"
msgstr ""
+"<![CDATA[<depends>jboss.ha:service=HASingletonDeployer,type=Barrier</"
+"depends>]]>"
#. Tag: para
#: Clustering_Guide_HTTP.xml:433
@@ -2183,3 +2197,4 @@
"would remain the master – there's nothing magic about A that would cause it "
"to become the master again just because it was before."
msgstr ""
+
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po 2008-05-25 10:32:08 UTC (rev 73669)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po 2008-05-25 12:33:17 UTC (rev 73670)
@@ -9,14 +9,14 @@
"Project-Id-Version: The_CMP_Engine\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-05-19 03:42+0000\n"
-"PO-Revision-Date: 2008-05-19 13:41+1000\n"
+"PO-Revision-Date: 2008-05-26 08:00+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: <en at li.org>\n"
+"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.4\n"
-"Plural-Forms: nplurals=2; plural=n != 1;\n"
+"Plural-Forms: nplurals=2; plural=n != 1;X-Generator: KAider 0.1\n"
+"X-Generator: KAider 0.1\n"
#. Tag: title
#: The_CMP_Engine.xml:6
@@ -1182,8 +1182,7 @@
msgid ""
"string fields which are shorter than the declared length will have their "
"length increased to the declared length. (not supported by all databases)"
-msgstr ""
-"字符串字段如果比所声明的要短，则扩大至所声明的长度。（不是所有数据库都支持）"
+msgstr "字符串字段如果比所声明的要短，则扩大至所声明的长度。（不是所有数据库都支持）"
#. Tag: para
#: The_CMP_Engine.xml:227
@@ -2942,8 +2941,7 @@
msgid ""
"The basic template of the relationship mapping declaration for "
"<literal>Organization-Gangster</literal> relationship follows:"
-msgstr ""
-"<literal>Organization-Gangster</literal> 关系映射声明遵循下面的基本模板："
+msgstr "<literal>Organization-Gangster</literal> 关系映射声明遵循下面的基本模板："
#. Tag: programlisting
#: The_CMP_Engine.xml:639
@@ -3912,7 +3910,7 @@
#. Tag: para
#: The_CMP_Engine.xml:883
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The EJB-QL query can be overridden in the <literal>jbosscmp-jdbc.xml</"
"literal> file. The finder or select is still required to have an EJB-QL "
@@ -5155,8 +5153,7 @@
msgid ""
"Then as each of the eight gangster in the sample database is accessed, JBoss "
"will execute the following eight queries:"
-msgstr ""
-"然后当示例数据库中的 8 个 gangster 都被访问时，JBoss 将执行下面的 8 个查询："
+msgstr "然后当示例数据库中的 8 个 gangster 都被访问时，JBoss 将执行下面的 8 个查询："
#. Tag: programlisting
#: The_CMP_Engine.xml:1129
@@ -6277,8 +6274,7 @@
#, no-c-format
msgid ""
"Note, if we remove <literal>left-join</literal> metadata we will have only"
-msgstr ""
-"请注意，如果我们删除了 <literal>left-join</literal> 元数据，我们将只有："
+msgstr "请注意，如果我们删除了 <literal>left-join</literal> 元数据，我们将只有："
#. Tag: programlisting
#: The_CMP_Engine.xml:1648
@@ -6311,18 +6307,21 @@
"cachemax</literal> element of the entity. This strategy is also used when "
"faulting in data not loaded in the <literal>on-find</literal> strategy."
msgstr ""
+"<literal>on-load</literal> 策略在某个 entity 被加载时为几个 entity 加载其他数据块，按顺序从被请求的 "
+"entity 开始，直到所选择的其他几个 entity。当查询被执行时，JBoss 把找到的 entity 的顺序保存在列表缓存里。之后，当其中一个 "
+"entity 被加载时，JBoss 使用这个列表来决定加载的 entity 块。该 entity 的 <literal>list-cachemax<"
+"/literal> 元素指定存储在缓存里的列表的个数。这个策略也用于 <literal>on-find</literal> 策略不加载的有问题的数据。"
#. Tag: para
#: The_CMP_Engine.xml:1658
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"As with the <literal>on-find</literal> strategy, <literal>on-load</literal> "
"is declared in the <literal>read-ahead</literal> element. The <literal>on-"
"load</literal> configuration for this example is shown below."
msgstr ""
-"JAXP JAR是<literal>crimson.jar</literal>还是 <literal>xerces.jar</literal>依"
-"赖于<literal>Main</literal>入口的<literal>-j</literal>选项。缺省是"
-"<literal>crimson.jar</literal>。"
+"和 <literal>on-find</literal> 策略一样，<literal>on-load</literal> 也在 <literal>"
+"read-ahead</literal> 元素里声明。下面是一个 <literal>on-load</literal> 配置的例子。"
#. Tag: programlisting
#: The_CMP_Engine.xml:1661
@@ -6383,7 +6382,7 @@
#, no-c-format
msgid ""
"With this strategy, the query for the finder method in remains unchanged."
-msgstr ""
+msgstr "根据这个策略，使用 finder 方法的查询仍维持不变。"
#. Tag: programlisting
#: The_CMP_Engine.xml:1665
@@ -6393,6 +6392,9 @@
" FROM gangster t0_g\n"
" ORDER BY t0_g.id ASC"
msgstr ""
+"SELECT t0_g.id\n"
+" FROM gangster t0_g\n"
+" ORDER BY t0_g.id ASC"
#. Tag: para
#: The_CMP_Engine.xml:1666
@@ -6404,6 +6406,8 @@
"<literal>nickName</literal> and <literal>badness</literal> fields for the "
"entities:"
msgstr ""
+"然而，在我们迭代结果集时数据的加载会有所不同。对于页面大小为 4 的结果集，JBoss 将只需要执行下面的两个查询来加载 <literal>name<"
+"/literal>、<literal>nickName</literal> 和 <literal>badness</literal> 字段。"
#. Tag: programlisting
#: The_CMP_Engine.xml:1669
@@ -6427,19 +6431,19 @@
#: The_CMP_Engine.xml:1670
#, no-c-format
msgid "The following table shows the execution of these queries:"
-msgstr ""
+msgstr "下面的表展示了这些查询的执行情况："
#. Tag: title
#: The_CMP_Engine.xml:1674
#, no-c-format
msgid "on-load Optimized Query Execution"
-msgstr ""
+msgstr "执行用 on-load 策略优化的查询"
#. Tag: title
#: The_CMP_Engine.xml:1865
#, no-c-format
msgid "none"
-msgstr ""
+msgstr "none 策略"
#. Tag: para
#: The_CMP_Engine.xml:1866
@@ -6454,6 +6458,10 @@
"literal> element or <literal>eager-load-group</literal>, it is ignored. The "
"none strategy is declared the following example."
msgstr ""
+"<literal>none</literal> 策略实际上是一个反策略（anti-strategy）。这个策略使系统用回缺省的 lazy-load "
+"代码，尤其是不预读任何数据或记住找到的 entity 的顺序。其结果就时本章开始时显示的查询执行结果。none 策略用 read-ahead "
+"元素进行声明。如果 <literal>read-ahead</literal> 元素包含一个 <literal>page-size</literal> "
+"元素或 <literal>eager-load-group</literal>，它将被忽略。下面是一个声明 none 策略的例子。"
#. Tag: programlisting
#: The_CMP_Engine.xml:1869
@@ -6507,9 +6515,9 @@
#. Tag: title
#: The_CMP_Engine.xml:1877
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Loading Process"
-msgstr "负载平衡策略"
+msgstr "加载过程"
#. Tag: para
#: The_CMP_Engine.xml:1878
@@ -6521,12 +6529,14 @@
"when an entity is loaded. The following section describes the commit options "
"and the loading processes."
msgstr ""
+"在前一节里，有几个步骤使用了短语 \"when the entity is loaded\"。这种模糊是故意留下的，因为为这个 entity "
+"指定的提交选项和事务的当前状态决定了 entity 的加载时机。下面的内容将描述提交选项和加载过程。"
#. Tag: title
#: The_CMP_Engine.xml:1882
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Commit Options"
-msgstr "限制"
+msgstr "提交选项"
#. Tag: para
#: The_CMP_Engine.xml:1883
@@ -6539,6 +6549,9 @@
"JavaBeans Specification, but the last one is specific to JBoss. A detailed "
"description of each commit option follows:"
msgstr ""
+"加载过程的中心是提交选项（commit option），它控制 entity 的数据的过期时间。JBoss 支持 4 种提交选项 <literal>A<"
+"/literal>、<literal>B</literal>、<literal>C</literal> 和 <literal>D</literal>"
+"。EJB 规格里描述了前面 3 种，最后一个是 JBoss 所特有的。下面是对每个提交选项的详细描述："
#. Tag: para
#: The_CMP_Engine.xml:1888
@@ -6552,6 +6565,9 @@
"direct JDBC (even within JBoss) will result in an inconsistent database "
"state."
msgstr ""
+"<emphasis role=\"bold\">A</emphasis>：JBoss 假设它是数据库的唯一用户；因此，JBoss 可以缓存事务间的 "
+"entity 的当前值，这能够提升性能。利用这种假设，JBoss 管理的数据都不能在 JBoss 之外进行修改。例如，在另外一个程序里修改数据或直接使用 "
+"JDBC（即使在 JBoss 内部）都将导致不一致的数据库状态。"
#. Tag: para
#: The_CMP_Engine.xml:1893
@@ -6562,14 +6578,17 @@
"between transactions. This context information is used for optimizing "
"loading of the entity. This is the default commit option."
msgstr ""
+"<emphasis role=\"bold\">B</emphasis>： JBoss 假设有多个用户访问数据库，但也保留事务间的 entity "
+"的上下文信息。这些信息被用来优化 entity 的加载。它是缺省的提交选项。"
#. Tag: para
#: The_CMP_Engine.xml:1898
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">C</emphasis>: JBoss discards all entity context "
"information at the end of the transaction."
-msgstr "<emphasis role=\"bold\">name</emphasis>：这个元素包含操作的名字。"
+msgstr ""
+"<emphasis role=\"bold\">C</emphasis>: 在事务结束时，JBoss 丢弃所有 entity 的上下文的信息。"
#. Tag: para
#: The_CMP_Engine.xml:1903
@@ -6579,6 +6598,8 @@
"option. This option is similar to commit option <literal>A</literal>, except "
"that the data only remains valid for a specified amount of time."
msgstr ""
+"<emphasis role=\"bold\">D</emphasis>：这是 JBoss 专有的提交选项。这个选项和 <literal>A<"
+"/literal> 相似，但其数据只在指定的时间内保持有效。"
#. Tag: para
#: The_CMP_Engine.xml:1908
@@ -6589,12 +6610,15 @@
"The following example changes the commit option to <literal>A</literal> for "
"all entity beans in the application:"
msgstr ""
+"我们在 <literal>jboss.xml</literal> 文件里对提交选项进行声明。对于这个文件的详细描述，请参考 <xref "
+"linkend=\"EJBs_on_JBoss\"/>。下面的例子把应用程序里的所有 entity bean 的提交选项修改为 <literal>A<"
+"/literal>："
#. Tag: title
#: The_CMP_Engine.xml:1911
#, no-c-format
msgid "The jboss.xml Commit Option Declaration"
-msgstr ""
+msgstr "在 jboss.xml 里声明提交选项"
#. Tag: programlisting
#: The_CMP_Engine.xml:1912
@@ -6624,7 +6648,7 @@
#: The_CMP_Engine.xml:1917
#, no-c-format
msgid "Eager-loading Process"
-msgstr ""
+msgstr "Eager 加载过程"
#. Tag: para
#: The_CMP_Engine.xml:1918
@@ -6639,6 +6663,11 @@
"the <literal>basic</literal> load group is set as the default <literal>eager-"
"load-group</literal> for the gangster entity bean:"
msgstr ""
+"当加载 entity 时，JBoss 必须决定需要加载的字段。在缺省情况下，JBoss 将使用选择这个 entity 的最后一个查询的 <literal>"
+"eager-load-group</literal>。如果没有查询选择这个 entity，或者最后的查询使用了 <literal>none<"
+"/literal> 预读策略，JBoss 将使用该 entity 的缺省的 <literal>eager-load-group</literal>"
+"。在下面的例子里，<literal>basic</literal> 加载组被设置为 gangster entity bean 的缺省 <literal>"
+"eager-load-group</literal>。"
#. Tag: programlisting
#: The_CMP_Engine.xml:1921
@@ -6691,7 +6720,7 @@
"The eager loading process is initiated the first time a method is called on "
"an entity in a transaction. A detailed description of the load process "
"follows:"
-msgstr ""
+msgstr "当事务里的 entity 的某个方法第一次被调用时，Eager 加载过程被初始化。下面是对这个加载过程的详细描述："
#. Tag: para
#: The_CMP_Engine.xml:1927
@@ -6702,6 +6731,8 @@
"commit option <literal>A</literal>, or when using commit option <literal>D</"
"literal>, and the data has not timed out."
msgstr ""
+"如果 entity 的上下文仍然有效，则无需进行加载，因此加载过程就结束了。在使用提交选项 <literal>A</literal> 或 <"
+"literal>D</literal> 且数据未超时时，entity 的上下文将保持有效。"
#. Tag: para
#: The_CMP_Engine.xml:1932
@@ -6709,7 +6740,7 @@
msgid ""
"Any residual data in the entity context is flushed. This assures that old "
"data does not bleed into the new load."
-msgstr ""
+msgstr "Entity 上下文里的任何驻留数据都将被清除。这确保了旧的数据不会混在新的加载过程里。"
#. Tag: para
#: The_CMP_Engine.xml:1937
@@ -6718,14 +6749,14 @@
"The primary key value is injected back into the primary key fields. The "
"primary key object is actually independent of the fields and needs to be "
"reloaded after the flush in step 2."
-msgstr ""
+msgstr "主键值被注入回主键字段里。主键对象实际上独立于这些字段，它需要在第二步的清除后重新进行加载。"
#. Tag: para
#: The_CMP_Engine.xml:1942 The_CMP_Engine.xml:1975
#, no-c-format
msgid ""
"All data in the preload cache for this entity is loaded into the fields."
-msgstr ""
+msgstr "预加载缓存里这个 entity 的任何数据都将加载到这些字段里。"
#. Tag: para
#: The_CMP_Engine.xml:1947
@@ -6738,6 +6769,9 @@
"ahead strategy. If all of the fields have already been loaded, the load "
"process skips to step 7."
msgstr ""
+"JBoss 决定仍需要被加载的其他字段。通常这些字段由 entity 的 eager-load group 所决定，但如果该 entity "
+"通过查询或带有 <literal>on-find</literal> 或 <literal>on-load</literal> 预读策略的 CMR "
+"字段进行定位时，它们可以被覆盖。如果所有这些字段都已经加载，那么加载过程将跳至步骤 7。"
#. Tag: para
#: The_CMP_Engine.xml:1952
@@ -6749,18 +6783,21 @@
"current entity is stored in the context and the data for the other entities "
"is stored in the preload cache."
msgstr ""
+"我们执行一个查询来选定所需的列。如果这个 entity 使用了 <literal>on-load</literal> 策略，那么如 <xref "
+"linkend=\"Read_ahead-on_load\"/> 所提及的，一页数据将被加载。当前 entity 的数据存储在上下文里，而其他 "
+"entity 的数据保存在预加载缓存中。"
#. Tag: para
#: The_CMP_Engine.xml:1957
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The <literal>ejbLoad</literal> method of the entity is called."
-msgstr "<literal>table</literal>：被连接表的名称。"
+msgstr "调用该 entity 的 <literal>ejbLoad</literal> 方法。"
#. Tag: title
#: The_CMP_Engine.xml:1965
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Lazy loading Process"
-msgstr "负载平衡策略"
+msgstr "Lazy 加载过程"
#. Tag: para
#: The_CMP_Engine.xml:1966
@@ -6773,6 +6810,9 @@
"removes any field that is already loaded. An example configuration is shown "
"below."
msgstr ""
+"Lazy 加载时 eager 加载的另外一半。如果某个字段没有进行 eager 加载，那么它必须进行 lazy 加载。当访问某个 bean "
+"的未加载字段时，JBoss 加载这个字段以及它所属的任何 <literal>lazy-load-group</literal> 里的字段。JBoss "
+"执行一系列 join 操作，然后删除任何已经加载的字段。下面是一个配置示例。"
#. Tag: programlisting
#: The_CMP_Engine.xml:1969
@@ -6848,6 +6888,11 @@
"literal>, <literal>contactInfo</literal>, and <literal>hangout</literal> are "
"loaded. A detailed description of the lazy loading process follows:"
msgstr ""
+"当 bean 提供者调用 <literal>getName()</literal> 时，JBoss 加载 <literal>name</literal>"
+"、 <literal>nickName</literal> 和 <literal>badness</literal>，假定它们还没有被加载。当 bean "
+"提供者调用 <literal>getNickName()</literal> 时，<literal>name</literal>、<literal>"
+"nickName</literal>、 <literal>badness</literal>、<literal>contactInfo</literal>"
+" 和 <literal>hangout</literal> 将被加载。下面是对 lazy 加载过程的详细描述："
#. Tag: para
#: The_CMP_Engine.xml:1980
@@ -6855,7 +6900,7 @@
msgid ""
"If the field value was loaded by the preload cache the lazy load process is "
"finished."
-msgstr ""
+msgstr "如果字段值通过预加载缓存加载，那么 lazy 加载过程就结束了。"
#. Tag: para
#: The_CMP_Engine.xml:1985
@@ -6863,7 +6908,7 @@
msgid ""
"JBoss finds all of the lazy load groups that contain this field, performs a "
"set join on the groups, and removes any field that has already been loaded."
-msgstr ""
+msgstr "JBoss 找到所有包含这个字段的 lazy 加载组，执行一系列 join 操作，并删除已经加载的任何字段。"
#. Tag: para
#: The_CMP_Engine.xml:1990
@@ -6874,12 +6919,14 @@
"is stored in the context and the data for the other entities is stored in "
"the preload cache."
msgstr ""
+"我们执行一个查询来选择所需的列。和基本的加载过程一样，JBoss 可以加载一个 entity 块。当前 entity 的数据保存在上下文里，而其他 "
+"entity 的数据则存储在预加载缓存里。"
#. Tag: title
#: The_CMP_Engine.xml:1996
#, no-c-format
msgid "Relationships"
-msgstr ""
+msgstr "关系"
#. Tag: para
#: The_CMP_Engine.xml:1997
@@ -6892,6 +6939,9 @@
"field values of the related entity can be preloaded using <literal>on-find</"
"literal>."
msgstr ""
+"关系是 lazy 加载里的一个特例，因为 CMR 字段既是字段也是查询。作为字段，它可以进行 <literal>on-load</literal> "
+"块加载，这表示当前搜索的 entity 的值和下几个 entity 的 CMR 字段的值将被加载。而作为查询，相关的 entity 的字段值可以通过 <"
+"literal>on-find</literal> 进行预加载。"
#. Tag: para
#: The_CMP_Engine.xml:2000
@@ -6901,12 +6951,13 @@
"scenario. In this example, an HTML table is generated containing each "
"gangster and their hangout. The example code follows:"
msgstr ""
+"熟悉加载过程最简单的方法是通过用例。在这个例子里，包含每个 gangster 及其 hangout 的 HTML 表将被生成。下面时示例代码："
#. Tag: title
#: The_CMP_Engine.xml:2003
#, no-c-format
msgid "Relationship Lazy Loading Example Code"
-msgstr ""
+msgstr "关系的 Lazy 加载的示例代码"
#. Tag: programlisting
#: The_CMP_Engine.xml:2004
@@ -6979,12 +7030,15 @@
"find</literal> section. The configuration of the <literal>Location</literal> "
"entity and <literal>Gangster-Hangout</literal> relationship follows:"
msgstr ""
+"对于这个例子，<literal>on-find</literal> 部分没有修改 gangster 的 <literal>findAll_onfind<"
+"/literal> 查询的配置。下面是 <literal>Location</literal> entity 和 <literal>"
+"Gangster-Hangout</literal> 关系的配置："
#. Tag: title
#: The_CMP_Engine.xml:2008
#, no-c-format
msgid "The jbosscmp-jdbc.xml Relationship Lazy Loading Configuration"
-msgstr ""
+msgstr "jbosscmp-jdbc.xml 里关于关系的 Lazy 加载的配置"
#. Tag: programlisting
#: The_CMP_Engine.xml:2009
@@ -7090,7 +7144,7 @@
#: The_CMP_Engine.xml:2010
#, no-c-format
msgid "JBoss will execute the following query for the finder:"
-msgstr ""
+msgstr "JBoss 将为该 finder 执行下列查询："
#. Tag: programlisting
#: The_CMP_Engine.xml:2013
@@ -7100,6 +7154,9 @@
" FROM gangster t0_g\n"
" ORDER BY t0_g.id ASC"
msgstr ""
+"SELECT t0_g.id, t0_g.name, t0_g.nick_name, t0_g.badness\n"
+" FROM gangster t0_g\n"
+" ORDER BY t0_g.id ASC"
#. Tag: para
#: The_CMP_Engine.xml:2014
@@ -7109,6 +7166,8 @@
"to load the <literal>city</literal>, <literal>state</literal>, and "
"<literal>zip</literal> fields of the hangout:"
msgstr ""
+"然后，当 hangout 被访问时，JBoss 将执行下面的两个查询来加载 hangout 的 <literal>city</literal>、 <"
+"literal>state</literal> 和 <literal>zip</literal> 字段。"
#. Tag: programlisting
#: The_CMP_Engine.xml:2017
@@ -7144,112 +7203,112 @@
#: The_CMP_Engine.xml:2022
#, no-c-format
msgid "on-find Optimized Relationship Query Execution"
-msgstr ""
+msgstr "执行通过 on-find 优化的关系查询"
#. Tag: entry
#: The_CMP_Engine.xml:2053
-#, fuzzy, no-c-format
+#, no-c-format
msgid "city"
-msgstr "client"
+msgstr "city"
#. Tag: entry
#: The_CMP_Engine.xml:2056
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>st</entry>"
-msgstr "<entry>yes</entry>"
+msgstr "<entry>st</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2059
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>zip</entry>"
-msgstr "<entry>DB2</entry>"
+msgstr "<entry>zip</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2084 The_CMP_Engine.xml:2113 The_CMP_Engine.xml:2142
#: The_CMP_Engine.xml:2171 The_CMP_Engine.xml:2200
#, no-c-format
msgid "San Fran"
-msgstr ""
+msgstr "San Fran"
#. Tag: entry
#: The_CMP_Engine.xml:2087 The_CMP_Engine.xml:2116 The_CMP_Engine.xml:2145
#: The_CMP_Engine.xml:2174 The_CMP_Engine.xml:2203
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>CA</entry>"
-msgstr "<entry>yes</entry>"
+msgstr "<entry>CA</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2090
#, no-c-format
msgid "94108"
-msgstr ""
+msgstr "94108"
#. Tag: entry
#: The_CMP_Engine.xml:2119 The_CMP_Engine.xml:2148 The_CMP_Engine.xml:2177
#: The_CMP_Engine.xml:2206
#, no-c-format
msgid "94133"
-msgstr ""
+msgstr "94133"
#. Tag: entry
#: The_CMP_Engine.xml:2229
#, no-c-format
msgid "New York"
-msgstr ""
+msgstr "New York"
#. Tag: entry
#: The_CMP_Engine.xml:2232
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>NY</entry>"
-msgstr "<entry>yes</entry>"
+msgstr "<entry>NY</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2235
#, no-c-format
msgid "10017"
-msgstr ""
+msgstr "10017"
#. Tag: entry
#: The_CMP_Engine.xml:2258
#, no-c-format
msgid "Chicago"
-msgstr ""
+msgstr "Chicago"
#. Tag: entry
#: The_CMP_Engine.xml:2261
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>IL</entry>"
-msgstr "<entry>yes</entry>"
+msgstr "<entry>IL</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2264
#, no-c-format
msgid "60661"
-msgstr ""
+msgstr "60661"
#. Tag: entry
#: The_CMP_Engine.xml:2287
#, no-c-format
msgid "Las Vegas"
-msgstr ""
+msgstr "Las Vegas"
#. Tag: entry
#: The_CMP_Engine.xml:2290
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<entry>NV</entry>"
-msgstr "<entry>yes</entry>"
+msgstr "<entry>NV</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2293
#, no-c-format
msgid "89109"
-msgstr ""
+msgstr "89109"
#. Tag: title
#: The_CMP_Engine.xml:2305
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Lazy loading result sets"
-msgstr "限制结果集内容"
+msgstr "Lazy 加载的结果集"
#. Tag: para
#: The_CMP_Engine.xml:2306
@@ -8828,8 +8887,7 @@
msgid ""
"<emphasis role=\"bold\">auto-increment-template</emphasis>: This declares "
"the SQL template for specifying auto increment columns."
-msgstr ""
-"<emphasis role=\"bold\">parameter</emphasis>：这个元素描述了操作的签名。"
+msgstr "<emphasis role=\"bold\">parameter</emphasis>：这个元素描述了操作的签名。"
#. Tag: para
#: The_CMP_Engine.xml:2764
@@ -9257,3 +9315,4 @@
"<emphasis role=\"bold\">mapper</emphasis>：处理 <literal>java-type</literal> "
"和 <literal>mapped-type</literal> 之间的转换的 <literal>Mapper</literal> 接口"
"实现的全限定名。"
+
More information about the jboss-cvs-commits
mailing list