[jboss-cvs] JBossAS SVN: r91914 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Aug 2 20:13:06 EDT 2009
Author: xhuang at jboss.com
Date: 2009-08-02 20:13:05 -0400 (Sun, 02 Aug 2009)
New Revision: 91914
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po 2009-08-01 21:47:17 UTC (rev 91913)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po 2009-08-03 00:13:05 UTC (rev 91914)
@@ -9,7 +9,7 @@
"Project-Id-Version: The_CMP_Engine\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-07-22 10:37+1000\n"
+"PO-Revision-Date: 2009-08-03 10:11+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -4335,19 +4335,18 @@
#. Tag: para
#: The_CMP_Engine.xml:974
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">select</emphasis>: The <literal>select</literal> "
"element specifies what is to be selected and consists of the following "
"elements:"
msgstr ""
"<emphasis role=\"bold\">select</emphasis>:<literal>select</literal> 元素指定"
-"所选择的内容,它由下面的元素组成:"
+"所选择的内容,它由下面的元素组成: "
#. Tag: para
#: The_CMP_Engine.xml:979
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">distinct</emphasis>: If this empty element is "
"present, JBoss will add the <literal>DISTINCT</literal> keyword to the "
@@ -4358,45 +4357,44 @@
"<emphasis role=\"bold\">distinct</emphasis>:如果使用了这个空的元素,JBoss 将"
"把 <literal>DISTINCT</literal> 关键字添加到生成的 <literal>SELECT</literal> "
"子句里。如果方法返回 <literal>java.util.Set</literal> 则会缺省使用 "
-"<literal>DISTINCT</literal>。"
+"<literal>DISTINCT</literal>。 "
#. Tag: para
#: The_CMP_Engine.xml:984
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ejb-name</emphasis>: This is the <literal>ejb-name</"
"literal> of the entity that will be selected. This is only required if the "
"query is for a select method."
msgstr ""
"<emphasis role=\"bold\">ejb-name</emphasis>:这是将被选择的 entity 的 "
-"<literal>ejb-name</literal>。它只有在查询是 select 方法时才是必需的。"
+"<literal>ejb-name</literal>。它只有在查询是 select 方法时才是必需的。 "
#. Tag: para
#: The_CMP_Engine.xml:989
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">field-name</emphasis>: This is the name of the CMP "
"field that will be selected from the specified entity. The default is to "
"select entire entity."
msgstr ""
"<emphasis role=\"bold\">field-name</emphasis>:这是将从指定的 entity 里选择"
-"的 CMP 字段的名称。缺省是选择整个 entity。"
+"的 CMP 字段的名称。缺省是选择整个 entity。 "
#. Tag: para
#: The_CMP_Engine.xml:994
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">alias</emphasis>: This specifies the alias that will "
"be used for the main select table. The default is to use the <literal>ejb-"
"name</literal>."
msgstr ""
"<emphasis role=\"bold\">alias</emphasis>:它指定用于主 select 表的别名。缺省"
-"是使用 <literal>ejb-name</literal>。"
+"是使用 <literal>ejb-name</literal>。 "
#. Tag: para
#: The_CMP_Engine.xml:999
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">additional-columns</emphasis>: Declares other "
"columns to be selected to satisfy ordering by arbitrary columns with finders "
@@ -4404,60 +4402,58 @@
msgstr ""
"<emphasis role=\"bold\">additional-columns</emphasis>:声明其他列来满足按任意"
"带有 finder 的列排序的需要或者利用 select 里的集合函数(aggregate "
-"function)。"
+"function)。 "
#. Tag: para
#: The_CMP_Engine.xml:1006
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">from</emphasis>: The <literal>from</literal> element "
"declares additional SQL to append to the generated <literal>FROM</literal> "
"clause."
msgstr ""
"<emphasis role=\"bold\">from</emphasis>:<literal>from</literal> 元素声明附加"
-"在生成的 <literal>FROM</literal> 子句后面的额外的 SQL。"
+"在生成的 <literal>FROM</literal> 子句后面的额外的 SQL。 "
#. Tag: para
#: The_CMP_Engine.xml:1011
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">where</emphasis>: The <literal>where</literal> "
"element declares the <literal>WHERE</literal> clause for the query."
msgstr ""
"<emphasis role=\"bold\">where</emphasis>:<literal>where</literal> 元素声明用"
-"于查询的 <literal>WHERE</literal> 子句。"
+"于查询的 <literal>WHERE</literal> 子句。 "
#. Tag: para
#: The_CMP_Engine.xml:1016
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">order</emphasis>: The <literal>order</literal> "
"element declares the <literal>ORDER</literal> clause for the query."
msgstr ""
"<emphasis role=\"bold\">order</emphasis>:<literal>order</literal> 元素声明查"
-"询语句的 <literal>ORDER</literal> 子句。"
+"询语句的 <literal>ORDER</literal> 子句。 "
#. Tag: para
#: The_CMP_Engine.xml:1021
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">other</emphasis>: The <literal>other</literal> "
"element declares additional SQL that is appended to the end of the query."
msgstr ""
"<emphasis role=\"bold\">other</emphasis>:<literal>other</literal> 元素声明附"
-"加在查询语句后面的额外 SQL。"
+"加在查询语句后面的额外 SQL。 "
#. Tag: para
#: The_CMP_Engine.xml:1026
#, no-c-format
-#, fuzzy
msgid "The following is an example DeclaredSQL declaration."
-msgstr "下面是一个 DeclaredSQL 声明的例子。"
+msgstr "下面是一个 DeclaredSQL 声明的例子。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1029
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -4508,14 +4504,12 @@
#. Tag: para
#: The_CMP_Engine.xml:1030 The_CMP_Engine.xml:1038 The_CMP_Engine.xml:1641
#, no-c-format
-#, fuzzy
msgid "The generated SQL would be:"
-msgstr "生成的 SQL 将是:"
+msgstr "生成的 SQL 将是: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1033
#, no-c-format
-#, fuzzy
msgid ""
"SELECT id\n"
"FROM gangster\n"
@@ -4530,7 +4524,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1034
#, no-c-format
-#, fuzzy
msgid ""
"As you can see, JBoss generates the <literal>SELECT</literal> and "
"<literal>FROM</literal> clauses necessary to select the primary key for this "
@@ -4543,12 +4536,11 @@
"literal> 子句来选择这个 entity 的主键。如果需要的话,你可以指定额外的 "
"<literal>FROM</literal> 子句,它附加在自动生成的 <literal>FROM</literal> 子句"
"的后面。下面是一个带有额外 <literal>FROM</literal> 子句的 DeclaredSQL 声明的"
-"例子。"
+"例子。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1037
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -4615,7 +4607,6 @@
#. Tag: programlisting
#: The_CMP_Engine.xml:1041
#, no-c-format
-#, fuzzy
msgid ""
"SELECT DISTINCT boss.id\n"
" FROM gangster boss, gangster g, organization o\n"
@@ -4630,7 +4621,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1042
#, no-c-format
-#, fuzzy
msgid ""
"Notice that the <literal>FROM</literal> clause starts with a comma. This is "
"because the container appends the declared <literal>FROM</literal> clause to "
@@ -4657,23 +4647,21 @@
"literal> 风格的列声明的 <literal>SELECT</literal> 子句。但不是所有的数据库厂"
"商都支持这种语法,所以最好是声明别名。可选的空的 <literal>distinct</literal> "
"元素使 <literal>SELECT</literal> 子句使用 <literal>SELECT DISTINCT</literal> "
-"声明。select 方法也可以用 DeclaredSQL 声明来查询 CMP 字段。"
+"声明。select 方法也可以用 DeclaredSQL 声明来查询 CMP 字段。 "
#. Tag: para
#: The_CMP_Engine.xml:1045
#, no-c-format
-#, fuzzy
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 ""
"现在我们来看看一个例子,它覆盖 select 并返回 <literal>Organization</literal> "
-"操作的所有 zip code。"
+"操作的所有 zip code。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1048
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -4730,14 +4718,12 @@
#. Tag: para
#: The_CMP_Engine.xml:1049
#, no-c-format
-#, fuzzy
msgid "The corresponding SQL would be:"
-msgstr "相应的 SQL 将是:"
+msgstr "相应的 SQL 将是: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1052
#, no-c-format
-#, fuzzy
msgid ""
"SELECT DISTINCT hangout.zip\n"
" FROM location hangout, organization o, gangster g\n"
@@ -4754,14 +4740,12 @@
#. Tag: title
#: The_CMP_Engine.xml:1054
#, no-c-format
-#, fuzzy
msgid "Parameters"
-msgstr "参数(Parameters)"
+msgstr "参数(Parameters) "
#. Tag: para
#: The_CMP_Engine.xml:1055
#, no-c-format
-#, fuzzy
msgid ""
"DeclaredSQL uses a completely new parameter handling system, which supports "
"entity and DVC parameters. Parameters are enclosed in curly brackets and use "
@@ -4770,12 +4754,11 @@
msgstr ""
"DeclaredSQL 使用一个全新的参数处理系统,它支持 entity 和 DVC 参数。参数括在花"
"括号里且使用基于 0 的索引,这和基于 1 的 EJB-QL 的参数不同。它有 3 中参数类"
-"别:simple、DVC 和 entity。"
+"别:simple、DVC 和 entity。 "
#. Tag: para
#: The_CMP_Engine.xml:1060
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">simple</emphasis>: A simple parameter can be of any "
"type except for a known (mapped) DVC or an entity. A simple parameter only "
@@ -4789,12 +4772,11 @@
"知的(映射的)DVC 或 entity。simple 参数之包含参数序号,如 <literal>{0}</"
"literal>。在设置了 simple 参数后,该 entity 的 <literal>datasourcemapping</"
"literal> 决定用来设置这个参数的 JDBC 类型。未知的 DVC 会被序列化之后再设置为"
-"参数。请注意大多数数据库都不支持在 WHERE 子句里使用 BLOB 值。"
+"参数。请注意大多数数据库都不支持在 WHERE 子句里使用 BLOB 值。 "
#. Tag: para
#: The_CMP_Engine.xml:1065
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">DVC</emphasis>: A DVC parameter can be any known "
"(mapped) DVC. A DVC parameter must be dereferenced down to a simple property "
@@ -4813,12 +4795,11 @@
"<literal>{0.email}</literal> 和 <literal>{0.cell.areaCode}</literal>,但不能"
"是 <literal>{0.cell}</literal>。用来设置参数的 JDBC 类型基于属性的类型和 "
"entity 的 <literal>datasourcemapping</literal>。在 <literal>dependent-value-"
-"class</literal> 元素为该属性声明的 JDBC 类型被用来设置这个参数。"
+"class</literal> 元素为该属性声明的 JDBC 类型被用来设置这个参数。 "
#. Tag: para
#: The_CMP_Engine.xml:1070
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">entity</emphasis>: An entity parameter can be any "
"entity in the application. An entity parameter must be dereferenced down to "
@@ -4840,19 +4821,17 @@
"<literal>ContactInfo</literal> 的主键字段的 entity,<literal>其有效参数</"
"literal>声明将是 <literal>{0.info.cell.areaCode}</literal>。只有 entity 的主"
"键成员的字段才可以被间接引用(以后的版本里可能取消这个限制)。在 entity 声明"
-"里为这个字段声明的 JDBC 类型被用来设置这个参数。"
+"里为这个字段声明的 JDBC 类型被用来设置这个参数。 "
#. Tag: title
#: The_CMP_Engine.xml:1080
#, no-c-format
-#, fuzzy
msgid "EJBQL 2.1 and SQL92 queries"
-msgstr "EJBQL 2.1 和 SQL92 查询"
+msgstr "EJBQL 2.1 和 SQL92 查询 "
#. Tag: para
#: The_CMP_Engine.xml:1081
#, no-c-format
-#, fuzzy
msgid ""
"The default query compiler doesn't fully support EJB-QL 2.1 or the SQL92 "
"standard. If you need either of these functions, you can replace the query "
@@ -4861,12 +4840,11 @@
msgstr ""
"缺省的查询编译器不完全支持 EJB-QL 2.1 或 SQL92 标准。如果你需要使用它们的函"
"数,你可以替换查询编译器。你可以在 <literal>standardjbosscmp-jdbc.xml</"
-"literal> 里指定缺省的编译器。"
+"literal> 里指定缺省的编译器。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1084
#, no-c-format
-#, fuzzy
msgid ""
"<defaults>\n"
" ...\n"
@@ -4885,18 +4863,16 @@
#. Tag: para
#: The_CMP_Engine.xml:1085
#, no-c-format
-#, fuzzy
msgid ""
"To use the SQL92 compiler, simply specify the SQL92 compiler in <literal>ql-"
"compiler</literal> element."
msgstr ""
"要使用 SQL92 编译器,简单地在 <literal>ql-compiler</literal> 元素里指定 "
-"SQL92 编译器就可以了。"
+"SQL92 编译器就可以了。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1088
#, no-c-format
-#, fuzzy
msgid ""
"<defaults>\n"
" ...\n"
@@ -4915,7 +4891,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1089
#, no-c-format
-#, fuzzy
msgid ""
"This changes the query compiler for all beans in the entire system. You can "
"also specify the ql-compiler for each element in <literal>jbosscmp-jdbc.xml</"
@@ -4923,12 +4898,11 @@
msgstr ""
"这会改变整个系统里的所有 bean 使用的查询编译器。你也可以在 <literal>jbosscmp-"
"jdbc.xml</literal> 里为每个元素指定查询编译器。下面是使用其中一个早前的查询的"
-"例子。"
+"例子。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1092
#, no-c-format
-#, fuzzy
msgid ""
"<query>\n"
" <query-method>\n"
@@ -4965,7 +4939,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1093
#, no-c-format
-#, fuzzy
msgid ""
"One important limitation of SQL92 query compiler is that it always selects "
"all the fields of an entity regardless the <literal>read-ahead</literal> "
@@ -4983,19 +4956,17 @@
"仅是主键字段,但只有主键字段会从 <literal>ResultSet</literal> 里读取。然后其"
"他字段也实际上将被载入 read-ahead 缓存。运行带有缺省的 load group 的 "
"<literal>on-find</literal><literal>read-ahead</literal> 则和我们所预期的相"
-"同。"
+"同。 "
#. Tag: title
#: The_CMP_Engine.xml:1099
#, no-c-format
-#, fuzzy
msgid "BMP Custom Finders"
-msgstr "自定义的 BMP Finder"
+msgstr "自定义的 BMP Finder "
#. Tag: para
#: The_CMP_Engine.xml:1100
#, no-c-format
-#, fuzzy
msgid ""
"JBoss also supports bean managed persistence custom finders. If a custom "
"finder method matches a finder declared in the home or local home interface, "
@@ -5007,12 +4978,11 @@
"JBoss 也支持 bean 管理的持久性自定义 finder。如果自定义的 finder 方法和 home "
"或 local home 接口里声明的 finder 相符,JBoss 将总是先于 <literal>ejb-jar."
"xml</literal> 或 <literal>jbosscmp-jdbc.xml</literal> 里声明的其他实现调用自"
-"定义的 finder。下面的简单示例根据主键集合来查找 entity:"
+"定义的 finder。下面的简单示例根据主键集合来查找 entity: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1103
#, no-c-format
-#, fuzzy
msgid ""
"public abstract class GangsterBean\n"
" implements EntityBean \n"
@@ -5035,7 +5005,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1104
#, no-c-format
-#, fuzzy
msgid ""
"This is a very useful finder because it quickly coverts primary keys into "
"real Entity objects without contacting the database. One drawback is that it "
@@ -5051,19 +5020,17 @@
"象。如果在这个“坏”的 Entity 上调用了任何方法,NoSuchEntityException 将被抛"
"出。它的另外一个缺点是结果 entity bean 违背了 EJB 规格,因为它实现了一个 "
"finder,除非把 StrictVerifier 属性设为 false,否则 JBoss EJB verifier 在部署"
-"它时就会失败。"
+"它时就会失败。 "
#. Tag: title
#: The_CMP_Engine.xml:1112
#, no-c-format
-#, fuzzy
msgid "Optimized Loading"
-msgstr "优化加载"
+msgstr "优化加载 "
#. Tag: para
#: The_CMP_Engine.xml:1113
#, no-c-format
-#, fuzzy
msgid ""
"The goal of optimized loading is to load the smallest amount of data "
"required to complete a transaction in the fewest number of queries. The "
@@ -5076,19 +5043,17 @@
"优化加载的目的是使用最少的查询次数、加载最少的数据来完成事务。JBoss 的调整需"
"要对加载过程有着详细了解。本节描述了 JBoss 加载过程的内部细节及其配置。对加载"
"过程的调整确实需要完整地理解加载系统,所以你可能需要对本节内容进行多次反复阅"
-"读。"
+"读。 "
#. Tag: title
#: The_CMP_Engine.xml:1117
#, no-c-format
-#, fuzzy
msgid "Loading Scenario"
-msgstr "加载模式"
+msgstr "加载模式 "
#. Tag: para
#: The_CMP_Engine.xml:1118
#, no-c-format
-#, fuzzy
msgid ""
"The easiest way to investigate the loading process is to look at a usage "
"scenario. The most common scenario is to locate a collection of entities and "
@@ -5096,12 +5061,11 @@
"generates an html table containing all of the gangsters:"
msgstr ""
"了解加载过程的最容易的方法就是查看其使用模式。最常用的模式是选定一个 entity "
-"集合并重复某个操作。下面的例子生成了一个包含所有 gangster 的 HTML 表格:"
+"集合并重复某个操作。下面的例子生成了一个包含所有 gangster 的 HTML 表格: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1121
#, no-c-format
-#, fuzzy
msgid ""
"public String createGangsterHtmlTable_none() \n"
" throws FinderException \n"
@@ -5150,19 +5114,17 @@
#. Tag: para
#: The_CMP_Engine.xml:1122
#, no-c-format
-#, fuzzy
msgid ""
"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 ""
"假设在单一事务里调用这段代码且禁用了所有的优化加载。在 "
-"<literal>findAll_none</literal> 调用时,JBoss 将执行下面的查询:"
+"<literal>findAll_none</literal> 调用时,JBoss 将执行下面的查询: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1125
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_g.id\n"
" FROM gangster t0_g\n"
@@ -5175,16 +5137,14 @@
#. Tag: para
#: The_CMP_Engine.xml:1126
#, no-c-format
-#, fuzzy
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
#, no-c-format
-#, fuzzy
msgid ""
"SELECT name, nick_name, badness, hangout, organization\n"
" FROM gangster WHERE (id=0)\n"
@@ -5223,7 +5183,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1130
#, no-c-format
-#, fuzzy
msgid ""
"There are two problems with this scenario. First, an excessive number of "
"queries are executed because JBoss executes one query for the "
@@ -5241,12 +5200,11 @@
"果的处理。虽然好像在执行查询时,实际选择的 entity bean 都被返回,但其实 "
"JBoss 只返回符合条件的 entity 的主键,而直到对其进行方法调用时才载入这个 "
"entity。这就是有名的 <emphasis>n+1</emphasis> 问题,而后续章节所讨论的 read-"
-"ahead 策略则可以解决这个问题。"
+"ahead 策略则可以解决这个问题。 "
#. Tag: para
#: The_CMP_Engine.xml:1133
#, no-c-format
-#, fuzzy
msgid ""
"Second, the values of unused fields are loaded needlessly. JBoss loads the "
"<literal>hangout</literal> and <literal>organization</literal> fields, which "
@@ -5255,41 +5213,38 @@
msgstr ""
"其次,不必要地加载了未使用的字段的值。JBoss 加载从未被访问的 "
"<literal>hangout</literal> 和 <literal>organization</literal> 字段。(为清楚"
-"起见,我们禁用了复杂的 <literal>contactInfo</literal> 字段)"
+"起见,我们禁用了复杂的 <literal>contactInfo</literal> 字段) "
#. Tag: para
#: The_CMP_Engine.xml:1136 The_CMP_Engine.xml:2018
#, no-c-format
-#, fuzzy
msgid "The following table shows the execution of the queries:"
-msgstr "下面的表展示了这些查询的执行情况:"
+msgstr "下面的表展示了这些查询的执行情况: "
#. Tag: title
#: The_CMP_Engine.xml:1140
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Unoptimized Query Execution"
-msgstr "执行未优化的查询"
+msgstr "执行未优化的查询 "
#. Tag: entry
#: The_CMP_Engine.xml:1144 The_CMP_Engine.xml:1360 The_CMP_Engine.xml:1678
#: The_CMP_Engine.xml:2035 The_CMP_Engine.xml:2050
#, no-c-format
-#, fuzzy
msgid "<entry>id</entry>"
msgstr "<entry>id</entry>"
#. 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 "名字"
+msgstr "名字 "
#. Tag: entry
#: The_CMP_Engine.xml:1150 The_CMP_Engine.xml:1366 The_CMP_Engine.xml:1684
#: The_CMP_Engine.xml:2041
#, no-c-format
-#, fuzzy
msgid "nick_name"
msgstr "nick_name"
@@ -5297,7 +5252,6 @@
#: The_CMP_Engine.xml:1153 The_CMP_Engine.xml:1369 The_CMP_Engine.xml:1687
#: The_CMP_Engine.xml:2044
#, no-c-format
-#, fuzzy
msgid "badness"
msgstr "badness"
@@ -5305,23 +5259,20 @@
#: The_CMP_Engine.xml:1156 The_CMP_Engine.xml:1372 The_CMP_Engine.xml:1690
#: The_CMP_Engine.xml:2047
#, no-c-format
-#, fuzzy
msgid "hangout"
msgstr "hangout"
#. Tag: entry
#: The_CMP_Engine.xml:1159 The_CMP_Engine.xml:1375 The_CMP_Engine.xml:1693
#, no-c-format
-#, fuzzy
msgid "organization"
-msgstr "organization"
+msgstr ""
#. Tag: entry
#: The_CMP_Engine.xml:1166 The_CMP_Engine.xml:1178 The_CMP_Engine.xml:1382
#: The_CMP_Engine.xml:1394 The_CMP_Engine.xml:1700 The_CMP_Engine.xml:1712
#: The_CMP_Engine.xml:2066 The_CMP_Engine.xml:2078 The_CMP_Engine.xml:2081
#, no-c-format
-#, fuzzy
msgid "<entry>0</entry>"
msgstr "<entry>0</entry>"
@@ -5329,7 +5280,6 @@
#: The_CMP_Engine.xml:1169 The_CMP_Engine.xml:1385 The_CMP_Engine.xml:1703
#: The_CMP_Engine.xml:2069
#, no-c-format
-#, fuzzy
msgid "Yojimbo"
msgstr "Yojimbo"
@@ -5337,7 +5287,6 @@
#: The_CMP_Engine.xml:1172 The_CMP_Engine.xml:1388 The_CMP_Engine.xml:1706
#: The_CMP_Engine.xml:2072
#, no-c-format
-#, fuzzy
msgid "Bodyguard"
msgstr "Bodyguard"
@@ -5348,7 +5297,6 @@
#: The_CMP_Engine.xml:2075 The_CMP_Engine.xml:2269 The_CMP_Engine.xml:2281
#: The_CMP_Engine.xml:2284
#, no-c-format
-#, fuzzy
msgid "<entry>7</entry>"
msgstr "<entry>7</entry>"
@@ -5357,7 +5305,6 @@
#: The_CMP_Engine.xml:1397 The_CMP_Engine.xml:1417 The_CMP_Engine.xml:1437
#: The_CMP_Engine.xml:1715 The_CMP_Engine.xml:1735 The_CMP_Engine.xml:1755
#, no-c-format
-#, fuzzy
msgid "Yakuza"
msgstr "Yakuza"
@@ -5366,7 +5313,6 @@
#: The_CMP_Engine.xml:1414 The_CMP_Engine.xml:1720 The_CMP_Engine.xml:1732
#: The_CMP_Engine.xml:2095 The_CMP_Engine.xml:2107 The_CMP_Engine.xml:2110
#, no-c-format
-#, fuzzy
msgid "<entry>1</entry>"
msgstr "<entry>1</entry>"
@@ -5374,7 +5320,6 @@
#: The_CMP_Engine.xml:1189 The_CMP_Engine.xml:1405 The_CMP_Engine.xml:1723
#: The_CMP_Engine.xml:2098
#, no-c-format
-#, fuzzy
msgid "Takeshi"
msgstr "Takeshi"
@@ -5382,7 +5327,6 @@
#: The_CMP_Engine.xml:1192 The_CMP_Engine.xml:1408 The_CMP_Engine.xml:1726
#: The_CMP_Engine.xml:2101
#, no-c-format
-#, fuzzy
msgid "Master"
msgstr "Master"
@@ -5390,7 +5334,6 @@
#: The_CMP_Engine.xml:1195 The_CMP_Engine.xml:1411 The_CMP_Engine.xml:1729
#: The_CMP_Engine.xml:2104
#, no-c-format
-#, fuzzy
msgid "<entry>10</entry>"
msgstr "<entry>10</entry>"
@@ -5401,7 +5344,6 @@
#: The_CMP_Engine.xml:2124 The_CMP_Engine.xml:2136 The_CMP_Engine.xml:2139
#: The_CMP_Engine.xml:2249
#, no-c-format
-#, fuzzy
msgid "<entry>2</entry>"
msgstr "<entry>2</entry>"
@@ -5409,7 +5351,6 @@
#: The_CMP_Engine.xml:1209 The_CMP_Engine.xml:1425 The_CMP_Engine.xml:1743
#: The_CMP_Engine.xml:2127
#, no-c-format
-#, fuzzy
msgid "Yuriko"
msgstr "Yuriko"
@@ -5417,7 +5358,6 @@
#: The_CMP_Engine.xml:1212 The_CMP_Engine.xml:1428 The_CMP_Engine.xml:1746
#: The_CMP_Engine.xml:2130
#, no-c-format
-#, fuzzy
msgid "Four finger"
msgstr "Four finger"
@@ -5429,7 +5369,6 @@
#: The_CMP_Engine.xml:2133 The_CMP_Engine.xml:2182 The_CMP_Engine.xml:2194
#: The_CMP_Engine.xml:2197 The_CMP_Engine.xml:2220
#, no-c-format
-#, fuzzy
msgid "<entry>4</entry>"
msgstr "<entry>4</entry>"
@@ -5438,7 +5377,6 @@
#: The_CMP_Engine.xml:1454 The_CMP_Engine.xml:1760 The_CMP_Engine.xml:1772
#: The_CMP_Engine.xml:2153 The_CMP_Engine.xml:2165 The_CMP_Engine.xml:2168
#, no-c-format
-#, fuzzy
msgid "<entry>3</entry>"
msgstr "<entry>3</entry>"
@@ -5446,7 +5384,6 @@
#: The_CMP_Engine.xml:1229 The_CMP_Engine.xml:1445 The_CMP_Engine.xml:1763
#: The_CMP_Engine.xml:2156
#, no-c-format
-#, fuzzy
msgid "Chow"
msgstr "Chow"
@@ -5454,7 +5391,6 @@
#: The_CMP_Engine.xml:1232 The_CMP_Engine.xml:1448 The_CMP_Engine.xml:1766
#: The_CMP_Engine.xml:2159
#, no-c-format
-#, fuzzy
msgid "Killer"
msgstr "Killer"
@@ -5462,7 +5398,6 @@
#: The_CMP_Engine.xml:1235 The_CMP_Engine.xml:1451 The_CMP_Engine.xml:1769
#: The_CMP_Engine.xml:2162
#, no-c-format
-#, fuzzy
msgid "<entry>9</entry>"
msgstr "<entry>9</entry>"
@@ -5470,7 +5405,6 @@
#: The_CMP_Engine.xml:1241 The_CMP_Engine.xml:1261 The_CMP_Engine.xml:1457
#: The_CMP_Engine.xml:1477 The_CMP_Engine.xml:1775 The_CMP_Engine.xml:1795
#, no-c-format
-#, fuzzy
msgid "Triads"
msgstr "Triads"
@@ -5478,7 +5412,6 @@
#: The_CMP_Engine.xml:1249 The_CMP_Engine.xml:1465 The_CMP_Engine.xml:1783
#: The_CMP_Engine.xml:2185
#, no-c-format
-#, fuzzy
msgid "Shogi"
msgstr "Shogi"
@@ -5486,7 +5419,6 @@
#: The_CMP_Engine.xml:1252 The_CMP_Engine.xml:1468 The_CMP_Engine.xml:1786
#: The_CMP_Engine.xml:2188
#, no-c-format
-#, fuzzy
msgid "Lightning"
msgstr "Lightning"
@@ -5494,7 +5426,6 @@
#: The_CMP_Engine.xml:1255 The_CMP_Engine.xml:1471 The_CMP_Engine.xml:1789
#: The_CMP_Engine.xml:2191
#, no-c-format
-#, fuzzy
msgid "<entry>8</entry>"
msgstr "<entry>8</entry>"
@@ -5503,7 +5434,6 @@
#: The_CMP_Engine.xml:1494 The_CMP_Engine.xml:1800 The_CMP_Engine.xml:1812
#: The_CMP_Engine.xml:2211 The_CMP_Engine.xml:2223 The_CMP_Engine.xml:2226
#, no-c-format
-#, fuzzy
msgid "<entry>5</entry>"
msgstr "<entry>5</entry>"
@@ -5511,7 +5441,6 @@
#: The_CMP_Engine.xml:1269 The_CMP_Engine.xml:1485 The_CMP_Engine.xml:1803
#: The_CMP_Engine.xml:2214
#, no-c-format
-#, fuzzy
msgid "Valentino"
msgstr "Valentino"
@@ -5519,7 +5448,6 @@
#: The_CMP_Engine.xml:1272 The_CMP_Engine.xml:1488 The_CMP_Engine.xml:1806
#: The_CMP_Engine.xml:2217
#, no-c-format
-#, fuzzy
msgid "Pizza-Face"
msgstr "Pizza-Face"
@@ -5528,7 +5456,6 @@
#: The_CMP_Engine.xml:1497 The_CMP_Engine.xml:1517 The_CMP_Engine.xml:1537
#: The_CMP_Engine.xml:1815 The_CMP_Engine.xml:1835 The_CMP_Engine.xml:1855
#, no-c-format
-#, fuzzy
msgid "Mafia"
msgstr "Mafia"
@@ -5539,7 +5466,6 @@
#: The_CMP_Engine.xml:2240 The_CMP_Engine.xml:2252 The_CMP_Engine.xml:2255
#: The_CMP_Engine.xml:2278
#, no-c-format
-#, fuzzy
msgid "<entry>6</entry>"
msgstr "<entry>6</entry>"
@@ -5547,7 +5473,6 @@
#: The_CMP_Engine.xml:1289 The_CMP_Engine.xml:1505 The_CMP_Engine.xml:1823
#: The_CMP_Engine.xml:2243
#, no-c-format
-#, fuzzy
msgid "Toni"
msgstr "Toni"
@@ -5555,7 +5480,6 @@
#: The_CMP_Engine.xml:1292 The_CMP_Engine.xml:1508 The_CMP_Engine.xml:1826
#: The_CMP_Engine.xml:2246
#, no-c-format
-#, fuzzy
msgid "Toothless"
msgstr "Toothless"
@@ -5563,7 +5487,6 @@
#: The_CMP_Engine.xml:1309 The_CMP_Engine.xml:1525 The_CMP_Engine.xml:1843
#: The_CMP_Engine.xml:2272
#, no-c-format
-#, fuzzy
msgid "Corleone"
msgstr "Corleone"
@@ -5571,21 +5494,18 @@
#: The_CMP_Engine.xml:1312 The_CMP_Engine.xml:1528 The_CMP_Engine.xml:1846
#: The_CMP_Engine.xml:2275
#, no-c-format
-#, fuzzy
msgid "Godfather"
msgstr "Godfather"
#. Tag: title
#: The_CMP_Engine.xml:1331
#, no-c-format
-#, fuzzy
msgid "Load Groups"
-msgstr "加载组(Load Group)"
+msgstr "加载组(Load Group) "
#. Tag: para
#: The_CMP_Engine.xml:1332
#, no-c-format
-#, fuzzy
msgid ""
"The configuration and optimization of the loading system begins with the "
"declaration of named load groups in the entity. A load group contains the "
@@ -5596,12 +5516,11 @@
"对加载系统的配置和优化从 entity 里命名的加载组(load group)声明开始。加载组"
"包含具有外键并将在单一操作里加载的 CMP 字段和 CMR 字段的名字(如 "
"Organization-Gangster 示例里的 <literal>Gangster</literal>)。下面是一个配置"
-"示例:"
+"示例: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1335
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -5654,7 +5573,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1336
#, no-c-format
-#, fuzzy
msgid ""
"In this example, two load groups are declared: <literal>basic</literal> and "
"<literal>contact info</literal>. Note that the load groups do not need to be "
@@ -5667,19 +5585,17 @@
"<literal>contact info</literal>。请注意,加载组并不需要相互排斥。例如,这两个"
"加载组都可以包含 <literal>nickName</literal> 字段。除了所声明的加载组,JBoss "
"还自动地添加一个名为 <literal>*</literal> 的组,它包含每个带有 entity 里的外"
-"键的 CMP 字段和 CMR 字段。"
+"键的 CMP 字段和 CMR 字段。 "
#. Tag: title
#: The_CMP_Engine.xml:1342
#, no-c-format
-#, fuzzy
msgid "Read-ahead"
msgstr "Read-ahead"
#. Tag: para
#: The_CMP_Engine.xml:1343
#, no-c-format
-#, fuzzy
msgid ""
"Optimized loading in JBoss is called read-ahead. This refers to the "
"technique of reading the row for an entity being loaded, as well as the next "
@@ -5698,31 +5614,28 @@
"前面章节所提及的加载问题。在预读期间加载的额外数据不会马上和内存里的 entity "
"对象相关联,因为 JBoss 里的 entity 知道实际被访问时才会实例化。相反,它会存储"
"在预加载的缓存里,而知道事务结束时才会载入到 entity 里。下面的章节描述了预读"
-"策略。"
+"策略。 "
#. Tag: title
#: The_CMP_Engine.xml:1347
#, no-c-format
-#, fuzzy
msgid "on-find"
msgstr "on-find"
#. Tag: para
#: The_CMP_Engine.xml:1348
#, no-c-format
-#, fuzzy
msgid ""
"The <literal>on-find</literal> strategy reads additional columns when the "
"query is invoked. If the query is <literal>on-find</literal> optimized, "
"JBoss will execute the following query when the query is executed."
msgstr ""
"<literal>on-find</literal> 策略在查询被调用时读取列。如果这个查询是经过 "
-"<literal>on-find</literal> 优化的,JBoss 将执行下面的查询。"
+"<literal>on-find</literal> 优化的,JBoss 将执行下面的查询。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1351
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_g.id, t0_g.name, t0_g.nick_name, t0_g.badness \n"
" FROM gangster t0_g\n"
@@ -5735,7 +5648,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1352
#, no-c-format
-#, fuzzy
msgid ""
"All of the required data would be in the preload cache, so no additional "
"queries would need to be executed while iterating through the query results. "
@@ -5745,19 +5657,17 @@
msgstr ""
"所有需要的数据都存放在预加载的缓存里,所以在迭代查询结果时不需要执行额外的查"
"询。这种策略对于返回少量数据的查询来说时有效的,但是如果把大量的查询结果放入"
-"内存就非常低效了。下面的表展示了这个查询的执行:"
+"内存就非常低效了。下面的表展示了这个查询的执行: "
#. Tag: title
#: The_CMP_Engine.xml:1356
#, no-c-format
-#, fuzzy
msgid "on-find Optimized Query Execution"
-msgstr "经过 on-find 优化的查询结果"
+msgstr "经过 on-find 优化的查询结果 "
#. Tag: para
#: The_CMP_Engine.xml:1544
#, no-c-format
-#, fuzzy
msgid ""
"The <literal>read-ahead</literal> strategy and <literal>load-group</literal> "
"for a query is defined in the <literal>query</literal> element. If a "
@@ -5770,12 +5680,11 @@
"<literal>query</literal> 元素里进行定义。如果 <literal>read-ahead</literal> "
"策略不在 <literal>query</literal> 里声明,<literal>entity</literal> 元素或 "
"<literal>defaults</literal> 元素里声明的策略将被使用。下面是 <literal>on-"
-"find</literal> 的配置:"
+"find</literal> 的配置: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1547
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -5830,7 +5739,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1548
#, no-c-format
-#, fuzzy
msgid ""
"One problem with the <literal>on-find</literal> strategy is that it must "
"load additional data for every entity selected. Commonly in web applications "
@@ -5843,19 +5751,17 @@
"<literal>on-find</literal> 策略存在的一个问题时它必须为每个选择的 entity 载入"
"额外的数据。在 web 程序里,页面上通常会显示固定数量的结果。既然预加载的数据只"
"在事务期间有效,而事务仅仅限于单个的 web HTTP 会话,那么大多数的预加载数据都"
-"不会被用到。下节讨论的 <literal>on-load</literal> 策略就不会有这个问题。"
+"不会被用到。下节讨论的 <literal>on-load</literal> 策略就不会有这个问题。 "
#. Tag: title
#: The_CMP_Engine.xml:1552
#, no-c-format
-#, fuzzy
msgid "Left join read ahead"
msgstr "Left join read ahead"
#. Tag: para
#: The_CMP_Engine.xml:1553
#, no-c-format
-#, fuzzy
msgid ""
"Left join read ahead is an enhanced <literal>on-find</literal><literal>read-"
"ahead</literal> strategy. It allows you to preload in one SQL query not only "
@@ -5872,49 +5778,44 @@
"可以通过 CMR 导航从基础实例引用的相关实例。CMR 导航的深度没有限制。在导航和关"
"系类型映射里使用的 CMR 字段的表间关系(cardinality)也没有限制,也就是说,外"
"键和关系表映射风格都被支持。让我们来看看一些例子。下面是 Entity 和关系的声"
-"明。"
+"明。 "
#. Tag: title
#: The_CMP_Engine.xml:1559
#, no-c-format
-#, fuzzy
msgid "D#findByPrimaryKey"
msgstr "D#findByPrimaryKey"
#. Tag: para
#: The_CMP_Engine.xml:1560
#, no-c-format
-#, fuzzy
msgid ""
"Suppose we have an entity <literal>D</literal>. A typical SQL query "
"generated for the <literal>findByPrimaryKey</literal> would look like this:"
msgstr ""
"假设我们有一个名为 <literal>D</literal> 的 entity。为 "
-"<literal>findByPrimaryKey</literal> 生成的典型的 SQL 查询将类似于:"
+"<literal>findByPrimaryKey</literal> 生成的典型的 SQL 查询将类似于: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1563
#, no-c-format
-#, fuzzy
msgid "SELECT t0_D.id, t0_D.name FROM D t0_D WHERE t0_D.id=?"
msgstr "SELECT t0_D.id, t0_D.name FROM D t0_D WHERE t0_D.id=?"
#. Tag: para
#: The_CMP_Engine.xml:1564
#, no-c-format
-#, fuzzy
msgid ""
"Suppose that while executing <literal>findByPrimaryKey</literal> we also "
"want to preload two collection-valued CMR fields <literal>bs</literal> and "
"<literal>cs</literal>."
msgstr ""
"假设当执行 <literal>findByPrimaryKey</literal> 时,我们也想要预加载两个值为集"
-"合的 CMR 字段 <literal>bs</literal> 和 <literal>cs</literal>。"
+"合的 CMR 字段 <literal>bs</literal> 和 <literal>cs</literal>。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1567
#, no-c-format
-#, fuzzy
msgid ""
"<query>\n"
" <query-method>\n"
@@ -5955,16 +5856,14 @@
#. Tag: para
#: The_CMP_Engine.xml:1568
#, no-c-format
-#, fuzzy
msgid ""
"The <literal>left-join</literal> declares the relations to be eager loaded. "
"The generated SQL would look like this:"
-msgstr "<literal>left-join</literal> 声明要加载的关系。生成的 SQL 将类似于:"
+msgstr "<literal>left-join</literal> 声明要加载的关系。生成的 SQL 将类似于: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1571
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_D.id, t0_D.name,\n"
" t1_D_bs.id, t1_D_bs.name,\n"
@@ -5985,7 +5884,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1572
#, no-c-format
-#, fuzzy
msgid ""
"For the <literal>D</literal> with the specific id we preload all its related "
"<literal>B</literal>'s and <literal>C</literal>'s and can access "
@@ -5993,49 +5891,44 @@
msgstr ""
"对于带有特定 ID 的 <literal>D</literal>,我们预加载所有相关的 <literal>B</"
"literal> 和 <literal>C</literal>,然后我们可以访问那些从预读缓存而不是数据库"
-"里加载的实例。"
+"里加载的实例。 "
#. Tag: title
#: The_CMP_Engine.xml:1578
#, no-c-format
-#, fuzzy
msgid "D#findAll"
msgstr "D#findAll"
#. Tag: para
#: The_CMP_Engine.xml:1579
#, no-c-format
-#, fuzzy
msgid ""
"In the same way, we could optimize the <literal>findAll</literal> method on "
"<literal>D</literal> selects all the <literal>D</literal>'s. A normal "
"findAll query would look like this:"
msgstr ""
"以相同的方式,我们可以优化 <literal>D</literal> 的 <literal>findAll</"
-"literal> 方法,选择所有的 <literal>D</literal>。普通的 findAll 查询类似于:"
+"literal> 方法,选择所有的 <literal>D</literal>。普通的 findAll 查询类似于: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1582
#, no-c-format
-#, fuzzy
msgid "SELECT DISTINCT t0_o.id, t0_o.name FROM D t0_o ORDER BY t0_o.id DESC"
msgstr "SELECT DISTINCT t0_o.id, t0_o.name FROM D t0_o ORDER BY t0_o.id DESC"
#. Tag: para
#: The_CMP_Engine.xml:1583
#, no-c-format
-#, fuzzy
msgid ""
"To preload the relations, we simply need to add the <literal>left-join</"
"literal> elements to the query."
msgstr ""
"为了预加载关系,我们只需简单地把 <literal>left-join</literal> 元素添加到这个"
-"查询里。"
+"查询里。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1586
#, no-c-format
-#, fuzzy
msgid ""
"<query>\n"
" <query-method>\n"
@@ -6070,14 +5963,12 @@
#. Tag: para
#: The_CMP_Engine.xml:1587
#, no-c-format
-#, fuzzy
msgid "And here is the generated SQL:"
-msgstr "下面是生成的 SQL:"
+msgstr "下面是生成的 SQL: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1590
#, no-c-format
-#, fuzzy
msgid ""
"SELECT DISTINCT t0_o.id, t0_o.name,\n"
" t1_o_bs.id, t1_o_bs.name,\n"
@@ -6097,47 +5988,44 @@
#. Tag: para
#: The_CMP_Engine.xml:1591
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Now the simple <literal>findAll</literal> query now preloads the related "
"<literal>B</literal> and <literal>C</literal> objects for each <literal>D</"
"literal> object."
msgstr ""
"现在,简单的 <literal>findAll</literal> 查询为每个 <literal>D</literal> 对象"
-"预加载了相关的 <literal>B</literal> 和 <literal>C</literal> 对象。"
+"预加载了相关的 <literal>B</literal> 和 <literal>C</literal> 对象。 "
#. Tag: title
#: The_CMP_Engine.xml:1597
#, no-c-format
-#, fuzzy
msgid "A#findAll"
msgstr "A#findAll"
#. Tag: para
#: The_CMP_Engine.xml:1598
#, no-c-format
-#, fuzzy
msgid ""
"Now let's look at a more complex configuration. Here we want to preload "
"instance <literal>A</literal> along with several relations."
msgstr ""
"现在,让我们来看一个更为复杂的配置。在这里我们想预加载实例 <literal>A</"
-"literal> 以及几个关系。"
+"literal> 以及几个关系。 "
#. Tag: para
#: The_CMP_Engine.xml:1603
#, no-c-format
-#, fuzzy
msgid ""
"its parent (self-relation) reached from <literal>A</literal> with CMR field "
"<literal>parent</literal>"
msgstr ""
"通过 CMR 字段 <literal>parent</literal> 从 <literal>A</literal> 连接的父关系"
-"(自有关系)。"
+"(自有关系)。 "
#. Tag: para
#: The_CMP_Engine.xml:1608
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"the <literal>B</literal> reached from <literal>A</literal> with CMR field "
"<literal>b</literal>, and the related <literal>C</literal> reached from "
@@ -6145,12 +6033,11 @@
msgstr ""
"用 CMR 字段 <literal>b</literal> 从 <literal>A</literal> 到达的 <literal>B</"
"literal>,以及相关的用 CMR 字段 <literal>c</literal> 到达的 <literal>C</"
-"literal>。"
+"literal>。 "
#. Tag: para
#: The_CMP_Engine.xml:1613
#, no-c-format
-#, fuzzy
msgid ""
"<literal>B</literal> reached from <literal>A</literal> but this time with "
"CMR field <literal>b2</literal> and related to it <literal>C</literal> "
@@ -6158,33 +6045,29 @@
msgstr ""
"从 <literal>A</literal> 到达的 <literal>B</literal>,但这次使用 CMR 字段 "
"<literal>b2</literal> 且将其关联至从 B 用 CMR 字段 c 到达的 <literal>C</"
-"literal>。"
+"literal>。 "
#. Tag: para
#: The_CMP_Engine.xml:1618
#, no-c-format
-#, fuzzy
msgid "For reference, the standard query would be:"
-msgstr "作为参考,标准的查询将是:"
+msgstr "作为参考,标准的查询将是: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1621
#, no-c-format
-#, fuzzy
msgid "SELECT t0_o.id, t0_o.name FROM A t0_o ORDER BY t0_o.id DESC FOR UPDATE"
msgstr "SELECT t0_o.id, t0_o.name FROM A t0_o ORDER BY t0_o.id DESC FOR UPDATE"
#. Tag: para
#: The_CMP_Engine.xml:1622
#, no-c-format
-#, fuzzy
msgid "The following metadata describes our preloading plan."
-msgstr "下面的元数据描述了我们的预加载计划。"
+msgstr "下面的元数据描述了我们的预加载计划。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1625
#, no-c-format
-#, fuzzy
msgid ""
"<query>\n"
" <query-method>\n"
@@ -6229,14 +6112,12 @@
#. Tag: para
#: The_CMP_Engine.xml:1626
#, no-c-format
-#, fuzzy
msgid "The SQL query generated would be:"
-msgstr "生成的 SQL 将是:"
+msgstr "生成的 SQL 将是: "
#. Tag: programlisting
#: The_CMP_Engine.xml:1629
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_o.id, t0_o.name,\n"
" t1_o_parent.id, t1_o_parent.name,\n"
@@ -6269,25 +6150,22 @@
#. Tag: para
#: The_CMP_Engine.xml:1630
#, no-c-format
-#, fuzzy
msgid ""
"With this configuration, you can navigate CMRs from any found instance of "
"<literal>A</literal> without an additional database load."
msgstr ""
"使用这个配置,你可以从任何找到的 <literal>A</literal> 实例导航至 CMR 而不需要"
-"加载其他的数据库。"
+"加载其他的数据库。 "
#. Tag: title
#: The_CMP_Engine.xml:1636
#, no-c-format
-#, fuzzy
msgid "A#findMeParentGrandParent"
msgstr "A#findMeParentGrandParent"
#. Tag: para
#: The_CMP_Engine.xml:1637
#, no-c-format
-#, fuzzy
msgid ""
"Here is another example of self-relation. Suppose, we want to write a method "
"that would preload an instance, its parent, grand-parent and its grand-grand-"
@@ -6296,12 +6174,11 @@
msgstr ""
"这是另外一个自有关系(self-relation)的例子。假设我们想编写一个方法,它在查询"
"里预加载一个实例、其 parent、 grand-parent 和 grand-grand-parent。为了实现这"
-"一点,我们将使用嵌套的 <literal>left-join</literal> 声明。"
+"一点,我们将使用嵌套的 <literal>left-join</literal> 声明。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1640
#, no-c-format
-#, fuzzy
msgid ""
"<query>\n"
" <query-method>\n"
@@ -6352,7 +6229,6 @@
#. Tag: programlisting
#: The_CMP_Engine.xml:1644
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B_FK, t0_o.B2_FK, t0_o."
"PARENT,\n"
@@ -6383,14 +6259,12 @@
#. Tag: para
#: The_CMP_Engine.xml:1645
#, no-c-format
-#, fuzzy
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
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B2_FK, t0_o.PARENT FOR "
"UPDATE"
@@ -6401,14 +6275,12 @@
#. Tag: title
#: The_CMP_Engine.xml:1654
#, no-c-format
-#, fuzzy
msgid "on-load"
msgstr "on-load"
#. Tag: para
#: The_CMP_Engine.xml:1655
#, no-c-format
-#, fuzzy
msgid ""
"The <literal>on-load</literal> strategy block-loads additional data for "
"several entities when an entity is loaded, starting with the requested "
@@ -6424,23 +6296,22 @@
"<literal>on-load</literal> 策略在某个 entity 被加载时为几个 entity 加载其他数据块,按顺序从被请求的 "
"entity 开始,直到所选择的其他几个 entity。当查询被执行时,JBoss 把找到的 entity 的顺序保存在列表缓存里。之后,当其中一个 "
"entity 被加载时,JBoss 使用这个列表来决定加载的 entity 块。该 entity 的 <literal>list-cachemax<"
-"/literal> 元素指定存储在缓存里的列表的个数。这个策略也用于 <literal>on-find</literal> 策略不加载的有问题的数据。"
+"/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 ""
"和 <literal>on-find</literal> 策略一样,<literal>on-load</literal> 也在 <literal>"
-"read-ahead</literal> 元素里声明。下面是一个 <literal>on-load</literal> 配置的例子。"
+"read-ahead</literal> 元素里声明。下面是一个 <literal>on-load</literal> 配置的例子。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1661
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -6495,14 +6366,12 @@
#. Tag: para
#: The_CMP_Engine.xml:1662
#, no-c-format
-#, fuzzy
msgid "With this strategy, the query for the finder method in remains unchanged."
-msgstr "根据这个策略,使用 finder 方法的查询仍维持不变。"
+msgstr "根据这个策略,使用 finder 方法的查询仍维持不变。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1665
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_g.id\n"
" FROM gangster t0_g\n"
@@ -6515,7 +6384,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1666
#, no-c-format
-#, fuzzy
msgid ""
"However, the data will be loaded differently as we iterate through the "
"result set. For a page size of four, JBoss will only need to execute the "
@@ -6524,12 +6392,11 @@
"entities:"
msgstr ""
"然而,在我们迭代结果集时数据的加载会有所不同。对于页面大小为 4 的结果集,JBoss 将只需要执行下面的两个查询来加载 <literal>name<"
-"/literal>、<literal>nickName</literal> 和 <literal>badness</literal> 字段。"
+"/literal>、<literal>nickName</literal> 和 <literal>badness</literal> 字段。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1669
#, no-c-format
-#, fuzzy
msgid ""
"SELECT id, name, nick_name, badness\n"
" FROM gangster\n"
@@ -6548,28 +6415,24 @@
#. Tag: para
#: The_CMP_Engine.xml:1670
#, no-c-format
-#, fuzzy
msgid "The following table shows the execution of these queries:"
-msgstr "下面的表展示了这些查询的执行情况:"
+msgstr "下面的表展示了这些查询的执行情况: "
#. Tag: title
#: The_CMP_Engine.xml:1674
#, no-c-format
-#, fuzzy
msgid "on-load Optimized Query Execution"
-msgstr "执行用 on-load 策略优化的查询"
+msgstr "执行用 on-load 策略优化的查询 "
#. Tag: title
#: The_CMP_Engine.xml:1865
#, no-c-format
-#, fuzzy
msgid "none"
-msgstr "none 策略"
+msgstr "none 策略 "
#. Tag: para
#: The_CMP_Engine.xml:1866
#, no-c-format
-#, fuzzy
msgid ""
"The <literal>none</literal> strategy is really an anti-strategy. This "
"strategy causes the system to fall back to the default lazy-load code, and "
@@ -6583,11 +6446,11 @@
"<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 策略的例子。"
+"元素或 <literal>eager-load-group</literal>,它将被忽略。下面是一个声明 none 策略的例子。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1869
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -6637,14 +6500,13 @@
#. 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
#, no-c-format
-#, fuzzy
msgid ""
"In the previous section several steps use the phrase \"when the entity is "
"loaded.\" This was intentionally left vague because the commit option "
@@ -6653,19 +6515,17 @@
"and the loading processes."
msgstr ""
"在前一节里,有几个步骤使用了短语 \"when the entity is loaded\"。这种模糊是故意留下的,因为为这个 entity "
-"指定的提交选项和事务的当前状态决定了 entity 的加载时机。下面的内容将描述提交选项和加载过程。"
+"指定的提交选项和事务的当前状态决定了 entity 的加载时机。下面的内容将描述提交选项和加载过程。 "
#. Tag: title
#: The_CMP_Engine.xml:1882
#, no-c-format
-#, fuzzy
msgid "Commit Options"
-msgstr "提交选项"
+msgstr "提交选项 "
#. Tag: para
#: The_CMP_Engine.xml:1883
#, no-c-format
-#, fuzzy
msgid ""
"Central to the loading process are the commit options, which control when "
"the data for an entity expires. JBoss supports four commit options "
@@ -6676,12 +6536,11 @@
msgstr ""
"加载过程的中心是提交选项(commit option),它控制 entity 的数据的过期时间。JBoss 支持 4 种提交选项 <literal>A<"
"/literal>、<literal>B</literal>、<literal>C</literal> 和 <literal>D</literal>"
-"。EJB 规格里描述了前面 3 种,最后一个是 JBoss 所特有的。下面是对每个提交选项的详细描述:"
+"。EJB 规格里描述了前面 3 种,最后一个是 JBoss 所特有的。下面是对每个提交选项的详细描述: "
#. Tag: para
#: The_CMP_Engine.xml:1888
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">A</emphasis>: JBoss assumes it is the sole user of "
"the database; therefore, JBoss can cache the current value of an entity "
@@ -6693,12 +6552,11 @@
msgstr ""
"<emphasis role=\"bold\">A</emphasis>:JBoss 假设它是数据库的唯一用户;因此,JBoss 可以缓存事务间的 "
"entity 的当前值,这能够提升性能。利用这种假设,JBoss 管理的数据都不能在 JBoss 之外进行修改。例如,在另外一个程序里修改数据或直接使用 "
-"JDBC(即使在 JBoss 内部)都将导致不一致的数据库状态。"
+"JDBC(即使在 JBoss 内部)都将导致不一致的数据库状态。 "
#. Tag: para
#: The_CMP_Engine.xml:1893
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">B</emphasis>: JBoss assumes that there is more than "
"one user of the database but keeps the context information about entities "
@@ -6706,32 +6564,30 @@
"loading of the entity. This is the default commit option."
msgstr ""
"<emphasis role=\"bold\">B</emphasis>: JBoss 假设有多个用户访问数据库,但也保留事务间的 entity "
-"的上下文信息。这些信息被用来优化 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\">C</emphasis>: 在事务结束时,JBoss 丢弃所有 entity 的上下文的信息。"
+msgstr "<emphasis role=\"bold\">C</emphasis>: 在事务结束时,JBoss 丢弃所有 entity 的上下文的信息。 "
#. Tag: para
#: The_CMP_Engine.xml:1903
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">D</emphasis>: This is a JBoss specific commit "
"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> 相似,但其数据只在指定的时间内保持有效。"
+"/literal> 相似,但其数据只在指定的时间内保持有效。 "
#. Tag: para
#: The_CMP_Engine.xml:1908
#, no-c-format
-#, fuzzy
msgid ""
"The commit option is declared in the <literal>jboss.xml</literal> file. For "
"a detailed description of this file see <xref linkend=\"EJBs_on_JBoss\"/>. "
@@ -6740,19 +6596,17 @@
msgstr ""
"我们在 <literal>jboss.xml</literal> 文件里对提交选项进行声明。对于这个文件的详细描述,请参考 <xref "
"linkend=\"EJBs_on_JBoss\"/>。下面的例子把应用程序里的所有 entity bean 的提交选项修改为 <literal>A<"
-"/literal>:"
+"/literal>: "
#. Tag: title
#: The_CMP_Engine.xml:1911
#, no-c-format
-#, fuzzy
msgid "The jboss.xml Commit Option Declaration"
-msgstr "在 jboss.xml 里声明提交选项"
+msgstr "在 jboss.xml 里声明提交选项 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1912
#, no-c-format
-#, fuzzy
msgid ""
"<jboss>\n"
" <container-configurations>\n"
@@ -6777,14 +6631,12 @@
#. Tag: title
#: The_CMP_Engine.xml:1917
#, no-c-format
-#, fuzzy
msgid "Eager-loading Process"
-msgstr "Eager 加载过程"
+msgstr "Eager 加载过程 "
#. Tag: para
#: The_CMP_Engine.xml:1918
#, no-c-format
-#, fuzzy
msgid ""
"When an entity is loaded, JBoss must determine the fields that need to be "
"loaded. By default, JBoss will use the <literal>eager-load-group</literal> "
@@ -6799,11 +6651,11 @@
"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>。"
+"eager-load-group</literal>。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1921
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -6848,17 +6700,15 @@
#. Tag: para
#: The_CMP_Engine.xml:1922
#, no-c-format
-#, fuzzy
msgid ""
"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 "当事务里的 entity 的某个方法第一次被调用时,Eager 加载过程被初始化。下面是对这个加载过程的详细描述:"
+msgstr "当事务里的 entity 的某个方法第一次被调用时,Eager 加载过程被初始化。下面是对这个加载过程的详细描述: "
#. Tag: para
#: The_CMP_Engine.xml:1927
#, no-c-format
-#, fuzzy
msgid ""
"If the entity context is still valid, no loading is necessary, and therefore "
"the loading process is done. The entity context will be valid when using "
@@ -6866,38 +6716,34 @@
"literal>, and the data has not timed out."
msgstr ""
"如果 entity 的上下文仍然有效,则无需进行加载,因此加载过程就结束了。在使用提交选项 <literal>A</literal> 或 <"
-"literal>D</literal> 且数据未超时时,entity 的上下文将保持有效。"
+"literal>D</literal> 且数据未超时时,entity 的上下文将保持有效。 "
#. Tag: para
#: The_CMP_Engine.xml:1932
#, no-c-format
-#, fuzzy
msgid ""
"Any residual data in the entity context is flushed. This assures that old "
"data does not bleed into the new load."
-msgstr "Entity 上下文里的任何驻留数据都将被清除。这确保了旧的数据不会混在新的加载过程里。"
+msgstr "Entity 上下文里的任何驻留数据都将被清除。这确保了旧的数据不会混在新的加载过程里。 "
#. Tag: para
#: The_CMP_Engine.xml:1937
#, no-c-format
-#, fuzzy
msgid ""
"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
-#, fuzzy
msgid "All data in the preload cache for this entity is loaded into the fields."
-msgstr "预加载缓存里这个 entity 的任何数据都将加载到这些字段里。"
+msgstr "预加载缓存里这个 entity 的任何数据都将加载到这些字段里。 "
#. Tag: para
#: The_CMP_Engine.xml:1947
#, no-c-format
-#, fuzzy
msgid ""
"JBoss determines the additional fields that still need to be loaded. "
"Normally the fields to load are determined by the eager-load group of the "
@@ -6908,12 +6754,11 @@
msgstr ""
"JBoss 决定仍需要被加载的其他字段。通常这些字段由 entity 的 eager-load group 所决定,但如果该 entity "
"通过查询或带有 <literal>on-find</literal> 或 <literal>on-load</literal> 预读策略的 CMR "
-"字段进行定位时,它们可以被覆盖。如果所有这些字段都已经加载,那么加载过程将跳至步骤 7。"
+"字段进行定位时,它们可以被覆盖。如果所有这些字段都已经加载,那么加载过程将跳至步骤 7。 "
#. Tag: para
#: The_CMP_Engine.xml:1952
#, no-c-format
-#, fuzzy
msgid ""
"A query is executed to select the necessary column. If this entity is using "
"the <literal>on-load</literal> strategy, a page of data is loaded as "
@@ -6923,24 +6768,23 @@
msgstr ""
"我们执行一个查询来选定所需的列。如果这个 entity 使用了 <literal>on-load</literal> 策略,那么如 <xref "
"linkend=\"Read_ahead-on_load\"/> 所提及的,一页数据将被加载。当前 entity 的数据存储在上下文里,而其他 "
-"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 "调用该 entity 的 <literal>ejbLoad</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 "Lazy 加载过程"
+msgstr "Lazy 加载过程 "
#. Tag: para
#: The_CMP_Engine.xml:1966
#, no-c-format
-#, fuzzy
msgid ""
"Lazy loading is the other half of eager loading. If a field is not eager "
"loaded, it must be lazy loaded. When an access to an unloaded field of a "
@@ -6951,12 +6795,11 @@
msgstr ""
"Lazy 加载时 eager 加载的另外一半。如果某个字段没有进行 eager 加载,那么它必须进行 lazy 加载。当访问某个 bean "
"的未加载字段时,JBoss 加载这个字段以及它所属的任何 <literal>lazy-load-group</literal> 里的字段。JBoss "
-"执行一系列 join 操作,然后删除任何已经加载的字段。下面是一个配置示例。"
+"执行一系列 join 操作,然后删除任何已经加载的字段。下面是一个配置示例。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:1969
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -7019,7 +6862,6 @@
#. Tag: para
#: The_CMP_Engine.xml:1970
#, no-c-format
-#, fuzzy
msgid ""
"When the bean provider calls <literal>getName()</literal> with this "
"configuration, JBoss loads <literal>name</literal>, <literal>nickName</"
@@ -7033,30 +6875,27 @@
"、 <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 加载过程的详细描述:"
+" 和 <literal>hangout</literal> 将被加载。下面是对 lazy 加载过程的详细描述: "
#. Tag: para
#: The_CMP_Engine.xml:1980
#, no-c-format
-#, fuzzy
msgid ""
"If the field value was loaded by the preload cache the lazy load process is "
"finished."
-msgstr "如果字段值通过预加载缓存加载,那么 lazy 加载过程就结束了。"
+msgstr "如果字段值通过预加载缓存加载,那么 lazy 加载过程就结束了。 "
#. Tag: para
#: The_CMP_Engine.xml:1985
#, no-c-format
-#, fuzzy
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 "JBoss 找到所有包含这个字段的 lazy 加载组,执行一系列 join 操作,并删除已经加载的任何字段。"
+msgstr "JBoss 找到所有包含这个字段的 lazy 加载组,执行一系列 join 操作,并删除已经加载的任何字段。 "
#. Tag: para
#: The_CMP_Engine.xml:1990
#, no-c-format
-#, fuzzy
msgid ""
"A query is executed to select the necessary columns. As in the basic load "
"process, JBoss may load a block of entities. The data for the current entity "
@@ -7064,19 +6903,17 @@
"the preload cache."
msgstr ""
"我们执行一个查询来选择所需的列。和基本的加载过程一样,JBoss 可以加载一个 entity 块。当前 entity 的数据保存在上下文里,而其他 "
-"entity 的数据则存储在预加载缓存里。"
+"entity 的数据则存储在预加载缓存里。 "
#. Tag: title
#: The_CMP_Engine.xml:1996
#, no-c-format
-#, fuzzy
msgid "Relationships"
-msgstr "关系"
+msgstr "关系 "
#. Tag: para
#: The_CMP_Engine.xml:1997
#, no-c-format
-#, fuzzy
msgid ""
"Relationships are a special case in lazy loading because a CMR field is both "
"a field and query. As a field it can be <literal>on-load</literal> block "
@@ -7087,29 +6924,26 @@
msgstr ""
"关系是 lazy 加载里的一个特例,因为 CMR 字段既是字段也是查询。作为字段,它可以进行 <literal>on-load</literal> "
"块加载,这表示当前搜索的 entity 的值和下几个 entity 的 CMR 字段的值将被加载。而作为查询,相关的 entity 的字段值可以通过 <"
-"literal>on-find</literal> 进行预加载。"
+"literal>on-find</literal> 进行预加载。 "
#. Tag: para
#: The_CMP_Engine.xml:2000
#, no-c-format
-#, fuzzy
msgid ""
"Again, the easiest way to investigate the loading is to look at a usage "
"scenario. In this example, an HTML table is generated containing each "
"gangster and their hangout. The example code follows:"
-msgstr "熟悉加载过程最简单的方法是通过用例。在这个例子里,包含每个 gangster 及其 hangout 的 HTML 表将被生成。下面时示例代码:"
+msgstr "熟悉加载过程最简单的方法是通过用例。在这个例子里,包含每个 gangster 及其 hangout 的 HTML 表将被生成。下面是示例代码: "
#. Tag: title
#: The_CMP_Engine.xml:2003
#, no-c-format
-#, fuzzy
msgid "Relationship Lazy Loading Example Code"
-msgstr "关系的 Lazy 加载的示例代码"
+msgstr "关系的 Lazy 加载的示例代码 "
#. Tag: programlisting
#: The_CMP_Engine.xml:2004
#, no-c-format
-#, fuzzy
msgid ""
"public String createGangsterHangoutHtmlTable() \n"
" throws FinderException\n"
@@ -7172,7 +7006,6 @@
#. Tag: para
#: The_CMP_Engine.xml:2005
#, no-c-format
-#, fuzzy
msgid ""
"For this example, the configuration of the gangster's "
"<literal>findAll_onfind</literal> query is unchanged from the <literal>on-"
@@ -7181,19 +7014,17 @@
msgstr ""
"对于这个例子,<literal>on-find</literal> 部分没有修改 gangster 的 <literal>findAll_onfind<"
"/literal> 查询的配置。下面是 <literal>Location</literal> entity 和 <literal>"
-"Gangster-Hangout</literal> 关系的配置:"
+"Gangster-Hangout</literal> 关系的配置: "
#. Tag: title
#: The_CMP_Engine.xml:2008
#, no-c-format
-#, fuzzy
msgid "The jbosscmp-jdbc.xml Relationship Lazy Loading Configuration"
-msgstr "jbosscmp-jdbc.xml 里关于关系的 Lazy 加载的配置"
+msgstr "jbosscmp-jdbc.xml 里关于关系的 Lazy 加载的配置 "
#. Tag: programlisting
#: The_CMP_Engine.xml:2009
#, no-c-format
-#, fuzzy
msgid ""
"<jbosscmp-jdbc>\n"
" <enterprise-beans>\n"
@@ -7294,14 +7125,12 @@
#. Tag: para
#: The_CMP_Engine.xml:2010
#, no-c-format
-#, fuzzy
msgid "JBoss will execute the following query for the finder:"
-msgstr "JBoss 将为该 finder 执行下列查询:"
+msgstr "JBoss 将为该 finder 执行下列查询: "
#. Tag: programlisting
#: The_CMP_Engine.xml:2013
#, no-c-format
-#, fuzzy
msgid ""
"SELECT t0_g.id, t0_g.name, t0_g.nick_name, t0_g.badness\n"
" FROM gangster t0_g\n"
@@ -7314,19 +7143,17 @@
#. Tag: para
#: The_CMP_Engine.xml:2014
#, no-c-format
-#, fuzzy
msgid ""
"Then when the hangout is accessed, JBoss executes the following two queries "
"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> 字段。"
+"literal>state</literal> 和 <literal>zip</literal> 字段。 "
#. Tag: programlisting
#: The_CMP_Engine.xml:2017
#, no-c-format
-#, fuzzy
msgid ""
"SELECT gangster.id, gangster.hangout,\n"
" location.city, location.st, location.zip\n"
@@ -7357,27 +7184,24 @@
#. Tag: title
#: The_CMP_Engine.xml:2022
#, no-c-format
-#, fuzzy
msgid "on-find Optimized Relationship Query Execution"
-msgstr "执行通过 on-find 优化的关系查询"
+msgstr "执行通过 on-find 优化的关系查询 "
#. Tag: entry
#: The_CMP_Engine.xml:2053
-#, fuzzy, no-c-format
+#, no-c-format
msgid "city"
msgstr "city"
#. Tag: entry
#: The_CMP_Engine.xml:2056
#, no-c-format
-#, fuzzy
msgid "<entry>st</entry>"
msgstr "<entry>st</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2059
#, no-c-format
-#, fuzzy
msgid "<entry>zip</entry>"
msgstr "<entry>zip</entry>"
@@ -7385,7 +7209,6 @@
#: 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
-#, fuzzy
msgid "San Fran"
msgstr "San Fran"
@@ -7393,14 +7216,12 @@
#: 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
#, no-c-format
-#, fuzzy
msgid "<entry>CA</entry>"
msgstr "<entry>CA</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2090
#, no-c-format
-#, fuzzy
msgid "94108"
msgstr "94108"
@@ -7408,79 +7229,68 @@
#: The_CMP_Engine.xml:2119 The_CMP_Engine.xml:2148 The_CMP_Engine.xml:2177
#: The_CMP_Engine.xml:2206
#, no-c-format
-#, fuzzy
msgid "94133"
msgstr "94133"
#. Tag: entry
#: The_CMP_Engine.xml:2229
#, no-c-format
-#, fuzzy
msgid "New York"
msgstr "New York"
#. Tag: entry
#: The_CMP_Engine.xml:2232
#, no-c-format
-#, fuzzy
msgid "<entry>NY</entry>"
msgstr "<entry>NY</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2235
#, no-c-format
-#, fuzzy
msgid "10017"
msgstr "10017"
#. Tag: entry
#: The_CMP_Engine.xml:2258
#, no-c-format
-#, fuzzy
msgid "Chicago"
msgstr "Chicago"
#. Tag: entry
#: The_CMP_Engine.xml:2261
#, no-c-format
-#, fuzzy
msgid "<entry>IL</entry>"
msgstr "<entry>IL</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2264
#, no-c-format
-#, fuzzy
msgid "60661"
msgstr "60661"
#. Tag: entry
#: The_CMP_Engine.xml:2287
#, no-c-format
-#, fuzzy
msgid "Las Vegas"
msgstr "Las Vegas"
#. Tag: entry
#: The_CMP_Engine.xml:2290
#, no-c-format
-#, fuzzy
msgid "<entry>NV</entry>"
msgstr "<entry>NV</entry>"
#. Tag: entry
#: The_CMP_Engine.xml:2293
#, no-c-format
-#, fuzzy
msgid "89109"
msgstr "89109"
#. Tag: title
#: The_CMP_Engine.xml:2305
#, no-c-format
-#, fuzzy
msgid "Lazy loading result sets"
-msgstr "Lazy 加载的结果集"
+msgstr "Lazy 加载的结果集 "
#. Tag: para
#: The_CMP_Engine.xml:2306
More information about the jboss-cvs-commits
mailing list