[jboss-cvs] JBossAS SVN: r73387 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 14 03:02:08 EDT 2008
Author: xhuang at jboss.com
Date: 2008-05-14 03:02:08 -0400 (Wed, 14 May 2008)
New Revision: 73387
Modified:
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/The_CMP_Engine.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po 2008-05-14 05:40:05 UTC (rev 73386)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po 2008-05-14 07:02:08 UTC (rev 73387)
@@ -9,7 +9,7 @@
"Project-Id-Version: The_CMP_Engine\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-11-05 06:04+0000\n"
-"PO-Revision-Date: 2008-05-13 19:18+1000\n"
+"PO-Revision-Date: 2008-05-14 15:00+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -4020,7 +4020,7 @@
"<emphasis role=\"bold\">additional-columns</emphasis>: Declares other "
"columns to be selected to satisfy ordering by arbitrary columns with finders "
"or to facilitate aggregate functions in selects."
-msgstr ""
+msgstr "<emphasis role=\"bold\">additional-columns</emphasis>：声明其他列来满足按任意带有 finder 的列排序的需要或者利用 select 里的集合函数（aggregate function）。"
#. Tag: para
#: The_CMP_Engine.xml:1006
@@ -4256,7 +4256,7 @@
msgid ""
"Now we well see an example which overrides a select to return all of the zip "
"codes an <literal>Organization</literal> operates in."
-msgstr ""
+msgstr "现在我们来看看一个例子，它覆盖 select 并返回 <literal>Organization</literal> 操作的所有 zip code。"
#. Tag: programlisting
#: The_CMP_Engine.xml:1048
@@ -4363,7 +4363,7 @@
"the <literal>datasourcemapping</literal> for the entity. An unknown DVC is "
"serialized and then set as a parameter. Note that most databases do not "
"support the use of a BLOB value in a WHERE clause."
-msgstr ""
+msgstr "<emphasis role=\"bold\">simple</emphasis>：simple 参数可以是任何类型，除了已知的（映射的）DVC 或 entity。simple 参数之包含参数序号，如 <literal>{0}</literal>。在设置了 simple 参数后，该 entity 的 <literal>datasourcemapping</literal> 决定用来设置这个参数的 JDBC 类型。未知的 DVC 会被序列化之后再设置为参数。请注意大多数数据库都不支持在 WHERE 子句里使用 BLOB 值。"
#. Tag: para
#: The_CMP_Engine.xml:1065
@@ -4380,6 +4380,9 @@
"type that is declared for that property in the <literal>dependent-value-"
"class</literal> element."
msgstr ""
+"<emphasis role=\"bold\">DVC</emphasis>：DVC 参数可以是任何已知的（映射的）DVC。DVC 参数必须通过简单属性（不能是另外一个 DVC）间接引用。例如，如果我们有一个类型为 <literal>ContactInfo</literal> 的 CVS 属性，有效的参数声明可以是 <literal>{0.email}</literal> 和 <literal>{0.cell.areaCode}</literal>，但不能是 <literal>{0.cell}</literal>。用来设置参数的 JDBC 类型基于属性的类型和 entity 的 <literal>datasourcemapping</"
+"literal>。在 <literal>dependent-value-"
+"class</literal> 元素为该属性声明的 JDBC 类型被用来设置这个参数。"
#. Tag: para
#: The_CMP_Engine.xml:1070
@@ -4397,7 +4400,7 @@
"restriction may be removed in later versions). The JDBC type used to set the "
"parameter is the JDBC type that is declared for that field in the entity "
"declaration."
-msgstr ""
+msgstr "<emphasis role=\"bold\">entity</emphasis>：entity 参数可以是应用程序里的任何 entity。entity 参数必须通过简单主键字段或者 DVC 主键字段的简单属性进行间接引用。例如，如果我们有一个类型为 <literal>Gangster</literal> 的参数，其有效的参数声明将是 <literal>{0.gangsterId}</literal>。如果我们有某个带有类型为 <literal>ContactInfo</literal> 的主键字段的 entity，<literal>其有效参数</literal>声明将是 <literal>{0.info.cell.areaCode}</literal>。只有 entity 的主键成员的字段才可以被间接引用（以后的版本里可能取消这个限制）。在 entity 声明里为这个字段声明的 JDBC 类型被用来设置这个参数。"
#. Tag: title
#: The_CMP_Engine.xml:1080
@@ -4581,13 +4584,13 @@
"entity bean violates the EJB specification in that it implements a finder, "
"and the JBoss EJB verifier will fail the deployment of such an entity unless "
"the StrictVerifier attribute is set to false."
-msgstr ""
+msgstr "这是一个非常有用的 finder，因为它可以快速地把主键转换成实际的Eentity 对象而不需要连接数据库。它一个缺点是创建了一个带有不存在于数据库里的主键的 Entity 对象。如果在这个“坏”的 Entity 上调用了任何方法，NoSuchEntityException 将被抛出。它的另外一个缺点是结果 entity bean 违背了 EJB 规格，因为它实现了一个 finder，除非把 StrictVerifier 属性设为 false，否则 JBoss EJB verifier 在部署它时就会失败。"
#. Tag: title
#: The_CMP_Engine.xml:1112
#, no-c-format
msgid "Optimized Loading"
-msgstr ""
+msgstr "优化加载"
#. Tag: para
#: The_CMP_Engine.xml:1113
@@ -4600,13 +4603,13 @@
"configuration. Tuning of the loading process really requires a holistic "
"understanding of the loading system, so this chapter may have to be read "
"more than once."
-msgstr ""
+msgstr "优化加载的目的是使用最少的查询次数、加载最少的数据来完成事务。JBoss 的调整需要对加载过程有着详细了解。本节描述了 JBoss 加载过程的内部细节及其配置。对加载过程的调整确实需要完整地理解加载系统，所以你可能需要对本节内容进行多次反复阅读。"
#. Tag: title
#: The_CMP_Engine.xml:1117
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Loading Scenario"
-msgstr "装载对象"
+msgstr "加载模式"
#. Tag: para
#: The_CMP_Engine.xml:1118
@@ -4616,7 +4619,7 @@
"scenario. The most common scenario is to locate a collection of entities and "
"iterate over the results performing some operation. The following example "
"generates an html table containing all of the gangsters:"
-msgstr ""
+msgstr "了解加载过程的最容易的方法就是查看其使用模式。最常用的模式是选定一个 entity 集合并重复某个操作。下面的例子生成了一个包含所有 gangster 的 HTML 表格："
#. Tag: programlisting
#: The_CMP_Engine.xml:1121
@@ -4673,7 +4676,7 @@
"Assume this code is called within a single transaction and all optimized "
"loading has been disabled. At the <literal>findAll_none</literal> call, "
"JBoss will execute the following query:"
-msgstr ""
+msgstr "假设在单一事务里调用这段代码且禁用了所有的优化加载。在 <literal>findAll_none</literal> 调用时，JBoss 将执行下面的查询："
#. Tag: programlisting
#: The_CMP_Engine.xml:1125
@@ -4683,6 +4686,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:1126
@@ -4690,7 +4696,7 @@
msgid ""
"Then as each of the eight gangster in the sample database is accessed, JBoss "
"will execute the following eight queries:"
-msgstr ""
+msgstr "然后当示例数据库中的 8 个 gangster 都被访问时，JBoss 将执行下面的 8 个查询："
#. Tag: programlisting
#: The_CMP_Engine.xml:1129
@@ -4745,6 +4751,8 @@
"emphasis> problem and is addressed with the read-ahead strategies described "
"in the following sections."
msgstr ""
+"这种模式有两个问题。首先，因为 JBoss 为每个 <literal>findAll</literal> 都执行一个查询且对于每个找到的元素都用查询进行访问。其原因是 JBoss 容器内部对查询结果的处理。虽然好像在执行查询时，实际选择的 entity bean 都被返回，但其实 JBoss 只返回符合条件的 entity 的主键，而直到对其进行方法调用时才载入这个 entity。这就是有名的 <emphasis>n+1</"
+"emphasis> 问题，而后续章节所讨论的 read-ahead 策略则可以解决这个问题。"
#. Tag: para
#: The_CMP_Engine.xml:1133
@@ -4755,12 +4763,14 @@
"are never accessed. (we have disabled the complex <literal>contactInfo</"
"literal> field for the sake of clarity)"
msgstr ""
+"其次，不必要地加载了未使用的字段的值。JBoss 加载从未被访问的 <literal>hangout</literal> 和 <literal>organization</literal> 字段。（为清楚起见，我们禁用了复杂的 <literal>contactInfo</"
+"literal> 字段）"
#. Tag: para
#: The_CMP_Engine.xml:1136 The_CMP_Engine.xml:2018
#, no-c-format
msgid "The following table shows the execution of the queries:"
-msgstr ""
+msgstr "下面的表展示了这些查询的执行情况："
#. Tag: title
#: The_CMP_Engine.xml:1140
@@ -4778,7 +4788,7 @@
#. Tag: entry
#: The_CMP_Engine.xml:1147 The_CMP_Engine.xml:1363 The_CMP_Engine.xml:1681
#: The_CMP_Engine.xml:2038
-#, fuzzy, no-c-format
+#, no-c-format
msgid "name"
msgstr "名字"
@@ -5118,12 +5128,14 @@
"JBoss automatically adds a group named <literal>*</literal> (the star group) "
"that contains every CMP field and CMR field with a foreign key in the entity."
msgstr ""
+"在这个例子里声明了两个加载组（load group）：<literal>basic</literal> 和 "
+"<literal>contact info</literal>。请注意，加载组并不需要相互排斥。例如，这两个加载组都可以包含 <literal>nickName</literal> 字段。除了所声明的加载组，JBoss 还自动地添加一个名为 <literal>*</literal> 的组，它包含每个带有 entity 里的外键的 CMP 字段和 CMR 字段。"
#. Tag: title
#: The_CMP_Engine.xml:1342
#, no-c-format
msgid "Read-ahead"
-msgstr ""
+msgstr "Read-ahead"
#. Tag: para
#: The_CMP_Engine.xml:1343
@@ -5139,7 +5151,7 @@
"accessed. Instead, it is stored in the preload cache where it remains until "
"it is loaded into an entity or the end of the transaction occurs. The "
"following sections describe the read-ahead strategies."
-msgstr ""
+msgstr "JBoss 里的优化加载被称为预读（read-ahead）。这指的是在读取被加载的 entity 的某一行时，同时还读取下面的几行，所以被称为预读（read-ahead）。JBoss 实现两个主要的策略（<literal>on-find</literal> 和 <literal>on-load</literal>）来优化前面章节所提及的加载问题。在预读期间加载的额外数据不会马上和内存里的 entity 对象相关联，因为 JBoss 里的 entity 知道实际被访问时才会实例化。相反，它会存储在预加载的缓存里，而知道事务结束时才会载入到 entity 里。下面的章节描述了预读策略。"
#. Tag: title
#: The_CMP_Engine.xml:1347
More information about the jboss-cvs-commits
mailing list