[jboss-cvs] JBossAS SVN: r92467 - 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
Mon Aug 17 23:29:22 EDT 2009


Author: xhuang at jboss.com
Date: 2009-08-17 23:29:21 -0400 (Mon, 17 Aug 2009)
New Revision: 92467

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-18 02:59:07 UTC (rev 92466)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/The_CMP_Engine.po	2009-08-18 03:29:21 UTC (rev 92467)
@@ -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-08-10 16:20+1000\n"
+"PO-Revision-Date: 2009-08-18 13:27+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -26,19 +26,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:7
 #, no-c-format
-msgid ""
-"This chapter will explore the use of container managed persistence (CMP) in "
-"JBoss. We will assume a basic familiarity the EJB CMP model and focus on the "
-"operation of the JBoss CMP engine. Specifically, we will look at how to "
-"configure and optimize CMP applications on JBoss. For more introductory "
-"coverage of basic CMP concepts, we recommend <emphasis>Enterprise Java "
-"Beans, Fourth Edition</emphasis> (O&#39;Reilly 2004)."
-msgstr ""
-"本章将探索 JBoss 里 Container Managed Persistence (CMP) 的使用。我们将假定你"
-"基本熟悉 EJB CMP 模型而把重点放在 JBoss CMP 引擎的操作上。特别是我们将讨论如"
-"何配置和优化 JBoss 里运行的 CMP 应用程序。对于 CMP 概念的介绍,我们推荐你首先"
-"阅读<emphasis>《Enterprise Java Beans, Fourth Edition》</emphasis> (O&#39;"
-"Reilly 2004)。 "
+msgid "This chapter will explore the use of container managed persistence (CMP) in JBoss. We will assume a basic familiarity the EJB CMP model and focus on the operation of the JBoss CMP engine. Specifically, we will look at how to configure and optimize CMP applications on JBoss. For more introductory coverage of basic CMP concepts, we recommend <emphasis>Enterprise Java Beans, Fourth Edition</emphasis> (O&#39;Reilly 2004)."
+msgstr "本章将探索 JBoss 里 Container Managed Persistence (CMP) 的使用。我们将假定你基本熟悉 EJB CMP 模型而把重点放在 JBoss CMP 引擎的操作上。特别是我们将讨论如何配置和优化 JBoss 里运行的 CMP 应用程序。对于 CMP 概念的介绍,我们推荐你首先阅读<emphasis>《Enterprise Java Beans, Fourth Edition》</emphasis> (O&#39;Reilly 2004)。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:11
@@ -49,15 +38,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:12
 #, no-c-format
-msgid ""
-"This chapter is example-driven. We will work with the crime portal "
-"application which stores information about imaginary criminal organizations. "
-"The data model we will be working with is shown in <xref linkend="
-"\"Example_Code-The_crime_portal_example_classes\"/>."
-msgstr ""
-"本章内容将通过例程来推进。我们将研究存储虚构的犯罪组织信息的 crime portal 应"
-"用程序。<xref linkend=\"Example_Code-The_crime_portal_example_classes\"/> 展"
-"示了我们使用的数据模型。 "
+msgid "This chapter is example-driven. We will work with the crime portal application which stores information about imaginary criminal organizations. The data model we will be working with is shown in <xref linkend=\"Example_Code-The_crime_portal_example_classes\"/>."
+msgstr "本章内容将通过例程来推进。我们将研究存储虚构的犯罪组织信息的 crime portal 应用程序。<xref linkend=\"Example_Code-The_crime_portal_example_classes\"/> 展示了我们使用的数据模型。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:16
@@ -68,13 +50,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:23
 #, no-c-format
-msgid ""
-"The source code for the crime portal is available in the <literal>src/main/"
-"org/jboss/cmp2</literal> directory of the example code. To build the example "
-"code, run Ant as shown below"
-msgstr ""
-"crime portal 的源码位于 <literal>src/main/"
-"org/jboss/cmp2</literal> 目录下。如下所示,要构建示例代码,请运行 Ant。"
+msgid "The source code for the crime portal is available in the <literal>src/main/org/jboss/cmp2</literal> directory of the example code. To build the example code, run Ant as shown below"
+msgstr "crime portal 的源码位于 <literal>src/main/org/jboss/cmp2</literal> 目录下。如下所示,要构建示例代码,请运行 Ant。"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:26
@@ -85,64 +62,39 @@
 #. Tag: para
 #: The_CMP_Engine.xml:27
 #, no-c-format
-msgid ""
-"This command builds and deploys the application to the JBoss server. When "
-"you start yours JBoss server, or if it is already running, you should see "
-"the following deployment messages:"
+msgid "This command builds and deploys the application to the JBoss server. When you start yours JBoss server, or if it is already running, you should see the following deployment messages:"
 msgstr "这个命令构建并把应用程序部署在 JBoss 服务器里。当你启动 JBoss 服务器时,或者如果它已经在运行时,你应该可以看到下面的部署信息:"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:30
 #, no-c-format
 msgid ""
-"15:46:36,704 INFO  [OrganizationBean$Proxy] Creating organization Yakuza, "
-"Japanese Gangsters\n"
-"15:46:36,790 INFO  [OrganizationBean$Proxy] Creating organization Mafia, "
-"Italian Bad Guys\n"
-"15:46:36,797 INFO  [OrganizationBean$Proxy] Creating organization Triads, "
-"Kung Fu Movie Extras\n"
-"15:46:36,877 INFO  [GangsterBean$Proxy] Creating Gangster 0 &#39;"
-"Bodyguard&#39; Yojimbo\n"
-"15:46:37,003 INFO  [GangsterBean$Proxy] Creating Gangster 1 &#39;Master&#39; "
-"Takeshi\n"
-"15:46:37,021 INFO  [GangsterBean$Proxy] Creating Gangster 2 &#39;Four "
-"finger&#39; Yuriko\n"
-"15:46:37,040 INFO  [GangsterBean$Proxy] Creating Gangster 3 &#39;Killer&#39; "
-"Chow\n"
-"15:46:37,106 INFO  [GangsterBean$Proxy] Creating Gangster 4 &#39;"
-"Lightning&#39; Shogi\n"
-"15:46:37,118 INFO  [GangsterBean$Proxy] Creating Gangster 5 &#39;Pizza-"
-"Face&#39; Valentino\n"
-"15:46:37,133 INFO  [GangsterBean$Proxy] Creating Gangster 6 &#39;"
-"Toohless&#39; Toni\n"
-"15:46:37,208 INFO  [GangsterBean$Proxy] Creating Gangster 7 &#39;"
-"Godfather&#39; Corleone\n"
+"15:46:36,704 INFO  [OrganizationBean$Proxy] Creating organization Yakuza, Japanese Gangsters\n"
+"15:46:36,790 INFO  [OrganizationBean$Proxy] Creating organization Mafia, Italian Bad Guys\n"
+"15:46:36,797 INFO  [OrganizationBean$Proxy] Creating organization Triads, Kung Fu Movie Extras\n"
+"15:46:36,877 INFO  [GangsterBean$Proxy] Creating Gangster 0 &#39;Bodyguard&#39; Yojimbo\n"
+"15:46:37,003 INFO  [GangsterBean$Proxy] Creating Gangster 1 &#39;Master&#39; Takeshi\n"
+"15:46:37,021 INFO  [GangsterBean$Proxy] Creating Gangster 2 &#39;Four finger&#39; Yuriko\n"
+"15:46:37,040 INFO  [GangsterBean$Proxy] Creating Gangster 3 &#39;Killer&#39; Chow\n"
+"15:46:37,106 INFO  [GangsterBean$Proxy] Creating Gangster 4 &#39;Lightning&#39; Shogi\n"
+"15:46:37,118 INFO  [GangsterBean$Proxy] Creating Gangster 5 &#39;Pizza-Face&#39; Valentino\n"
+"15:46:37,133 INFO  [GangsterBean$Proxy] Creating Gangster 6 &#39;Toohless&#39; Toni\n"
+"15:46:37,208 INFO  [GangsterBean$Proxy] Creating Gangster 7 &#39;Godfather&#39; Corleone\n"
 "15:46:37,238 INFO  [JobBean$Proxy] Creating Job 10th Street Jeweler Heist\n"
 "15:46:37,247 INFO  [JobBean$Proxy] Creating Job The Greate Train Robbery\n"
 "15:46:37,257 INFO  [JobBean$Proxy] Creating Job Cheap Liquor Snatch and Grab"
 msgstr ""
-"15:46:36,704 INFO  [OrganizationBean$Proxy] Creating organization Yakuza, "
-"Japanese Gangsters\n"
-"15:46:36,790 INFO  [OrganizationBean$Proxy] Creating organization Mafia, "
-"Italian Bad Guys\n"
-"15:46:36,797 INFO  [OrganizationBean$Proxy] Creating organization Triads, "
-"Kung Fu Movie Extras\n"
-"15:46:36,877 INFO  [GangsterBean$Proxy] Creating Gangster 0 &#39;"
-"Bodyguard&#39; Yojimbo\n"
-"15:46:37,003 INFO  [GangsterBean$Proxy] Creating Gangster 1 &#39;Master&#39; "
-"Takeshi\n"
-"15:46:37,021 INFO  [GangsterBean$Proxy] Creating Gangster 2 &#39;Four "
-"finger&#39; Yuriko\n"
-"15:46:37,040 INFO  [GangsterBean$Proxy] Creating Gangster 3 &#39;Killer&#39; "
-"Chow\n"
-"15:46:37,106 INFO  [GangsterBean$Proxy] Creating Gangster 4 &#39;"
-"Lightning&#39; Shogi\n"
-"15:46:37,118 INFO  [GangsterBean$Proxy] Creating Gangster 5 &#39;Pizza-"
-"Face&#39; Valentino\n"
-"15:46:37,133 INFO  [GangsterBean$Proxy] Creating Gangster 6 &#39;"
-"Toohless&#39; Toni\n"
-"15:46:37,208 INFO  [GangsterBean$Proxy] Creating Gangster 7 &#39;"
-"Godfather&#39; Corleone\n"
+"15:46:36,704 INFO  [OrganizationBean$Proxy] Creating organization Yakuza, Japanese Gangsters\n"
+"15:46:36,790 INFO  [OrganizationBean$Proxy] Creating organization Mafia, Italian Bad Guys\n"
+"15:46:36,797 INFO  [OrganizationBean$Proxy] Creating organization Triads, Kung Fu Movie Extras\n"
+"15:46:36,877 INFO  [GangsterBean$Proxy] Creating Gangster 0 &#39;Bodyguard&#39; Yojimbo\n"
+"15:46:37,003 INFO  [GangsterBean$Proxy] Creating Gangster 1 &#39;Master&#39; Takeshi\n"
+"15:46:37,021 INFO  [GangsterBean$Proxy] Creating Gangster 2 &#39;Four finger&#39; Yuriko\n"
+"15:46:37,040 INFO  [GangsterBean$Proxy] Creating Gangster 3 &#39;Killer&#39; Chow\n"
+"15:46:37,106 INFO  [GangsterBean$Proxy] Creating Gangster 4 &#39;Lightning&#39; Shogi\n"
+"15:46:37,118 INFO  [GangsterBean$Proxy] Creating Gangster 5 &#39;Pizza-Face&#39; Valentino\n"
+"15:46:37,133 INFO  [GangsterBean$Proxy] Creating Gangster 6 &#39;Toohless&#39; Toni\n"
+"15:46:37,208 INFO  [GangsterBean$Proxy] Creating Gangster 7 &#39;Godfather&#39; Corleone\n"
 "15:46:37,238 INFO  [JobBean$Proxy] Creating Job 10th Street Jeweler Heist\n"
 "15:46:37,247 INFO  [JobBean$Proxy] Creating Job The Greate Train Robbery\n"
 "15:46:37,257 INFO  [JobBean$Proxy] Creating Job Cheap Liquor Snatch and Grab"
@@ -150,13 +102,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:31
 #, no-c-format
-msgid ""
-"Since the beans in the examples are configured to have their tables removed "
-"on undeployment, anytime you restart the JBoss server you need to rerun the "
-"config target to reload the example data and re-deploy the application."
-msgstr ""
-"既然本例里的 bean 都配置成在卸载时删除数据库表,每当你启动 JBoss 服务器时,你"
-"都需要重新运行 config 目标来加载示例数据并重部署应用程序。 "
+msgid "Since the beans in the examples are configured to have their tables removed on undeployment, anytime you restart the JBoss server you need to rerun the config target to reload the example data and re-deploy the application."
+msgstr "既然本例里的 bean 都配置成在卸载时删除数据库表,每当你启动 JBoss 服务器时,你都需要重新运行 config 目标来加载示例数据并重部署应用程序。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:35
@@ -167,14 +114,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:36
 #, no-c-format
-msgid ""
-"In order to get meaningful feedback from the chapter tests, you will want to "
-"increase the log level of the CMP subsystem before running running the test. "
-"To enable debug logging add the following category to your <literal>log4j."
-"xml</literal> file:"
-msgstr ""
-"要从单元测试里得到有意义的反馈,在运行测试前你需要提高 CMP 子系统的日志级别。"
-"要启用 debug 日志,请在 <literal>log4j.xml</literal> 文件里添加下列类别: "
+msgid "In order to get meaningful feedback from the chapter tests, you will want to increase the log level of the CMP subsystem before running running the test. To enable debug logging add the following category to your <literal>log4j.xml</literal> file:"
+msgstr "要从单元测试里得到有意义的反馈,在运行测试前你需要提高 CMP 子系统的日志级别。要启用 debug 日志,请在 <literal>log4j.xml</literal> 文件里添加下列类别: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:39
@@ -191,62 +132,42 @@
 #. Tag: para
 #: The_CMP_Engine.xml:40
 #, no-c-format
-msgid ""
-"In addition to this, it is necessary to decrease the threshold on the "
-"<literal>CONSOLE</literal> appender to allow debug level messages to be "
-"logged to the console. The following changes also need to be applied to the "
-"<literal>log4j.xml</literal> file."
-msgstr ""
-"除此以外,有必要降低 <literal>CONSOLE</literal> appender 的限制来允许 debug "
-"级别的信息输出到控制台上。<literal>log4j.xml</literal> 文件也需要进行下面的改"
-"动。 "
+msgid "In addition to this, it is necessary to decrease the threshold on the <literal>CONSOLE</literal> appender to allow debug level messages to be logged to the console. The following changes also need to be applied to the <literal>log4j.xml</literal> file."
+msgstr "除此以外,有必要降低 <literal>CONSOLE</literal> appender 的限制来允许 debug 级别的信息输出到控制台上。<literal>log4j.xml</literal> 文件也需要进行下面的改动。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:43
 #, no-c-format
 msgid ""
-"&lt;appender name=\"CONSOLE\" class=\"org.apache.log4j.ConsoleAppender"
-"\"&gt;\n"
-"    &lt;errorHandler class=\"org.jboss.logging.util.OnlyOnceErrorHandler\"/"
-"&gt;\n"
+"&lt;appender name=\"CONSOLE\" class=\"org.apache.log4j.ConsoleAppender\"&gt;\n"
+"    &lt;errorHandler class=\"org.jboss.logging.util.OnlyOnceErrorHandler\"/&gt;\n"
 "    &lt;param name=\"Target\"    value=\"System.out\"/&gt;\n"
-"    &lt;param name=\"Threshold\" value=\"<emphasis role=\"bold\">DEBUG</"
-"emphasis>\" /&gt;\n"
+"    &lt;param name=\"Threshold\" value=\"<emphasis role=\"bold\">DEBUG</emphasis>\" /&gt;\n"
 "\n"
 "    &lt;layout class=\"org.apache.log4j.PatternLayout\"&gt;\n"
-"        &lt;!-- The default pattern: Date Priority [Category] Message\\n --"
-"&gt;\n"
-"        &lt;param name=\"ConversionPattern\" value=\"%d{ABSOLUTE} %-5p [%c"
-"{1}] %m%n\"/&gt;\n"
+"        &lt;!-- The default pattern: Date Priority [Category] Message\\n"
+" --&gt;\n"
+"        &lt;param name=\"ConversionPattern\" value=\"%d{ABSOLUTE} %-5p [%c{1}] %m%n\"/&gt;\n"
 "    &lt;/layout&gt;\n"
 "&lt;/appender&gt;"
 msgstr ""
-"&lt;appender name=\"CONSOLE\" class=\"org.apache.log4j.ConsoleAppender"
-"\"&gt;\n"
-"    &lt;errorHandler class=\"org.jboss.logging.util.OnlyOnceErrorHandler\"/"
-"&gt;\n"
+"&lt;appender name=\"CONSOLE\" class=\"org.apache.log4j.ConsoleAppender\"&gt;\n"
+"    &lt;errorHandler class=\"org.jboss.logging.util.OnlyOnceErrorHandler\"/&gt;\n"
 "    &lt;param name=\"Target\"    value=\"System.out\"/&gt;\n"
-"    &lt;param name=\"Threshold\" value=\"<emphasis role=\"bold\">DEBUG</"
-"emphasis>\" /&gt;\n"
+"    &lt;param name=\"Threshold\" value=\"<emphasis role=\"bold\">DEBUG</emphasis>\" /&gt;\n"
 "\n"
 "    &lt;layout class=\"org.apache.log4j.PatternLayout\"&gt;\n"
-"        &lt;!-- The default pattern: Date Priority [Category] Message\\n --"
-"&gt;\n"
-"        &lt;param name=\"ConversionPattern\" value=\"%d{ABSOLUTE} %-5p [%c"
-"{1}] %m%n\"/&gt;\n"
+"        &lt;!-- The default pattern: Date Priority [Category] Message\\n"
+" --&gt;\n"
+"        &lt;param name=\"ConversionPattern\" value=\"%d{ABSOLUTE} %-5p [%c{1}] %m%n\"/&gt;\n"
 "    &lt;/layout&gt;\n"
 "&lt;/appender&gt;"
 
 #. Tag: para
 #: The_CMP_Engine.xml:44
 #, no-c-format
-msgid ""
-"To see the full workings of the CMP engine you would need to enable the "
-"custom <literal>TRACE</literal> level priority on the <literal>org.jboss.ejb."
-"plugins.cmp</literal> category as shown here:"
-msgstr ""
-"要看到 CMP 引擎的全部信息,如下所示,你需要启用 <literal>org.jboss.ejb."
-"plugins.cmp</literal> 类别上自定义的 <literal>TRACE</literal> 级别的优先级: "
+msgid "To see the full workings of the CMP engine you would need to enable the custom <literal>TRACE</literal> level priority on the <literal>org.jboss.ejb.plugins.cmp</literal> category as shown here:"
+msgstr "要看到 CMP 引擎的全部信息,如下所示,你需要启用 <literal>org.jboss.ejb.plugins.cmp</literal> 类别上自定义的 <literal>TRACE</literal> 级别的优先级: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:47
@@ -269,13 +190,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:52
 #, no-c-format
-msgid ""
-"The first test target illustrates a number of the customization features "
-"that will be discussed throughout this chapter. To run these tests execute "
-"the following ant target:"
-msgstr ""
-"第一个 test 目标演示了本章将讨论的大量自定义特征。要运行这些测试,请执行下面"
-"的 Ant 目标: "
+msgid "The first test target illustrates a number of the customization features that will be discussed throughout this chapter. To run these tests execute the following ant target:"
+msgstr "第一个 test 目标演示了本章将讨论的大量自定义特征。要运行这些测试,请执行下面的 Ant 目标: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:55
@@ -287,75 +203,47 @@
 #: The_CMP_Engine.xml:56
 #, no-c-format
 msgid ""
-"22:30:09,862 DEBUG [OrganizationEJB#findByPrimaryKey] Executing SQL: SELECT "
-"t0_OrganizationEJ\n"
+"22:30:09,862 DEBUG [OrganizationEJB#findByPrimaryKey] Executing SQL: SELECT t0_OrganizationEJ\n"
 "B.name FROM ORGANIZATION t0_OrganizationEJB WHERE t0_OrganizationEJB.name=?\n"
-"22:30:09,927 DEBUG [OrganizationEJB] Executing SQL: SELECT desc, the_boss "
-"FROM ORGANIZATION W\n"
+"22:30:09,927 DEBUG [OrganizationEJB] Executing SQL: SELECT desc, the_boss FROM ORGANIZATION W\n"
 "HERE (name=?)\n"
-"22:30:09,931 DEBUG [OrganizationEJB] load relation SQL: SELECT id FROM "
-"GANGSTER WHERE (organi\n"
+"22:30:09,931 DEBUG [OrganizationEJB] load relation SQL: SELECT id FROM GANGSTER WHERE (organi\n"
 "zation=?)\n"
-"22:30:09,947 DEBUG [StatelessSessionContainer] Useless invocation of remove"
-"() for stateless s\n"
+"22:30:09,947 DEBUG [StatelessSessionContainer] Useless invocation of remove() for stateless s\n"
 "ession bean\n"
-"22:30:10,086 DEBUG [GangsterEJB#findBadDudes_ejbql] Executing SQL: SELECT "
-"t0_g.id FROM GANGST\n"
+"22:30:10,086 DEBUG [GangsterEJB#findBadDudes_ejbql] Executing SQL: SELECT t0_g.id FROM GANGST\n"
 "ER t0_g WHERE (t0_g.badness &gt; ?)\n"
-"22:30:10,097 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT "
-"t0_GangsterEJB.id FRO\n"
+"22:30:10,097 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT t0_GangsterEJB.id FRO\n"
 "M GANGSTER t0_GangsterEJB WHERE t0_GangsterEJB.id=?\n"
-"22:30:10,102 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT "
-"t0_GangsterEJB.id FRO\n"
+"22:30:10,102 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT t0_GangsterEJB.id FRO\n"
 "M GANGSTER t0_GangsterEJB WHERE t0_GangsterEJB.id=?"
 msgstr ""
-"22:30:09,862 DEBUG [OrganizationEJB#findByPrimaryKey] Executing SQL: SELECT "
-"t0_OrganizationEJ\n"
+"22:30:09,862 DEBUG [OrganizationEJB#findByPrimaryKey] Executing SQL: SELECT t0_OrganizationEJ\n"
 "B.name FROM ORGANIZATION t0_OrganizationEJB WHERE t0_OrganizationEJB.name=?\n"
-"22:30:09,927 DEBUG [OrganizationEJB] Executing SQL: SELECT desc, the_boss "
-"FROM ORGANIZATION W\n"
+"22:30:09,927 DEBUG [OrganizationEJB] Executing SQL: SELECT desc, the_boss FROM ORGANIZATION W\n"
 "HERE (name=?)\n"
-"22:30:09,931 DEBUG [OrganizationEJB] load relation SQL: SELECT id FROM "
-"GANGSTER WHERE (organi\n"
+"22:30:09,931 DEBUG [OrganizationEJB] load relation SQL: SELECT id FROM GANGSTER WHERE (organi\n"
 "zation=?)\n"
-"22:30:09,947 DEBUG [StatelessSessionContainer] Useless invocation of remove"
-"() for stateless s\n"
+"22:30:09,947 DEBUG [StatelessSessionContainer] Useless invocation of remove() for stateless s\n"
 "ession bean\n"
-"22:30:10,086 DEBUG [GangsterEJB#findBadDudes_ejbql] Executing SQL: SELECT "
-"t0_g.id FROM GANGST\n"
+"22:30:10,086 DEBUG [GangsterEJB#findBadDudes_ejbql] Executing SQL: SELECT t0_g.id FROM GANGST\n"
 "ER t0_g WHERE (t0_g.badness &gt; ?)\n"
-"22:30:10,097 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT "
-"t0_GangsterEJB.id FRO\n"
+"22:30:10,097 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT t0_GangsterEJB.id FRO\n"
 "M GANGSTER t0_GangsterEJB WHERE t0_GangsterEJB.id=?\n"
-"22:30:10,102 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT "
-"t0_GangsterEJB.id FRO\n"
+"22:30:10,102 DEBUG [GangsterEJB#findByPrimaryKey] Executing SQL: SELECT t0_GangsterEJB.id FRO\n"
 "M GANGSTER t0_GangsterEJB WHERE t0_GangsterEJB.id=?"
 
 #. Tag: para
 #: The_CMP_Engine.xml:57
 #, no-c-format
-msgid ""
-"These tests exercise various finders, selectors and object to table mapping "
-"issues. We will refer to the tests throughout the chapter."
+msgid "These tests exercise various finders, selectors and object to table mapping issues. We will refer to the tests throughout the chapter."
 msgstr "这些测试涉及了不同的 finder、selector 以及对象和表映射相关的问题。在整本书里我们都将引用这些测试结果。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:60
 #, no-c-format
-msgid ""
-"The other main target runs a set of tests to demonstrate the optimized "
-"loading configurations presented in <xref linkend=\"The_CMP_Engine-"
-"Optimized_Loading\"/>. Now that the logging is setup correctly, the read-"
-"ahead tests will display useful information about the queries performed. "
-"Note that you do not have to restart the JBoss server for it to recognize "
-"the changes to the log4j.xml file, but it may take a minute or so. The "
-"following shows the actual execution of the readahead client:"
-msgstr ""
-"main 目标运行一系列的测试来演示 <xref linkend=\"The_CMP_Engine-"
-"Optimized_Loading\"/> 里讲述的优化载入配置。既然设置了正确的日志级别,read-"
-"ahead 将显示一些有用的所执行的查询的信息。请注意,虽然你并不需要重启 JBoss 服"
-"务器来应用对 log4j.xml 文件的修改,但这也需要一分钟左右的时间。下面显示了 "
-"readahead 客户端的实际执行情况: "
+msgid "The other main target runs a set of tests to demonstrate the optimized loading configurations presented in <xref linkend=\"The_CMP_Engine-Optimized_Loading\"/>. Now that the logging is setup correctly, the read-ahead tests will display useful information about the queries performed. Note that you do not have to restart the JBoss server for it to recognize the changes to the log4j.xml file, but it may take a minute or so. The following shows the actual execution of the readahead client:"
+msgstr "main 目标运行一系列的测试来演示 <xref linkend=\"The_CMP_Engine-Optimized_Loading\"/> 里讲述的优化载入配置。既然设置了正确的日志级别,read-ahead 将显示一些有用的所执行的查询的信息。请注意,虽然你并不需要重启 JBoss 服务器来应用对 log4j.xml 文件的修改,但这也需要一分钟左右的时间。下面显示了 readahead 客户端的实际执行情况: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:63
@@ -366,16 +254,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:64
 #, no-c-format
-msgid ""
-"When the readahead client is executed, all of the SQL queries executed "
-"during the test are displayed in the JBoss server console. The important "
-"items of note when analyzing the output are the number of queries executed, "
-"the columns selected, and the number of rows loaded. The following shows the "
-"read-ahead none portion of the JBoss server console output from readahead:"
-msgstr ""
-"当 readahead 客户端被执行时,测试期间执行的所有的 SQL 查询都显示在 JBoss 服务"
-"器控制台上。当分析输出时要注意的是执行的查询、选择的列以及加载的行的数量。下"
-"面显示的是 JBoss 服务器控制台输出的 read-ahead none 部分。 "
+msgid "When the readahead client is executed, all of the SQL queries executed during the test are displayed in the JBoss server console. The important items of note when analyzing the output are the number of queries executed, the columns selected, and the number of rows loaded. The following shows the read-ahead none portion of the JBoss server console output from readahead:"
+msgstr "当 readahead 客户端被执行时,测试期间执行的所有的 SQL 查询都显示在 JBoss 服务器控制台上。当分析输出时要注意的是执行的查询、选择的列以及加载的行的数量。下面显示的是 JBoss 服务器控制台输出的 read-ahead none 部分。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:67
@@ -385,32 +265,23 @@
 "########################################################\n"
 "### read-ahead none\n"
 "###\n"
-"22:44:31,582 DEBUG [GangsterEJB#findAll_none] Executing SQL: SELECT t0_g.id "
-"FROM GANGSTER t0_\n"
+"22:44:31,582 DEBUG [GangsterEJB#findAll_none] Executing SQL: SELECT t0_g.id FROM GANGSTER t0_\n"
 "g ORDER BY t0_g.id ASC\n"
-"22:44:31,604 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,604 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,615 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,615 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,622 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,622 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,628 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,628 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,635 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,635 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,644 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,644 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,649 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,649 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,658 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,658 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
 "22:44:31,670 INFO  [ReadAheadTest] \n"
 "###\n"
@@ -421,32 +292,23 @@
 "########################################################\n"
 "### read-ahead none\n"
 "###\n"
-"22:44:31,582 DEBUG [GangsterEJB#findAll_none] Executing SQL: SELECT t0_g.id "
-"FROM GANGSTER t0_\n"
+"22:44:31,582 DEBUG [GangsterEJB#findAll_none] Executing SQL: SELECT t0_g.id FROM GANGSTER t0_\n"
 "g ORDER BY t0_g.id ASC\n"
-"22:44:31,604 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,604 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,615 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,615 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,622 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,622 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,628 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,628 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,635 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,635 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,644 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,644 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,649 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,649 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
-"22:44:31,658 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, "
-"badness, organization\n"
+"22:44:31,658 DEBUG [GangsterEJB] Executing SQL: SELECT name, nick_name, badness, organization\n"
 ", hangout FROM GANGSTER WHERE (id=?)\n"
 "22:44:31,670 INFO  [ReadAheadTest] \n"
 "###\n"
@@ -456,9 +318,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:68
 #, no-c-format
-msgid ""
-"We will revisit this example and explore the output when we discuss the "
-"settings for optimized loading."
+msgid "We will revisit this example and explore the output when we discuss the settings for optimized loading."
 msgstr "在讨论优化加载的设置时,我们将再次使用这个示例并进一步探讨其输出。 "
 
 #. Tag: title
@@ -470,29 +330,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:77
 #, no-c-format
-msgid ""
-"The <literal>jbosscmp-jdbc.xml</literal> descriptor is used to control the "
-"behavior of the JBoss engine. This can be done globally through the "
-"<literal>conf/standardjbosscmp-jdbc.xml</literal> descriptor found in the "
-"server configuration file set, or per EJB JAR deployment via a <literal>META-"
-"INF/jbosscmp-jdbc.xml</literal> descriptor."
-msgstr ""
-"我们使用 <literal>jbosscmp-jdbc.xml</literal> 描述符来控制 JBoss 引擎的行为。"
-"这可以通过服务器配置文件集里的 <literal>conf/standardjbosscmp-jdbc.xml</"
-"literal> 描述符进行全局设置,或者通过 <literal>META-INF/jbosscmp-jdbc.xml</"
-"literal> 对每个 EJB JAR 部署进行设置。 "
+msgid "The <literal>jbosscmp-jdbc.xml</literal> descriptor is used to control the behavior of the JBoss engine. This can be done globally through the <literal>conf/standardjbosscmp-jdbc.xml</literal> descriptor found in the server configuration file set, or per EJB JAR deployment via a <literal>META-INF/jbosscmp-jdbc.xml</literal> descriptor."
+msgstr "我们使用 <literal>jbosscmp-jdbc.xml</literal> 描述符来控制 JBoss 引擎的行为。这可以通过服务器配置文件集里的 <literal>conf/standardjbosscmp-jdbc.xml</literal> 描述符进行全局设置,或者通过 <literal>META-INF/jbosscmp-jdbc.xml</literal> 对每个 EJB JAR 部署进行设置。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:80
 #, no-c-format
-msgid ""
-"The DTD for the <literal>jbosscmp-jdbc.xml</literal> descriptor can be found "
-"in <literal>JBOSS_DIST/docs/dtd/jbosscmp-jdbc_4_0.dtd</literal>. The public "
-"doctype for this DTD is:"
-msgstr ""
-"<literal>JBOSS_DIST/docs/dtd/jbosscmp-jdbc_4_0.dtd</literal> 定义了"
-"<literal>jbosscmp-jdbc.xml</literal> 描述符使用的 DTD。此 DTD 的 public "
-"doctype 是: "
+msgid "The DTD for the <literal>jbosscmp-jdbc.xml</literal> descriptor can be found in <literal>JBOSS_DIST/docs/dtd/jbosscmp-jdbc_4_0.dtd</literal>. The public doctype for this DTD is:"
+msgstr "<literal>JBOSS_DIST/docs/dtd/jbosscmp-jdbc_4_0.dtd</literal> 定义了<literal>jbosscmp-jdbc.xml</literal> 描述符使用的 DTD。此 DTD 的 public doctype 是: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:83
@@ -509,12 +354,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:84
 #, no-c-format
-msgid ""
-"The top level elements are shown in <xref linkend="
-"\"The_jbosscmp_jdbc_Structure-The_jbosscmp_jdbc_content_model.\"/>."
-msgstr ""
-"<xref linkend=\"The_jbosscmp_jdbc_Structure-The_jbosscmp_jdbc_content_model."
-"\"/> 展示了顶层的元素: "
+msgid "The top level elements are shown in <xref linkend=\"The_jbosscmp_jdbc_Structure-The_jbosscmp_jdbc_content_model.\"/>."
+msgstr "<xref linkend=\"The_jbosscmp_jdbc_Structure-The_jbosscmp_jdbc_content_model.\"/> 展示了顶层的元素: "
 
 #. Tag: title
 #: The_CMP_Engine.xml:88
@@ -525,123 +366,50 @@
 #. Tag: para
 #: The_CMP_Engine.xml:97
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">defaults</emphasis>: The defaults section allows for "
-"the specification of default behavior/settings for behavior that controls "
-"entity beans. Use of this section simplifies the amount of information "
-"needed for the common behaviors found in the entity beans section. See <xref "
-"linkend=\"The_CMP_Engine-Defaults\"/> for the details of the defaults "
-"content."
-msgstr ""
-"<emphasis role=\"bold\">defaults</emphasis>:defaults 部分允许对控制 Entity "
-"Bean 的行为的缺省行文/设置进行定义。这简化了 entity beans 部分里公用行为所需"
-"的信息。关于 defaults 内容的细节,请参考 <xref linkend=\"The_CMP_Engine-"
-"Defaults\"/>。 "
+msgid "<emphasis role=\"bold\">defaults</emphasis>: The defaults section allows for the specification of default behavior/settings for behavior that controls entity beans. Use of this section simplifies the amount of information needed for the common behaviors found in the entity beans section. See <xref linkend=\"The_CMP_Engine-Defaults\"/> for the details of the defaults content."
+msgstr "<emphasis role=\"bold\">defaults</emphasis>:defaults 部分允许对控制 Entity Bean 的行为的缺省行文/设置进行定义。这简化了 entity beans 部分里公用行为所需的信息。关于 defaults 内容的细节,请参考 <xref linkend=\"The_CMP_Engine-Defaults\"/>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:102
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">enterprise-beans</emphasis>: The <literal>enterprise-"
-"beans</literal> element allows for customization of entity beans defined in "
-"the <literal>ejb-jar.xml</literal><literal>enterprise-beans</literal> "
-"descriptor. This is described in detail in <xref linkend=\"The_CMP_Engine-"
-"Entity_Beans\"/>."
-msgstr ""
-"<emphasis role=\"bold\">enterprise-beans</emphasis>:<literal>enterprise-"
-"beans</literal> 元素允许自定义 <literal>ejb-jar.xml</"
-"literal><literal>enterprise-beans</literal> 描述符里定义的 entity bean。"
-"<xref linkend=\"The_CMP_Engine-Entity_Beans\"/> 里对它进行了详细描述。 "
+msgid "<emphasis role=\"bold\">enterprise-beans</emphasis>: The <literal>enterprise-beans</literal> element allows for customization of entity beans defined in the <literal>ejb-jar.xml</literal><literal>enterprise-beans</literal> descriptor. This is described in detail in <xref linkend=\"The_CMP_Engine-Entity_Beans\"/>."
+msgstr "<emphasis role=\"bold\">enterprise-beans</emphasis>:<literal>enterprise-beans</literal> 元素允许自定义 <literal>ejb-jar.xml</literal><literal>enterprise-beans</literal> 描述符里定义的 entity bean。<xref linkend=\"The_CMP_Engine-Entity_Beans\"/> 里对它进行了详细描述。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:107
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">relationships</emphasis>: The "
-"<literal>relationships</literal> element allows for the customization of "
-"tables and the loading behavior of entity relationships. This is described "
-"in detail in <xref linkend=\"The_CMP_Engine-Container_Managed_Relationships"
-"\"/>."
-msgstr ""
-"<emphasis role=\"bold\">relationships</emphasis>:<literal>relationships</"
-"literal> 元素允许对 entity 关系表和加载行为进行自定义。<xref linkend="
-"\"The_CMP_Engine-Container_Managed_Relationships\"/> 对它进行了详细描述。 "
+msgid "<emphasis role=\"bold\">relationships</emphasis>: The <literal>relationships</literal> element allows for the customization of tables and the loading behavior of entity relationships. This is described in detail in <xref linkend=\"The_CMP_Engine-Container_Managed_Relationships\"/>."
+msgstr "<emphasis role=\"bold\">relationships</emphasis>:<literal>relationships</literal> 元素允许对 entity 关系表和加载行为进行自定义。<xref linkend=\"The_CMP_Engine-Container_Managed_Relationships\"/> 对它进行了详细描述。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:112
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">dependent-value-classes</emphasis>: The "
-"<literal>dependent-value-classes</literal> element allows for the "
-"customization of the mapping of dependent value classes to tables. Dependent "
-"value classes are described in detail in <xref linkend=\"CMP_Fields-"
-"Dependent_Value_Classes_DVCs\"/> (DVCs)."
-msgstr ""
-"<emphasis role=\"bold\">dependent-value-classes</emphasis>:"
-"<literal>dependent-value-classes</literal> 元素允许对 dependent value 类和表"
-"之间的映射进行自定义。<xref linkend=\"CMP_Fields-Dependent_Value_Classes_DVCs"
-"\"/> 里对 Dependent value 类进行了详细描述。 "
+msgid "<emphasis role=\"bold\">dependent-value-classes</emphasis>: The <literal>dependent-value-classes</literal> element allows for the customization of the mapping of dependent value classes to tables. Dependent value classes are described in detail in <xref linkend=\"CMP_Fields-Dependent_Value_Classes_DVCs\"/> (DVCs)."
+msgstr "<emphasis role=\"bold\">dependent-value-classes</emphasis>:<literal>dependent-value-classes</literal> 元素允许对 dependent value 类和表之间的映射进行自定义。<xref linkend=\"CMP_Fields-Dependent_Value_Classes_DVCs\"/> 里对 Dependent value 类进行了详细描述。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:117
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">type-mappings</emphasis>: The <literal>type-"
-"mappings</literal> element defines the Java to SQL type mappings for a "
-"database, along with SQL templates, and function mappings. This is described "
-"in detail in <xref linkend=\"The_CMP_Engine-Datasource_Customization\"/>."
-msgstr ""
-"<emphasis role=\"bold\">type-mappings</emphasis>:<literal>type-mappings</"
-"literal> 元素定义了用于数据库的 Java 与 SQL 类型的映射关系、SQL 模板以及函数"
-"映射。<xref linkend=\"The_CMP_Engine-Datasource_Customization\"/> 里对它进行"
-"了详细描述。 "
+msgid "<emphasis role=\"bold\">type-mappings</emphasis>: The <literal>type-mappings</literal> element defines the Java to SQL type mappings for a database, along with SQL templates, and function mappings. This is described in detail in <xref linkend=\"The_CMP_Engine-Datasource_Customization\"/>."
+msgstr "<emphasis role=\"bold\">type-mappings</emphasis>:<literal>type-mappings</literal> 元素定义了用于数据库的 Java 与 SQL 类型的映射关系、SQL 模板以及函数映射。<xref linkend=\"The_CMP_Engine-Datasource_Customization\"/> 里对它进行了详细描述。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:122
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">entity-commands</emphasis>: The <literal>entity-"
-"commands</literal> element allows for the definition of the entity creation "
-"command instances that know how to create an entity instance in a persistent "
-"store. This is described in detail in <xref linkend=\"The_CMP_Engine-"
-"Entity_Commands_and_Primary_Key_Generation\"/>."
-msgstr ""
-"<emphasis role=\"bold\">entity-commands</emphasis>:<literal>entity-"
-"commands</literal> 元素定义负责在持久性存储里创建 Entity 实例的 entity "
-"creation command 实例。<xref linkend=\"The_CMP_Engine-"
-"Entity_Commands_and_Primary_Key_Generation\"/> 里对它进行了详细描述。 "
+msgid "<emphasis role=\"bold\">entity-commands</emphasis>: The <literal>entity-commands</literal> element allows for the definition of the entity creation command instances that know how to create an entity instance in a persistent store. This is described in detail in <xref linkend=\"The_CMP_Engine-Entity_Commands_and_Primary_Key_Generation\"/>."
+msgstr "<emphasis role=\"bold\">entity-commands</emphasis>:<literal>entity-commands</literal> 元素定义负责在持久性存储里创建 Entity 实例的 entity creation command 实例。<xref linkend=\"The_CMP_Engine-Entity_Commands_and_Primary_Key_Generation\"/> 里对它进行了详细描述。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:127
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">user-type-mappings</emphasis>: The <literal>user-"
-"type-mappings</literal> elements defines a mapping of a user types to a "
-"column using a mapper class. A mapper is like a mediator. When storing, it "
-"takes an instance of the user type and translates it to a column value. When "
-"loading, it takes a column value and translates it to an instance of the "
-"user type. Details of the user type mappings are described in <xref linkend="
-"\"Datasource_Customization-User_Type_Mappings\"/>."
-msgstr ""
-"<emphasis role=\"bold\">user-type-mappings</emphasis>:<literal>user-type-"
-"mappings</literal> 元素用 mapper 类定义了用户类型和列之间的映射。Mapper 类就"
-"像一个中介。进行存储时,它获取用户类型的实例并将其转换成 column 值。当进行加"
-"载时,它获取一个 Column 值并转换成用户类型的实例。<xref linkend="
-"\"Datasource_Customization-User_Type_Mappings\"/> 里对用户类型映射进行了详细"
-"描述。 "
+msgid "<emphasis role=\"bold\">user-type-mappings</emphasis>: The <literal>user-type-mappings</literal> elements defines a mapping of a user types to a column using a mapper class. A mapper is like a mediator. When storing, it takes an instance of the user type and translates it to a column value. When loading, it takes a column value and translates it to an instance of the user type. Details of the user type mappings are described in <xref linkend=\"Datasource_Customization-User_Type_Mappings\"/>."
+msgstr "<emphasis role=\"bold\">user-type-mappings</emphasis>:<literal>user-type-mappings</literal> 元素用 mapper 类定义了用户类型和列之间的映射。Mapper 类就像一个中介。进行存储时,它获取用户类型的实例并将其转换成 column 值。当进行加载时,它获取一个 Column 值并转换成用户类型的实例。<xref linkend=\"Datasource_Customization-User_Type_Mappings\"/> 里对用户类型映射进行了详细描述。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:132
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">reserved-words</emphasis>: The <literal>reserved-"
-"words</literal> element defines one or more reserved words that should be "
-"escaped when generating tables. Each reserved word is specified as the "
-"content of a <literal>word</literal> element."
-msgstr ""
-"<emphasis role=\"bold\">reserved-words</emphasis>:<literal>reserved-words</"
-"literal> 元素定义了产生表时不能使用的一个或多个保留字。每个保留字都通过  "
-"<literal>word</literal> 元素进行指定。 "
+msgid "<emphasis role=\"bold\">reserved-words</emphasis>: The <literal>reserved-words</literal> element defines one or more reserved words that should be escaped when generating tables. Each reserved word is specified as the content of a <literal>word</literal> element."
+msgstr "<emphasis role=\"bold\">reserved-words</emphasis>:<literal>reserved-words</literal> 元素定义了产生表时不能使用的一个或多个保留字。每个保留字都通过  <literal>word</literal> 元素进行指定。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:140
@@ -652,30 +420,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:141
 #, no-c-format
-msgid ""
-"We&#39;ll start our look at entity beans in JBoss by examining one of the "
-"CMP entity beans in the crime portal. We&#39;ll look at the gangster bean, "
-"which is implemented as local CMP entity bean. Although JBoss can provide "
-"remote entity beans with pass-by-reference semantics for calls in the same "
-"VM to get the performance benefit as from local entity beans, the use of "
-"local entity beans is strongly encouraged."
-msgstr ""
-"通过 crime portal 里的一个 CMP Entity Bean,我们将开始学习 JBoss 里的 entity "
-"bean。我们将讨论作为本地 CMP entity bean 实现的 gangster bean。虽然 JBoss 可"
-"以提供远程 entity bean,它在相同的 VM 里使用引用传递(pass-by-reference)模式"
-"来获取和本地 entity bean 一样的性能优化。但我们还是鼓励尽量使用本地 entity "
-"bean。 "
+msgid "We&#39;ll start our look at entity beans in JBoss by examining one of the CMP entity beans in the crime portal. We&#39;ll look at the gangster bean, which is implemented as local CMP entity bean. Although JBoss can provide remote entity beans with pass-by-reference semantics for calls in the same VM to get the performance benefit as from local entity beans, the use of local entity beans is strongly encouraged."
+msgstr "通过 crime portal 里的一个 CMP Entity Bean,我们将开始学习 JBoss 里的 entity bean。我们将讨论作为本地 CMP entity bean 实现的 gangster bean。虽然 JBoss 可以提供远程 entity bean,它在相同的 VM 里使用引用传递(pass-by-reference)模式来获取和本地 entity bean 一样的性能优化。但我们还是鼓励尽量使用本地 entity bean。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:144
 #, no-c-format
-msgid ""
-"We&#39;ll start with the required home interface. Since we&#39;re only "
-"concerned with the CMP fields at this point, we&#39;ll show only the methods "
-"dealing with the CMP fields."
-msgstr ""
-"我们将从必需的 home 接口开始。既然目前我们只关心 CMP 字段,我们将只显示和 "
-"CMP 字段相关的方法。 "
+msgid "We&#39;ll start with the required home interface. Since we&#39;re only concerned with the CMP fields at this point, we&#39;ll show only the methods dealing with the CMP fields."
+msgstr "我们将从必需的 home 接口开始。既然目前我们只关心 CMP 字段,我们将只显示和 CMP 字段相关的方法。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:147
@@ -704,9 +456,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:148
 #, no-c-format
-msgid ""
-"The local interface is what clients will use to talk. Again, it contains "
-"only the CMP field accessors."
+msgid "The local interface is what clients will use to talk. Again, it contains only the CMP field accessors."
 msgstr "客户用 local 接口来进行对话。它只包含 CMP 字段的 accessor。 "
 
 #. Tag: programlisting
@@ -746,12 +496,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:152
 #, no-c-format
-msgid ""
-"Finally, we have the actual gangster bean. Despite it&#39;s size, very "
-"little code is actually required. The bulk of the class is the create method."
-msgstr ""
-"最后,我们看到的实际的 gangster bean。它实际上只需要极少的代码。这个类的主要"
-"部分是 create 方法。 "
+msgid "Finally, we have the actual gangster bean. Despite it&#39;s size, very little code is actually required. The bulk of the class is the create method."
+msgstr "最后,我们看到的实际的 gangster bean。它实际上只需要极少的代码。这个类的主要部分是 create 方法。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:155
@@ -766,8 +512,7 @@
 "     public Integer ejbCreate(Integer id, String name, String nickName)\n"
 "         throws CreateException \n"
 "     {\n"
-"         log.info(\"Creating Gangster \" + id + \" &#39;\" + nickName + "
-"\"&#39; \"+ name);\n"
+"         log.info(\"Creating Gangster \" + id + \" &#39;\" + nickName + \"&#39; \"+ name);\n"
 "         setGangsterId(id);\n"
 "         setName(name);\n"
 "         setNickName(nickName);\n"
@@ -809,8 +554,7 @@
 "     public Integer ejbCreate(Integer id, String name, String nickName)\n"
 "         throws CreateException \n"
 "     {\n"
-"         log.info(\"Creating Gangster \" + id + \" &#39;\" + nickName + "
-"\"&#39; \"+ name);\n"
+"         log.info(\"Creating Gangster \" + id + \" &#39;\" + nickName + \"&#39; \"+ name);\n"
 "         setGangsterId(id);\n"
 "         setName(name);\n"
 "         setNickName(nickName);\n"
@@ -846,44 +590,33 @@
 #. Tag: para
 #: The_CMP_Engine.xml:156
 #, no-c-format
-msgid ""
-"The only thing missing now is the <literal>ejb-jar.xml</literal> deployment "
-"descriptor. Although the actual bean class is named <literal>GangsterBean</"
-"literal>, we&#39;ve called the entity <literal>GangsterEJB</literal>."
-msgstr ""
-"现在唯一缺少的是 <literal>ejb-jar.xml</literal> 部署描述符。虽然实际的 bean "
-"的类名是<literal>GangsterBean</literal>,我们将称其为 entity "
-"<literal>GangsterEJB</literal>。 "
+msgid "The only thing missing now is the <literal>ejb-jar.xml</literal> deployment descriptor. Although the actual bean class is named <literal>GangsterBean</literal>, we&#39;ve called the entity <literal>GangsterEJB</literal>."
+msgstr "现在唯一缺少的是 <literal>ejb-jar.xml</literal> 部署描述符。虽然实际的 bean 的类名是<literal>GangsterBean</literal>,我们将称其为 entity <literal>GangsterEJB</literal>。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:159
 #, no-c-format
 msgid ""
 "&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
-"&lt;ejb-jar xmlns=\"http://java.sun.com/xml/ns/\"Whats_new_in_JBoss_4-"
-"J2EE_Certification_and_Standards_Compliance\" version=\"2.1\"\n"
+"&lt;ejb-jar xmlns=\"http://java.sun.com/xml/ns/\"Whats_new_in_JBoss_4-J2EE_Certification_and_Standards_Compliance\" version=\"2.1\"\n"
 "    xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
 "    xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee \n"
-"                        http://java.sun.com/xml/ns/j2ee/ejb-jar_\\2_1.xsd"
-"\"&gt;\n"
+"                        http://java.sun.com/xml/ns/j2ee/ejb-jar_\\2_1.xsd\"&gt;\n"
 "   &lt;display-name&gt;Crime Portal&lt;/display-name&gt;\n"
 "\n"
 "    &lt;enterprise-beans&gt;\n"
 "        &lt;entity&gt;\n"
 "            &lt;display-name&gt;Gangster Entity Bean&lt;/display-name&gt;\n"
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
-"            &lt;local-home&gt;org.jboss.cmp2.crimeportal.GangsterHome&lt;/"
-"local-home&gt;\n"
+"            &lt;local-home&gt;org.jboss.cmp2.crimeportal.GangsterHome&lt;/local-home&gt;\n"
 "            &lt;local&gt;org.jboss.cmp2.crimeportal.Gangster&lt;/local&gt;\n"
 "\n"
-"            &lt;ejb-class&gt;org.jboss.cmp2.crimeportal.GangsterBean&lt;/ejb-"
-"class&gt;\n"
+"            &lt;ejb-class&gt;org.jboss.cmp2.crimeportal.GangsterBean&lt;/ejb-class&gt;\n"
 "            &lt;persistence-type&gt;Container&lt;/persistence-type&gt;\n"
 "            &lt;prim-key-class&gt;java.lang.Integer&lt;/prim-key-class&gt;\n"
 "            &lt;reentrant&gt;False&lt;/reentrant&gt;\n"
 "            &lt;cmp-version&gt;2.x&lt;/cmp-version&gt;\n"
-"            &lt;abstract-schema-name&gt;gangster&lt;/abstract-schema-"
-"name&gt;\n"
+"            &lt;abstract-schema-name&gt;gangster&lt;/abstract-schema-name&gt;\n"
 "\n"
 "            &lt;cmp-field&gt;\n"
 "                &lt;field-name&gt;gangsterId&lt;/field-name&gt;\n"
@@ -908,30 +641,25 @@
 "&lt;/ejb-jar&gt;"
 msgstr ""
 "&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
-"&lt;ejb-jar xmlns=\"http://java.sun.com/xml/ns/\"Whats_new_in_JBoss_4-"
-"J2EE_Certification_and_Standards_Compliance\" version=\"2.1\"\n"
+"&lt;ejb-jar xmlns=\"http://java.sun.com/xml/ns/\"Whats_new_in_JBoss_4-J2EE_Certification_and_Standards_Compliance\" version=\"2.1\"\n"
 "    xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
 "    xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee \n"
-"                        http://java.sun.com/xml/ns/j2ee/ejb-jar_\\2_1.xsd"
-"\"&gt;\n"
+"                        http://java.sun.com/xml/ns/j2ee/ejb-jar_\\2_1.xsd\"&gt;\n"
 "   &lt;display-name&gt;Crime Portal&lt;/display-name&gt;\n"
 "\n"
 "    &lt;enterprise-beans&gt;\n"
 "        &lt;entity&gt;\n"
 "            &lt;display-name&gt;Gangster Entity Bean&lt;/display-name&gt;\n"
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
-"            &lt;local-home&gt;org.jboss.cmp2.crimeportal.GangsterHome&lt;/"
-"local-home&gt;\n"
+"            &lt;local-home&gt;org.jboss.cmp2.crimeportal.GangsterHome&lt;/local-home&gt;\n"
 "            &lt;local&gt;org.jboss.cmp2.crimeportal.Gangster&lt;/local&gt;\n"
 "\n"
-"            &lt;ejb-class&gt;org.jboss.cmp2.crimeportal.GangsterBean&lt;/ejb-"
-"class&gt;\n"
+"            &lt;ejb-class&gt;org.jboss.cmp2.crimeportal.GangsterBean&lt;/ejb-class&gt;\n"
 "            &lt;persistence-type&gt;Container&lt;/persistence-type&gt;\n"
 "            &lt;prim-key-class&gt;java.lang.Integer&lt;/prim-key-class&gt;\n"
 "            &lt;reentrant&gt;False&lt;/reentrant&gt;\n"
 "            &lt;cmp-version&gt;2.x&lt;/cmp-version&gt;\n"
-"            &lt;abstract-schema-name&gt;gangster&lt;/abstract-schema-"
-"name&gt;\n"
+"            &lt;abstract-schema-name&gt;gangster&lt;/abstract-schema-name&gt;\n"
 "\n"
 "            &lt;cmp-field&gt;\n"
 "                &lt;field-name&gt;gangsterId&lt;/field-name&gt;\n"
@@ -958,15 +686,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:160
 #, no-c-format
-msgid ""
-"Note that we&#39;ve specified a CMP version of <literal>2.x</literal> to "
-"indicate that this is EJB 2.x CMP entity bean. The abstract schema name was "
-"set to <literal>gangster</literal>. That will be important when we look at "
-"EJB-QL queries in <xref linkend=\"The_CMP_Engine-Queries\"/>."
-msgstr ""
-"请注意,我们已经指定了 CMP 版本为 <literal>2.x</literal> 以表示这是一个 EJB "
-"2.x CMP entity bean。抽象模式名称被设置为 <literal>gangster</literal>。在 "
-"<xref linkend=\"The_CMP_Engine-Queries\"/> 里讨论 EJB-QL 查询时,这将很重要。 "
+msgid "Note that we&#39;ve specified a CMP version of <literal>2.x</literal> to indicate that this is EJB 2.x CMP entity bean. The abstract schema name was set to <literal>gangster</literal>. That will be important when we look at EJB-QL queries in <xref linkend=\"The_CMP_Engine-Queries\"/>."
+msgstr "请注意,我们已经指定了 CMP 版本为 <literal>2.x</literal> 以表示这是一个 EJB 2.x CMP entity bean。抽象模式名称被设置为 <literal>gangster</literal>。在 <xref linkend=\"The_CMP_Engine-Queries\"/> 里讨论 EJB-QL 查询时,这将很重要。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:164
@@ -977,22 +698,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:165
 #, no-c-format
-msgid ""
-"The JBoss configuration for the entity is declared with an <literal>entity</"
-"literal> element in the <literal>jbosscmp-jdbc.xml</literal> file. This file "
-"is located in the <literal>META-INF</literal> directory of the EJB JAR and "
-"contains all of the optional configuration information for configuring the "
-"CMP mapping. The <literal>entity</literal> elements for each entity bean are "
-"grouped together in the <literal>enterprise-beans</literal> element under "
-"the top level <literal>jbosscmp-jdbc</literal> element. A stubbed out entity "
-"configuration is shown below."
-msgstr ""
-"该 entity 的 JBoss 配置用 <literal>jbosscmp-jdbc.xml</literal> 文件里的 "
-"<literal>entity</literal> 元素进行声明。这个文件存在于 EJB JAR 的 "
-"<literal>META-INF</literal> 目录下,它包含所有用来配置 CMP 映射的可选配置信"
-"息。每个 entity bean 的 <literal>entity</literal> 元素都在 "
-"<literal>enterprise-beans</literal> 里进行分组,以 <literal>jbosscmp-jdbc</"
-"literal> 为顶层元素。下面是这个 entity 的根配置。 "
+msgid "The JBoss configuration for the entity is declared with an <literal>entity</literal> element in the <literal>jbosscmp-jdbc.xml</literal> file. This file is located in the <literal>META-INF</literal> directory of the EJB JAR and contains all of the optional configuration information for configuring the CMP mapping. The <literal>entity</literal> elements for each entity bean are grouped together in the <literal>enterprise-beans</literal> element under the top level <literal>jbosscmp-jdbc</literal> element. A stubbed out entity configuration is shown below."
+msgstr "该 entity 的 JBoss 配置用 <literal>jbosscmp-jdbc.xml</literal> 文件里的 <literal>entity</literal> 元素进行声明。这个文件存在于 EJB JAR 的 <literal>META-INF</literal> 目录下,它包含所有用来配置 CMP 映射的可选配置信息。每个 entity bean 的 <literal>entity</literal> 元素都在 <literal>enterprise-beans</literal> 里进行分组,以 <literal>jbosscmp-jdbc</literal> 为顶层元素。下面是这个 entity 的根配置。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:168
@@ -1041,31 +748,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:169
 #, no-c-format
-msgid ""
-"The <literal>ejb-name</literal> element is required to match the entity "
-"specification here with the one in the <literal>ejb-jar.xml</literal> file. "
-"The remainder of the elements specify either overrides the global or "
-"application-wide CMP defaults and CMP mapping details specific to the bean. "
-"The application defaults come from the <literal>defaults</literal> section "
-"of the <literal>jbosscmp-jdbc.xml</literal> file and the global defaults "
-"come from the <literal>defaults</literal> section of the "
-"<literal>standardjbosscmp-jdbc.xml</literal> file in the <literal>conf</"
-"literal> directory for the current server configuration file set. The "
-"<literal>defaults</literal> section is discussed in <xref linkend="
-"\"The_CMP_Engine-Defaults\"/>. <xref linkend=\"Entity_Mapping-"
-"The_entity_element_content_model\"/> shows the full <literal>entity</"
-"literal> content model."
-msgstr ""
-"<literal>ejb-name</literal> 元素需要匹配 <literal>ejb-jar.xml</literal> 文件"
-"里的 entity 定义。这个元素的剩余部分指定或覆盖和该 bean 相关的全局或应用程序"
-"的 CMP 缺省值以及 CMP 的映射细节。应用程序的缺省设置来自 <literal>jbosscmp-"
-"jdbc.xml</literal> 文件的 <literal>defaults</literal> 部分而全局设置来自当前"
-"服务器配置文件集的 <literal>conf</literal> 目录下的 "
-"<literal>standardjbosscmp-jdbc.xml</literal> 文件里的 <literal>defaults</"
-"literal> 部分。 <xref linkend=\"The_CMP_Engine-Defaults\"/> 里将讨论 "
-"<literal>defaults</literal> 部分的设置。<xref linkend=\"Entity_Mapping-"
-"The_entity_element_content_model\"/> 展示了完整的 <literal>entity</literal> "
-"的内容格式。 "
+msgid "The <literal>ejb-name</literal> element is required to match the entity specification here with the one in the <literal>ejb-jar.xml</literal> file. The remainder of the elements specify either overrides the global or application-wide CMP defaults and CMP mapping details specific to the bean. The application defaults come from the <literal>defaults</literal> section of the <literal>jbosscmp-jdbc.xml</literal> file and the global defaults come from the <literal>defaults</literal> section of the <literal>standardjbosscmp-jdbc.xml</literal> file in the <literal>conf</literal> directory for the current server configuration file set. The <literal>defaults</literal> section is discussed in <xref linkend=\"The_CMP_Engine-Defaults\"/>. <xref linkend=\"Entity_Mapping-The_entity_element_content_model\"/> shows the full <literal>entity</literal> content model."
+msgstr "<literal>ejb-name</literal> 元素需要匹配 <literal>ejb-jar.xml</literal> 文件里的 entity 定义。这个元素的剩余部分指定或覆盖和该 bean 相关的全局或应用程序的 CMP 缺省值以及 CMP 的映射细节。应用程序的缺省设置来自 <literal>jbosscmp-jdbc.xml</literal> 文件的 <literal>defaults</literal> 部分而全局设置来自当前服务器配置文件集的 <literal>conf</literal> 目录下的 <literal>standardjbosscmp-jdbc.xml</literal> 文件里的 <literal>defaults</literal> 部分。 <xref linkend=\"The_CMP_Engine-Defaults\"/> 里将讨论 <literal>defaults</literal> 部分的设置。<xref linkend=\"Entity_Mapping-The_entity_element_content_model\"/> 展示了完整的 <literal>entity</literal> 的内容格式。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:173
@@ -1082,378 +766,176 @@
 #. Tag: para
 #: The_CMP_Engine.xml:185
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ejb-name</emphasis>: This required element is the "
-"name of the EJB to which this configuration applies. This element must match "
-"an <literal>ejb-name</literal> of an entity in the <literal>ejb-jar.xml</"
-"literal> file."
-msgstr ""
-"<emphasis role=\"bold\">ejb-name</emphasis>:这个元素是配置所适用的 EJB 的名"
-"称。这个元素必须匹配 <literal>ejb-jar.xml</literal> 文件里的某个 entity 的 "
-"<literal>ejb-name</literal>。 "
+msgid "<emphasis role=\"bold\">ejb-name</emphasis>: This required element is the name of the EJB to which this configuration applies. This element must match an <literal>ejb-name</literal> of an entity in the <literal>ejb-jar.xml</literal> file."
+msgstr "<emphasis role=\"bold\">ejb-name</emphasis>:这个元素是配置所适用的 EJB 的名称。这个元素必须匹配 <literal>ejb-jar.xml</literal> 文件里的某个 entity 的 <literal>ejb-name</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:190
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">datasource</emphasis>: This optional element is the "
-"<literal>jndi-name</literal> used to look up the datasource. All database "
-"connections used by an entity or relation-table are obtained from the "
-"datasource. Having different datasources for entities is not recommended, as "
-"it vastly constrains the domain over which finders and ejbSelects can query. "
-"The default is <literal>java:/DefaultDS</literal> unless overridden in the "
-"defaults section."
-msgstr ""
-"<emphasis role=\"bold\">datasource</emphasis>:这个可选元素是用来查找数据库"
-"的 <literal>jndi-name</literal>。entity 或关系型表使用的所有数据库连接都从数"
-"据源(datasource)获得。我们不推荐把不同的数据源用于 entity,因为这极大地限制"
-"了 finders 和 ejbSelects 可以查询的范围。除非在 defaults 部分进行覆盖,它的缺"
-"省值是 <literal>java:/DefaultDS</literal>。 "
+msgid "<emphasis role=\"bold\">datasource</emphasis>: This optional element is the <literal>jndi-name</literal> used to look up the datasource. All database connections used by an entity or relation-table are obtained from the datasource. Having different datasources for entities is not recommended, as it vastly constrains the domain over which finders and ejbSelects can query. The default is <literal>java:/DefaultDS</literal> unless overridden in the defaults section."
+msgstr "<emphasis role=\"bold\">datasource</emphasis>:这个可选元素是用来查找数据库的 <literal>jndi-name</literal>。entity 或关系型表使用的所有数据库连接都从数据源(datasource)获得。我们不推荐把不同的数据源用于 entity,因为这极大地限制了 finders 和 ejbSelects 可以查询的范围。除非在 defaults 部分进行覆盖,它的缺省值是 <literal>java:/DefaultDS</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:195
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">datasource-mapping</emphasis>: This optional element "
-"specifies the name of the <literal>type-mapping</literal>, which determines "
-"how Java types are mapped to SQL types, and how EJB-QL functions are mapped "
-"to database specific functions. Type mappings are discussed in <xref linkend="
-"\"Datasource_Customization-Mapping\"/>. The default is <literal>Hypersonic "
-"SQL</literal> unless overridden in the defaults section."
-msgstr ""
-"<emphasis role=\"bold\">datasource-mapping</emphasis>:这个可选元素指定 "
-"<literal>type-mapping</literal> 的名称,它决定 Java 类型如何映射到 SQL 类型,"
-"以及 EJB-QL 功能如何映射到数据库专有的功能。<xref linkend="
-"\"Datasource_Customization-Mapping\"/> 里将讨论类型映射。除非在 defaults 部分"
-"进行覆盖,它的缺省值是 <literal>Hypersonic SQL</literal>。 "
+msgid "<emphasis role=\"bold\">datasource-mapping</emphasis>: This optional element specifies the name of the <literal>type-mapping</literal>, which determines how Java types are mapped to SQL types, and how EJB-QL functions are mapped to database specific functions. Type mappings are discussed in <xref linkend=\"Datasource_Customization-Mapping\"/>. The default is <literal>Hypersonic SQL</literal> unless overridden in the defaults section."
+msgstr "<emphasis role=\"bold\">datasource-mapping</emphasis>:这个可选元素指定 <literal>type-mapping</literal> 的名称,它决定 Java 类型如何映射到 SQL 类型,以及 EJB-QL 功能如何映射到数据库专有的功能。<xref linkend=\"Datasource_Customization-Mapping\"/> 里将讨论类型映射。除非在 defaults 部分进行覆盖,它的缺省值是 <literal>Hypersonic SQL</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:200
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">create-table</emphasis>: This optional element when "
-"true, specifies that JBoss should attempt to create a table for the entity. "
-"When the application is deployed, JBoss checks if a table already exists "
-"before creating the table. If a table is found, it is logged, and the table "
-"is not created. This option is very useful during the early stages of "
-"development when the table structure changes often. The default is false "
-"unless overridden in the defaults section."
-msgstr ""
-"<emphasis role=\"bold\">create-table</emphasis>:如果设置这个可选元素为 "
-"true,表示 JBoss 应该试图为这个 entity 创建一个表。当应用程序被部署时,JBoss "
-"将在创建表之前检查它是否已经存在。如果找到了一个表,JBoss 将进行记录且不再创"
-"建。在部署的早期,但表结果经常变动时,这个选项非常有用。除非在 defauts 部分进"
-"行覆盖,它的缺省值为 false。 "
+msgid "<emphasis role=\"bold\">create-table</emphasis>: This optional element when true, specifies that JBoss should attempt to create a table for the entity. When the application is deployed, JBoss checks if a table already exists before creating the table. If a table is found, it is logged, and the table is not created. This option is very useful during the early stages of development when the table structure changes often. The default is false unless overridden in the defaults section."
+msgstr "<emphasis role=\"bold\">create-table</emphasis>:如果设置这个可选元素为 true,表示 JBoss 应该试图为这个 entity 创建一个表。当应用程序被部署时,JBoss 将在创建表之前检查它是否已经存在。如果找到了一个表,JBoss 将进行记录且不再创建。在部署的早期,但表结果经常变动时,这个选项非常有用。除非在 defauts 部分进行覆盖,它的缺省值为 false。 "
 
 #. Tag: para
-#: The_CMP_Engine.xml:205 The_CMP_Engine.xml:2553
+#: The_CMP_Engine.xml:205
+#: The_CMP_Engine.xml:2553
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">alter-table</emphasis>: If <literal>create-table</"
-"literal> is used to automatically create the schema, <literal>alter-table</"
-"literal> can be used to keep the schema current with changes to the entity "
-"bean. Alter table will perform the following specific tasks:"
-msgstr ""
-"<emphasis role=\"bold\">alter-table</emphasis>:如果 <literal>create-table</"
-"literal> 被用来自动创建表,<literal>alter-table</literal> 则被用来应用 "
-"entity bean 的当前变动。Alter table 将执行下面的特殊任务: "
+msgid "<emphasis role=\"bold\">alter-table</emphasis>: If <literal>create-table</literal> is used to automatically create the schema, <literal>alter-table</literal> can be used to keep the schema current with changes to the entity bean. Alter table will perform the following specific tasks:"
+msgstr "<emphasis role=\"bold\">alter-table</emphasis>:如果 <literal>create-table</literal> 被用来自动创建表,<literal>alter-table</literal> 则被用来应用 entity bean 的当前变动。Alter table 将执行下面的特殊任务: "
 
 #. Tag: para
-#: The_CMP_Engine.xml:210 The_CMP_Engine.xml:2558
+#: The_CMP_Engine.xml:210
+#: The_CMP_Engine.xml:2558
 #, no-c-format
 msgid "new fields will be created"
 msgstr "添加新的字段 "
 
 #. Tag: para
-#: The_CMP_Engine.xml:215 The_CMP_Engine.xml:2563
+#: The_CMP_Engine.xml:215
+#: The_CMP_Engine.xml:2563
 #, no-c-format
 msgid "fields which are no longer used will be removed"
 msgstr "不再使用的字段将被删除 "
 
 #. Tag: para
-#: The_CMP_Engine.xml:220 The_CMP_Engine.xml:2568
+#: The_CMP_Engine.xml:220
+#: The_CMP_Engine.xml:2568
 #, no-c-format
-msgid ""
-"string fields which are shorter than the declared length will have their "
-"length increased to the declared length. (not supported by all databases)"
+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 "字符串字段如果比所声明的要短,则扩大至所声明的长度。(不是所有数据库都支持) "
 
 #. Tag: para
 #: The_CMP_Engine.xml:227
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">remove-table</emphasis>: This optional element when "
-"true, JBoss will attempt to drop the table for each entity and each relation "
-"table mapped relationship. When the application is undeployed, JBoss will "
-"attempt to drop the table. This option is very useful during the early "
-"stages of development when the table structure changes often. The default is "
-"false unless overridden in the defaults section."
-msgstr ""
-"<emphasis role=\"bold\">remove-table</emphasis>:如果这个可选元素为 true,"
-"JBoss 将试图删除每个 entity 以及关系型表匹配的关系所对应的表。当应用程序被卸"
-"载时,JBoss 将试图删除这个表。在部署的早期,当表结构经常变动时,这个选项非常"
-"有用。除非在 defauts 部分进行覆盖,它的缺省值是 false。 "
+msgid "<emphasis role=\"bold\">remove-table</emphasis>: This optional element when true, JBoss will attempt to drop the table for each entity and each relation table mapped relationship. When the application is undeployed, JBoss will attempt to drop the table. This option is very useful during the early stages of development when the table structure changes often. The default is false unless overridden in the defaults section."
+msgstr "<emphasis role=\"bold\">remove-table</emphasis>:如果这个可选元素为 true,JBoss 将试图删除每个 entity 以及关系型表匹配的关系所对应的表。当应用程序被卸载时,JBoss 将试图删除这个表。在部署的早期,当表结构经常变动时,这个选项非常有用。除非在 defauts 部分进行覆盖,它的缺省值是 false。 "
 
 #. Tag: para
-#: The_CMP_Engine.xml:232 The_CMP_Engine.xml:801
+#: The_CMP_Engine.xml:232
+#: The_CMP_Engine.xml:801
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">post-table-create</emphasis>: This optional element "
-"specifies an arbitrary SQL statement that should be executed immediately "
-"after the database table is created. This command is only executed if "
-"<literal>create-table</literal> is true and the table did not previously "
-"exist."
-msgstr ""
-"<emphasis role=\"bold\">post-table-create</emphasis>:这个可选元素指定在数据"
-"库表被创建后立即执行的任意 SQL 语句。如果 <literal>create-table</literal> 为 "
-"true 且表以前不存在时,这个命令才会被执行。"
+msgid "<emphasis role=\"bold\">post-table-create</emphasis>: This optional element specifies an arbitrary SQL statement that should be executed immediately after the database table is created. This command is only executed if <literal>create-table</literal> is true and the table did not previously exist."
+msgstr "<emphasis role=\"bold\">post-table-create</emphasis>:这个可选元素指定在数据库表被创建后立即执行的任意 SQL 语句。如果 <literal>create-table</literal> 为 true 且表以前不存在时,这个命令才会被执行。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:237
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-only</emphasis>: This optional element when "
-"true specifies that the bean provider will not be allowed to change the "
-"value of any fields. A field that is read-only will not be stored in, or "
-"inserted into, the database. If a primary key field is read-only, the create "
-"method will throw a <literal>CreateException</literal>. If a set accessor is "
-"called on a read-only field, it throws an <literal>EJBException</literal>. "
-"Read-only fields are useful for fields that are filled in by database "
-"triggers, such as last update. The <literal>read-only</literal> option can "
-"be overridden on a per <literal>cmp-field</literal> basis, and is discussed "
-"in <xref linkend=\"CMP_Fields-Read_only_Fields\"/>. The default is false "
-"unless overridden in the <literal>defaults</literal> section."
-msgstr ""
-"<emphasis role=\"bold\">read-only</emphasis>:这个可选元素为 true 时表示不允"
-"许 bean 提供者改变任何字段的值。只读字段不能存储、插入数据库。如果主键字段是"
-"只读的,那么 create 方法将抛出 <literal>CreateException</literal>。如果对只读"
-"字段调用 set 存取方法,它将抛出 <literal>EJBException</literal>。只读字段可用"
-"于数据库触发器(Trigger)填值的字段。<literal>read-only</literal> 选项可以根"
-"据 <literal>cmp-field</literal> 逐个覆盖,这将在 <xref linkend=\"CMP_Fields-"
-"Read_only_Fields\"/> 里进行讨论。除非在 <literal>defaults</literal> 部分覆"
-"盖,它的缺省值是 false。 "
+msgid "<emphasis role=\"bold\">read-only</emphasis>: This optional element when true specifies that the bean provider will not be allowed to change the value of any fields. A field that is read-only will not be stored in, or inserted into, the database. If a primary key field is read-only, the create method will throw a <literal>CreateException</literal>. If a set accessor is called on a read-only field, it throws an <literal>EJBException</literal>. Read-only fields are useful for fields that are filled in by database triggers, such as last update. The <literal>read-only</literal> option can be overridden on a per <literal>cmp-field</literal> basis, and is discussed in <xref linkend=\"CMP_Fields-Read_only_Fields\"/>. The default is false unless overridden in the <literal>defaults</literal> section."
+msgstr "<emphasis role=\"bold\">read-only</emphasis>:这个可选元素为 true 时表示不允许 bean 提供者改变任何字段的值。只读字段不能存储、插入数据库。如果主键字段是只读的,那么 create 方法将抛出 <literal>CreateException</literal>。如果对只读字段调用 set 存取方法,它将抛出 <literal>EJBException</literal>。只读字段可用于数据库触发器(Trigger)填值的字段。<literal>read-only</literal> 选项可以根据 <literal>cmp-field</literal> 逐个覆盖,这将在 <xref linkend=\"CMP_Fields-Read_only_Fields\"/> 里进行讨论。除非在 <literal>defaults</literal> 部分覆盖,它的缺省值是 false。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:242
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-time-out</emphasis>: This optional element is "
-"the amount of time in milliseconds that a read on a read-only field is "
-"valid. A value of 0 means that the value is always reloaded at the start of "
-"a transaction, and a value of -1 means that the value never times out. This "
-"option can also be overridden on a per <literal>cmp-field</literal> basis. "
-"If <literal>read-only</literal> is false, this value is ignored. The default "
-"is -1 unless overridden in the <literal>defaults</literal> section."
-msgstr ""
-"<emphasis role=\"bold\">read-time-out</emphasis>:这个可选元素定义只读字段的"
-"读操作的有效期(毫秒数)。0 表示在事务启动时总是重新加载,而 -1 表示用不超"
-"时。这个选项也可以根据 <literal>cmp-field</literal> 进行覆盖。如果 "
-"<literal>read-only</literal> 为 false,这个值将被忽略。除非在 "
-"<literal>defaults</literal> 部分进行覆盖,其缺省值是 -1。 "
+msgid "<emphasis role=\"bold\">read-time-out</emphasis>: This optional element is the amount of time in milliseconds that a read on a read-only field is valid. A value of 0 means that the value is always reloaded at the start of a transaction, and a value of -1 means that the value never times out. This option can also be overridden on a per <literal>cmp-field</literal> basis. If <literal>read-only</literal> is false, this value is ignored. The default is -1 unless overridden in the <literal>defaults</literal> section."
+msgstr "<emphasis role=\"bold\">read-time-out</emphasis>:这个可选元素定义只读字段的读操作的有效期(毫秒数)。0 表示在事务启动时总是重新加载,而 -1 表示用不超时。这个选项也可以根据 <literal>cmp-field</literal> 进行覆盖。如果 <literal>read-only</literal> 为 false,这个值将被忽略。除非在 <literal>defaults</literal> 部分进行覆盖,其缺省值是 -1。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:247
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">row-locking</emphasis>: This optional element if "
-"true specifies that JBoss will lock all rows loaded in a transaction. Most "
-"databases implement this by using the <literal>SELECT FOR UPDATE</literal> "
-"syntax when loading the entity, but the actual syntax is determined by the "
-"<literal>row-locking-template</literal> in the datasource-mapping used by "
-"this entity. The default is false unless overridden in the "
-"<literal>defaults</literal> section."
-msgstr ""
-"<emphasis role=\"bold\">row-locking</emphasis>:这个可选元素为 true 时表示 "
-"JBoss 将锁住在事务里加载的所有记录。大多数数据库通过在加载 entity 时调用 "
-"<literal>SELECT FOR UPDATE</literal> 来实现这个功能,但实际的语法由这个 "
-"entity 使用的 datasource-mapping 里的 <literal>row-locking-template</"
-"literal> 决定。除非在 <literal>defaults</literal> 部分进行覆盖,其缺省值是 "
-"false。 "
+msgid "<emphasis role=\"bold\">row-locking</emphasis>: This optional element if true specifies that JBoss will lock all rows loaded in a transaction. Most databases implement this by using the <literal>SELECT FOR UPDATE</literal> syntax when loading the entity, but the actual syntax is determined by the <literal>row-locking-template</literal> in the datasource-mapping used by this entity. The default is false unless overridden in the <literal>defaults</literal> section."
+msgstr "<emphasis role=\"bold\">row-locking</emphasis>:这个可选元素为 true 时表示 JBoss 将锁住在事务里加载的所有记录。大多数数据库通过在加载 entity 时调用 <literal>SELECT FOR UPDATE</literal> 来实现这个功能,但实际的语法由这个 entity 使用的 datasource-mapping 里的 <literal>row-locking-template</literal> 决定。除非在 <literal>defaults</literal> 部分进行覆盖,其缺省值是 false。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:252
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">pk-constraint</emphasis>: This optional element if "
-"true specifies that JBoss will add a primary key constraint when creating "
-"tables. The default is true unless overridden in the defaults section."
-msgstr ""
-"<emphasis role=\"bold\">pk-constraint</emphasis>:这个可选元素为 true 表示 "
-"JBoss 将在创建表时添加一个主键约束。除非在 defaults 部分进行覆盖,其缺省值是 "
-"true。 "
+msgid "<emphasis role=\"bold\">pk-constraint</emphasis>: This optional element if true specifies that JBoss will add a primary key constraint when creating tables. The default is true unless overridden in the defaults section."
+msgstr "<emphasis role=\"bold\">pk-constraint</emphasis>:这个可选元素为 true 表示 JBoss 将在创建表时添加一个主键约束。除非在 defaults 部分进行覆盖,其缺省值是 true。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:257
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-ahead</emphasis>: This optional element "
-"controls caching of query results and <literal>cmr-fields</literal> for the "
-"entity. This option is discussed in <xref linkend=\"Optimized_Loading-"
-"Read_ahead\"/>."
-msgstr ""
-"<emphasis role=\"bold\">read-ahead</emphasis>:这个可选元素控制查询结果的缓存"
-"和 entity 的 <literal>cmr-fields</literal>。<xref linkend="
-"\"Optimized_Loading-Read_ahead\"/> 将对它进行访问。 "
+msgid "<emphasis role=\"bold\">read-ahead</emphasis>: This optional element controls caching of query results and <literal>cmr-fields</literal> for the entity. This option is discussed in <xref linkend=\"Optimized_Loading-Read_ahead\"/>."
+msgstr "<emphasis role=\"bold\">read-ahead</emphasis>:这个可选元素控制查询结果的缓存和 entity 的 <literal>cmr-fields</literal>。<xref linkend=\"Optimized_Loading-Read_ahead\"/> 将对它进行访问。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:262
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">fetch-size</emphasis>: This optional element "
-"specifies the number of entities to read in one round-trip to the underlying "
-"datastore. The default is 0 unless overridden in the defaults section."
-msgstr ""
-"<emphasis role=\"bold\">fetch-size</emphasis>:这个可选元素指定从底层数据库一"
-"次所读取的 entity 的个数。除非在 defaults 部分进行覆盖,其缺省值是 0。 "
+msgid "<emphasis role=\"bold\">fetch-size</emphasis>: This optional element specifies the number of entities to read in one round-trip to the underlying datastore. The default is 0 unless overridden in the defaults section."
+msgstr "<emphasis role=\"bold\">fetch-size</emphasis>:这个可选元素指定从底层数据库一次所读取的 entity 的个数。除非在 defaults 部分进行覆盖,其缺省值是 0。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:267
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">list-cache-max</emphasis>: This optional element "
-"specifies the number of read-lists that can be tracked by this entity. This "
-"option is discussed in <literal>on-load</literal>. The default is 1000 "
-"unless overridden in the defaults section."
-msgstr ""
-"<emphasis role=\"bold\">list-cache-max</emphasis>:这个可选元素指定这个 "
-"entity 可追踪的 read-list 的个数。这个选项将在 <literal>on-load</literal> 里"
-"进行讨论。除非在 defaults 部分进行覆盖,其缺省值是 1000。 "
+msgid "<emphasis role=\"bold\">list-cache-max</emphasis>: This optional element specifies the number of read-lists that can be tracked by this entity. This option is discussed in <literal>on-load</literal>. The default is 1000 unless overridden in the defaults section."
+msgstr "<emphasis role=\"bold\">list-cache-max</emphasis>:这个可选元素指定这个 entity 可追踪的 read-list 的个数。这个选项将在 <literal>on-load</literal> 里进行讨论。除非在 defaults 部分进行覆盖,其缺省值是 1000。 "
 
 #. Tag: para
-#: The_CMP_Engine.xml:272 The_CMP_Engine.xml:2615
+#: The_CMP_Engine.xml:272
+#: The_CMP_Engine.xml:2615
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">clean-read-ahead-on-load</emphasis>: When an entity "
-"is loaded from the read ahead cache, JBoss can remove the data used from the "
-"read ahead cache. The default is <literal>false</literal>."
-msgstr ""
-"<emphasis role=\"bold\">clean-read-ahead-on-load</emphasis>:当 entity 从 "
-"read ahead 缓存里载入时,JBoss 可以删除 read ahead 缓存里的数据。其缺省值是 "
-"<literal>false</literal>。 "
+msgid "<emphasis role=\"bold\">clean-read-ahead-on-load</emphasis>: When an entity is loaded from the read ahead cache, JBoss can remove the data used from the read ahead cache. The default is <literal>false</literal>."
+msgstr "<emphasis role=\"bold\">clean-read-ahead-on-load</emphasis>:当 entity 从 read ahead 缓存里载入时,JBoss 可以删除 read ahead 缓存里的数据。其缺省值是 <literal>false</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:277
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">table-name</emphasis>: This optional element is the "
-"name of the table that will hold data for this entity. Each entity instance "
-"will be stored in one row of this table. The default is the <literal>ejb-"
-"name</literal>."
-msgstr ""
-"<emphasis role=\"bold\">table-name</emphasis>:这个可选元素是为该 entity 存储"
-"数据的表的名称。每个 entity 实例都将存储在这个表的一行里。它的缺省值是 "
-"<literal>ejb-name</literal>。 "
+msgid "<emphasis role=\"bold\">table-name</emphasis>: This optional element is the name of the table that will hold data for this entity. Each entity instance will be stored in one row of this table. The default is the <literal>ejb-name</literal>."
+msgstr "<emphasis role=\"bold\">table-name</emphasis>:这个可选元素是为该 entity 存储数据的表的名称。每个 entity 实例都将存储在这个表的一行里。它的缺省值是 <literal>ejb-name</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:282
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">cmp-field</emphasis>: The optional element allows "
-"one to define how the <literal>ejb-jar.xml</literal><literal>cmp-field</"
-"literal> is mapped onto the persistence store. This is discussed in <xref "
-"linkend=\"The_CMP_Engine-CMP_Fields\"/>."
-msgstr ""
-"<emphasis role=\"bold\">cmp-field</emphasis>:这个可选元素允许你定义怎样把 "
-"<literal>ejb-jar.xml</literal> 里的 <literal>cmp-field</literal> 映射到持久性"
-"存储里。这将在 <xref linkend=\"The_CMP_Engine-CMP_Fields\"/> 进行讨论。 "
+msgid "<emphasis role=\"bold\">cmp-field</emphasis>: The optional element allows one to define how the <literal>ejb-jar.xml</literal><literal>cmp-field</literal> is mapped onto the persistence store. This is discussed in <xref linkend=\"The_CMP_Engine-CMP_Fields\"/>."
+msgstr "<emphasis role=\"bold\">cmp-field</emphasis>:这个可选元素允许你定义怎样把 <literal>ejb-jar.xml</literal> 里的 <literal>cmp-field</literal> 映射到持久性存储里。这将在 <xref linkend=\"The_CMP_Engine-CMP_Fields\"/> 进行讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:287
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">load-groups</emphasis>: This optional element "
-"specifies one or more groupings of CMP fields to declare load groupings of "
-"fields. This is discussed in <xref linkend=\"Optimized_Loading-Load_Groups\"/"
-">."
-msgstr ""
-"<emphasis role=\"bold\">load-groups</emphasis>:这个可选元素指定一个或多个 "
-"CMP 字段组来声明字段的 load grouping。这将在 <xref linkend="
-"\"Optimized_Loading-Load_Groups\"/> 里进行讨论。 "
+msgid "<emphasis role=\"bold\">load-groups</emphasis>: This optional element specifies one or more groupings of CMP fields to declare load groupings of fields. This is discussed in <xref linkend=\"Optimized_Loading-Load_Groups\"/>."
+msgstr "<emphasis role=\"bold\">load-groups</emphasis>:这个可选元素指定一个或多个 CMP 字段组来声明字段的 load grouping。这将在 <xref linkend=\"Optimized_Loading-Load_Groups\"/> 里进行讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:292
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">eager-load-groups</emphasis>: This optional element "
-"defines one or more load grouping as eager load groups. This is discussed in "
-"<xref linkend=\"Loading_Process-Eager_loading_Process\"/>."
-msgstr ""
-"<emphasis role=\"bold\">eager-load-groups</emphasis>:这个可选元素将一个或多"
-"个 load grouping 定义为 eager load group。这将在 <xref linkend="
-"\"Loading_Process-Eager_loading_Process\"/> 里进行讨论。 "
+msgid "<emphasis role=\"bold\">eager-load-groups</emphasis>: This optional element defines one or more load grouping as eager load groups. This is discussed in <xref linkend=\"Loading_Process-Eager_loading_Process\"/>."
+msgstr "<emphasis role=\"bold\">eager-load-groups</emphasis>:这个可选元素将一个或多个 load grouping 定义为 eager load group。这将在 <xref linkend=\"Loading_Process-Eager_loading_Process\"/> 里进行讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:297
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">lazy-load-groups</emphasis>: This optional element "
-"defines one or more load grouping as lazy load groups. This is discussed in "
-"<xref linkend=\"Loading_Process-Lazy_loading_Process\"/>."
-msgstr ""
-"<emphasis role=\"bold\">lazy-load-groups</emphasis>:这个可选元素将一个或多"
-"个 load grouping 定义为 lazy load group。这将在 <xref linkend="
-"\"Loading_Process-Lazy_loading_Process\"/> 里进行讨论。 "
+msgid "<emphasis role=\"bold\">lazy-load-groups</emphasis>: This optional element defines one or more load grouping as lazy load groups. This is discussed in <xref linkend=\"Loading_Process-Lazy_loading_Process\"/>."
+msgstr "<emphasis role=\"bold\">lazy-load-groups</emphasis>:这个可选元素将一个或多个 load grouping 定义为 lazy load group。这将在 <xref linkend=\"Loading_Process-Lazy_loading_Process\"/> 里进行讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:302
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">query</emphasis>: This optional element specifies "
-"the definition of finders and selectors. This is discussed in <xref linkend="
-"\"The_CMP_Engine-Queries\"/>."
-msgstr ""
-"<emphasis role=\"bold\">query</emphasis>:这个可选元素定义 finder 和 "
-"selector。这将在 <xref linkend=\"The_CMP_Engine-Queries\"/> 里进行讨论。 "
+msgid "<emphasis role=\"bold\">query</emphasis>: This optional element specifies the definition of finders and selectors. This is discussed in <xref linkend=\"The_CMP_Engine-Queries\"/>."
+msgstr "<emphasis role=\"bold\">query</emphasis>:这个可选元素定义 finder 和 selector。这将在 <xref linkend=\"The_CMP_Engine-Queries\"/> 里进行讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:307
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">unknown-pk</emphasis>: This optional element allows "
-"one to define how an unknown primary key type of <literal>java.lang.Object</"
-"literal> maps to the persistent store."
-msgstr ""
-"<emphasis role=\"bold\">unknown-pk</emphasis>:这个可选元素允许你定义未知主键"
-"类型的 <literal>java.lang.Object</literal> 怎样映射到持久性存储里。 "
+msgid "<emphasis role=\"bold\">unknown-pk</emphasis>: This optional element allows one to define how an unknown primary key type of <literal>java.lang.Object</literal> maps to the persistent store."
+msgstr "<emphasis role=\"bold\">unknown-pk</emphasis>:这个可选元素允许你定义未知主键类型的 <literal>java.lang.Object</literal> 怎样映射到持久性存储里。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:312
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">entity-command</emphasis>: This optional element "
-"allows one to define the entity creation command instance. Typically this is "
-"used to define a custom command instance to allow for primary key "
-"generation. This is described in detail in <xref linkend=\"The_CMP_Engine-"
-"Entity_Commands_and_Primary_Key_Generation\"/>."
-msgstr ""
-"<emphasis role=\"bold\">entity-command</emphasis>:这个可选元素允许你定义创"
-"建 entity 的 command 实例。通常它用来定义自定义的 command 实例来产生主键。这"
-"将在 <xref linkend=\"The_CMP_Engine-"
-"Entity_Commands_and_Primary_Key_Generation\"/> 里进行详细讨论。 "
+msgid "<emphasis role=\"bold\">entity-command</emphasis>: This optional element allows one to define the entity creation command instance. Typically this is used to define a custom command instance to allow for primary key generation. This is described in detail in <xref linkend=\"The_CMP_Engine-Entity_Commands_and_Primary_Key_Generation\"/>."
+msgstr "<emphasis role=\"bold\">entity-command</emphasis>:这个可选元素允许你定义创建 entity 的 command 实例。通常它用来定义自定义的 command 实例来产生主键。这将在 <xref linkend=\"The_CMP_Engine-Entity_Commands_and_Primary_Key_Generation\"/> 里进行详细讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:317
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">optimistic-locking</emphasis>: This optional element "
-"defines the strategy to use for optimistic locking. This is described in "
-"detail in <xref linkend=\"The_CMP_Engine-Optimistic_Locking\"/>."
-msgstr ""
-"<emphasis role=\"bold\">optimistic-locking</emphasis>:这个可选元素定义用于乐"
-"观锁定的策略。这将在 <xref linkend=\"The_CMP_Engine-Optimistic_Locking\"/> 里"
-"进行详细讨论。 "
+msgid "<emphasis role=\"bold\">optimistic-locking</emphasis>: This optional element defines the strategy to use for optimistic locking. This is described in detail in <xref linkend=\"The_CMP_Engine-Optimistic_Locking\"/>."
+msgstr "<emphasis role=\"bold\">optimistic-locking</emphasis>:这个可选元素定义用于乐观锁定的策略。这将在 <xref linkend=\"The_CMP_Engine-Optimistic_Locking\"/> 里进行详细讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:322
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">audit</emphasis>: This optional element defines the "
-"CMP fields that will be audited. This is described in detail in <xref "
-"linkend=\"CMP_Fields-Auditing_Entity_Access\"/>."
-msgstr ""
-"<emphasis role=\"bold\">audit</emphasis>:这个可选元素定义将被审计的 CMP 字"
-"段。这将在 <xref linkend=\"CMP_Fields-Auditing_Entity_Access\"/> 里进行详细讨"
-"论。 "
+msgid "<emphasis role=\"bold\">audit</emphasis>: This optional element defines the CMP fields that will be audited. This is described in detail in <xref linkend=\"CMP_Fields-Auditing_Entity_Access\"/>."
+msgstr "<emphasis role=\"bold\">audit</emphasis>:这个可选元素定义将被审计的 CMP 字段。这将在 <xref linkend=\"CMP_Fields-Auditing_Entity_Access\"/> 里进行详细讨论。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:332
@@ -1464,18 +946,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:333
 #, no-c-format
-msgid ""
-"CMP fields are declared on the bean class as abstract getter and setter "
-"methods that follow the JavaBean property accessor conventions. Our gangster "
-"bean, for example, has a <literal>getName()</literal> and a <literal>setName"
-"()</literal> method for accessing the <literal>name</literal> CMP field. In "
-"this section we will look at how the configure these declared CMP fields and "
-"control the persistence and behavior."
-msgstr ""
-"CMP 字段在 bean 类里被声明为 abstract getter 和 setter 方法,这遵循了 "
-"JavaBean 的属性存取器约定。例如,gangster bean 有一个 <literal>getName()</"
-"literal> 和 <literal>setName()</literal> 方法来访问 <literal>name</literal> "
-"CMP 字段。本节我们将查看怎样配置这些声明的 CMP 字段和控制其持久性以及行为。 "
+msgid "CMP fields are declared on the bean class as abstract getter and setter methods that follow the JavaBean property accessor conventions. Our gangster bean, for example, has a <literal>getName()</literal> and a <literal>setName()</literal> method for accessing the <literal>name</literal> CMP field. In this section we will look at how the configure these declared CMP fields and control the persistence and behavior."
+msgstr "CMP 字段在 bean 类里被声明为 abstract getter 和 setter 方法,这遵循了 JavaBean 的属性存取器约定。例如,gangster bean 有一个 <literal>getName()</literal> 和 <literal>setName()</literal> 方法来访问 <literal>name</literal> CMP 字段。本节我们将查看怎样配置这些声明的 CMP 字段和控制其持久性以及行为。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:337
@@ -1486,17 +958,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:338
 #, no-c-format
-msgid ""
-"The declaration of a CMP field starts in the <literal>ejb-jar.xml</literal> "
-"file. On the gangster bean, for example, the <literal>gangsterId</literal>, "
-"<literal>name</literal>, <literal>nickName</literal> and <literal>badness</"
-"literal> would be declared in the <literal>ejb-jar.xml</literal> file as "
-"follows:"
-msgstr ""
-"CMP 字段的声明可以从 <literal>ejb-jar.xml</literal> 文件开始。以 gangster "
-"bean 为例,<literal>gangsterId</literal>、<literal>name</literal>、"
-"<literal>nickName</literal> 和 <literal>badness</literal> 都在 <literal>ejb-"
-"jar.xml</literal> 里进行声明: "
+msgid "The declaration of a CMP field starts in the <literal>ejb-jar.xml</literal> file. On the gangster bean, for example, the <literal>gangsterId</literal>, <literal>name</literal>, <literal>nickName</literal> and <literal>badness</literal> would be declared in the <literal>ejb-jar.xml</literal> file as follows:"
+msgstr "CMP 字段的声明可以从 <literal>ejb-jar.xml</literal> 文件开始。以 gangster bean 为例,<literal>gangsterId</literal>、<literal>name</literal>、<literal>nickName</literal> 和 <literal>badness</literal> 都在 <literal>ejb-jar.xml</literal> 里进行声明: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:341
@@ -1506,14 +969,10 @@
 "  &lt;enterprise-beans&gt;\n"
 "    &lt;entity&gt;\n"
 "        &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;gangsterId&lt;/field-name&gt;&lt;/"
-"cmp-field&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;name&lt;/field-name&gt;&lt;/cmp-"
-"field&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;nickName&lt;/field-name&gt;&lt;/"
-"cmp-field&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;badness&lt;/field-name&gt;&lt;/"
-"cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;gangsterId&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;name&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;nickName&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;badness&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
 "    &lt;/entity&gt;\n"
 "  &lt;/enterprise-beans&gt;\n"
 "            &lt;/ejb-jar&gt;"
@@ -1522,14 +981,10 @@
 "  &lt;enterprise-beans&gt;\n"
 "    &lt;entity&gt;\n"
 "        &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;gangsterId&lt;/field-name&gt;&lt;/"
-"cmp-field&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;name&lt;/field-name&gt;&lt;/cmp-"
-"field&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;nickName&lt;/field-name&gt;&lt;/"
-"cmp-field&gt;\n"
-"        &lt;cmp-field&gt;&lt;field-name&gt;badness&lt;/field-name&gt;&lt;/"
-"cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;gangsterId&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;name&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;nickName&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
+"        &lt;cmp-field&gt;&lt;field-name&gt;badness&lt;/field-name&gt;&lt;/cmp-field&gt;\n"
 "    &lt;/entity&gt;\n"
 "  &lt;/enterprise-beans&gt;\n"
 "            &lt;/ejb-jar&gt;"
@@ -1537,13 +992,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:342
 #, no-c-format
-msgid ""
-"Note that the J2EE deployment descriptor doesn&#39;t declare any object-"
-"relational mapping details or other configuration. It is nothing more than a "
-"simple declaration of the CMP fields."
-msgstr ""
-"请注意 J2EE 的部署描述符并不声明任何和对象相关的映射细节或其他配置。它仅仅是"
-"对 CMP 字段的简单声明。 "
+msgid "Note that the J2EE deployment descriptor doesn&#39;t declare any object-relational mapping details or other configuration. It is nothing more than a simple declaration of the CMP fields."
+msgstr "请注意 J2EE 的部署描述符并不声明任何和对象相关的映射细节或其他配置。它仅仅是对 CMP 字段的简单声明。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:348
@@ -1554,23 +1004,13 @@
 #. Tag: para
 #: The_CMP_Engine.xml:349
 #, no-c-format
-msgid ""
-"The relational mapping configuration of a CMP field is done in the "
-"<literal>jbosscmp-jdbc.xml</literal> file. The structure is similar to the "
-"<literal>ejb-jar.xml</literal> with an entity <literal>element</literal> "
-"that has <literal>cmp-field</literal> elements under it with the additional "
-"configuration details."
-msgstr ""
-"CMP 字段的关系映射配置在 <literal>jbosscmp-jdbc.xml</literal> 里完成。这个结"
-"构类似于带有包含 <literal>cmp-field</literal> 元素的 entity "
-"<literal>element</literal> 的 <literal>ejb-jar.xml</literal> 文件。 "
+msgid "The relational mapping configuration of a CMP field is done in the <literal>jbosscmp-jdbc.xml</literal> file. The structure is similar to the <literal>ejb-jar.xml</literal> with an entity <literal>element</literal> that has <literal>cmp-field</literal> elements under it with the additional configuration details."
+msgstr "CMP 字段的关系映射配置在 <literal>jbosscmp-jdbc.xml</literal> 里完成。这个结构类似于带有包含 <literal>cmp-field</literal> 元素的 entity <literal>element</literal> 的 <literal>ejb-jar.xml</literal> 文件。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:352
 #, no-c-format
-msgid ""
-"The following is shows the basic column name and data type mappings for the "
-"gangster bean."
+msgid "The following is shows the basic column name and data type mappings for the gangster bean."
 msgstr "下面展示了 gangster bean 的基本列名称和数据类型映射。 "
 
 #. Tag: programlisting
@@ -1638,12 +1078,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:356
 #, no-c-format
-msgid ""
-"The full content model of the <literal>cmp-field</literal> element of the "
-"<literal>jbosscmp-jdbc.xml</literal> is shown below."
-msgstr ""
-"下面是 <literal>jbosscmp-jdbc.xml</literal> 的 <literal>cmp-field</literal> "
-"元素的完整内容模型。 "
+msgid "The full content model of the <literal>cmp-field</literal> element of the <literal>jbosscmp-jdbc.xml</literal> is shown below."
+msgstr "下面是 <literal>jbosscmp-jdbc.xml</literal> 的 <literal>cmp-field</literal> 元素的完整内容模型。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:361
@@ -1660,161 +1096,74 @@
 #. Tag: para
 #: The_CMP_Engine.xml:374
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">field-name</emphasis>: This required element is the "
-"name of the <literal>cmp-field</literal> that is being configured. It must "
-"match the <literal>field-name</literal> element of a <literal>cmp-field</"
-"literal> declared for this entity in the <literal>ejb-jar.xml</literal> file."
-msgstr ""
-"<emphasis role=\"bold\">field-name</emphasis>:这个必需元素是需要配置的 "
-"<literal>cmp-field</literal> 的名字。它必须符合在 <literal>ejb-jar.xml</"
-"literal> 文件里声明的 <literal>cmp-field</literal> 的 <literal>field-name</"
-"literal> 元素的值。 "
+msgid "<emphasis role=\"bold\">field-name</emphasis>: This required element is the name of the <literal>cmp-field</literal> that is being configured. It must match the <literal>field-name</literal> element of a <literal>cmp-field</literal> declared for this entity in the <literal>ejb-jar.xml</literal> file."
+msgstr "<emphasis role=\"bold\">field-name</emphasis>:这个必需元素是需要配置的 <literal>cmp-field</literal> 的名字。它必须符合在 <literal>ejb-jar.xml</literal> 文件里声明的 <literal>cmp-field</literal> 的 <literal>field-name</literal> 元素的值。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:379
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-only</emphasis>: This declares that field in "
-"question is read-only. This field will not be written to the database by "
-"JBoss. Read-only fields are discussed in <xref linkend=\"CMP_Fields-"
-"Read_only_Fields\"/>."
-msgstr ""
-"<emphasis role=\"bold\">read-only</emphasis>:这声明该字段为只读。JBoss 将不"
-"能把这个字段写入数据库。只读字段会在 <xref linkend=\"CMP_Fields-"
-"Read_only_Fields\"/> 里进行讨论。 "
+msgid "<emphasis role=\"bold\">read-only</emphasis>: This declares that field in question is read-only. This field will not be written to the database by JBoss. Read-only fields are discussed in <xref linkend=\"CMP_Fields-Read_only_Fields\"/>."
+msgstr "<emphasis role=\"bold\">read-only</emphasis>:这声明该字段为只读。JBoss 将不能把这个字段写入数据库。只读字段会在 <xref linkend=\"CMP_Fields-Read_only_Fields\"/> 里进行讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:384
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-only-timeout</emphasis>: This is the time in "
-"milliseconds that a read-only field value will be considered valid."
-msgstr ""
-"<emphasis role=\"bold\">read-only-timeout</emphasis>:只读字段的值的有效期,"
-"单位为毫秒。 "
+msgid "<emphasis role=\"bold\">read-only-timeout</emphasis>: This is the time in milliseconds that a read-only field value will be considered valid."
+msgstr "<emphasis role=\"bold\">read-only-timeout</emphasis>:只读字段的值的有效期,单位为毫秒。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:389
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">column-name</emphasis>: This optional element is the "
-"name of the column to which the <literal>cmp-field</literal> is mapped. The "
-"default is to use the <literal>field-name</literal> value."
-msgstr ""
-"<emphasis role=\"bold\">column-name</emphasis>:是一个可选属性,它指定了 "
-"<literal>cmp-field</literal> 所映射的列的名字。它缺省使用 <literal>field-"
-"name</literal> 的值。 "
+msgid "<emphasis role=\"bold\">column-name</emphasis>: This optional element is the name of the column to which the <literal>cmp-field</literal> is mapped. The default is to use the <literal>field-name</literal> value."
+msgstr "<emphasis role=\"bold\">column-name</emphasis>:是一个可选属性,它指定了 <literal>cmp-field</literal> 所映射的列的名字。它缺省使用 <literal>field-name</literal> 的值。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:394
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">not-null</emphasis>: This optional element indicates "
-"that JBoss should add a NOT NULL to the end of the column declaration when "
-"automatically creating the table for this entity. The default for primary "
-"key fields and primitives is not null."
-msgstr ""
-"<emphasis role=\"bold\">not-null</emphasis>:这个可选元素指定 JBoss 为这个 "
-"entity 自动创建表时应该在列声明结尾添加一个非空值(NOT NULL)。主键字段和原始"
-"类型的缺省值都是非空值。 "
+msgid "<emphasis role=\"bold\">not-null</emphasis>: This optional element indicates that JBoss should add a NOT NULL to the end of the column declaration when automatically creating the table for this entity. The default for primary key fields and primitives is not null."
+msgstr "<emphasis role=\"bold\">not-null</emphasis>:这个可选元素指定 JBoss 为这个 entity 自动创建表时应该在列声明结尾添加一个非空值(NOT NULL)。主键字段和原始类型的缺省值都是非空值。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:399
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">jdbc-type</emphasis>: This is the JDBC type that is "
-"used when setting parameters in a JDBC prepared statement or loading data "
-"from a JDBC result set. The valid types are defined in <literal>java.sql."
-"Types</literal>. This is only required if <literal>sql-type</literal> is "
-"specified. The default JDBC type will be based on the database type in the "
-"<literal>datasourcemapping</literal>."
-msgstr ""
-"<emphasis role=\"bold\">jdbc-type</emphasis>:这是在设置 JDBC prepared 语句或"
-"从 JDBC 结果集里载入数据时使用的 JDBC 类型。其有效值在 <literal>java.sql."
-"Types</literal> 里定义。它只有在指定了 <literal>sql-type</literal> 时才需要。"
-"缺省的 JDBC 类型将基于 <literal>datasourcemapping</literal> 里的数据库类型。 "
+msgid "<emphasis role=\"bold\">jdbc-type</emphasis>: This is the JDBC type that is used when setting parameters in a JDBC prepared statement or loading data from a JDBC result set. The valid types are defined in <literal>java.sql.Types</literal>. This is only required if <literal>sql-type</literal> is specified. The default JDBC type will be based on the database type in the <literal>datasourcemapping</literal>."
+msgstr "<emphasis role=\"bold\">jdbc-type</emphasis>:这是在设置 JDBC prepared 语句或从 JDBC 结果集里载入数据时使用的 JDBC 类型。其有效值在 <literal>java.sql.Types</literal> 里定义。它只有在指定了 <literal>sql-type</literal> 时才需要。缺省的 JDBC 类型将基于 <literal>datasourcemapping</literal> 里的数据库类型。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:404
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">sql-type</emphasis>: This is the SQL type that is "
-"used in create table statements for this field. Valid SQL types are only "
-"limited by your database vendor. This is only required if <literal>jdbc-"
-"type</literal> is specified. The default SQL type will be base on the "
-"database type in the <literal>datasourcemapping</literal>"
-msgstr ""
-"<emphasis role=\"bold\">sql-type</emphasis>:这是在 create table 语句里使用"
-"的 SQL 类型。它只有在指定了 <literal>jdbc-type</literal> 时才需要。缺省的 "
-"SQL 类型将基于 <literal>datasourcemapping</literal> 里的类型。 "
+msgid "<emphasis role=\"bold\">sql-type</emphasis>: This is the SQL type that is used in create table statements for this field. Valid SQL types are only limited by your database vendor. This is only required if <literal>jdbc-type</literal> is specified. The default SQL type will be base on the database type in the <literal>datasourcemapping</literal>"
+msgstr "<emphasis role=\"bold\">sql-type</emphasis>:这是在 create table 语句里使用的 SQL 类型。它只有在指定了 <literal>jdbc-type</literal> 时才需要。缺省的 SQL 类型将基于 <literal>datasourcemapping</literal> 里的类型。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:409
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">property</emphasis>: This optional element allows "
-"one to define how the properties of a dependent value class CMP field should "
-"be mapped to the persistent store. This is discussed further in <xref "
-"linkend=\"CMP_Fields-Dependent_Value_Classes_DVCs\"/>."
-msgstr ""
-"<emphasis role=\"bold\">property</emphasis>:这个可选元素允许你定义 "
-"dependent value 类的 CMP 字段的属性怎样映射到持久性存储。<xref linkend="
-"\"CMP_Fields-Dependent_Value_Classes_DVCs\"/> 里将对它进行进一步讨论。 "
+msgid "<emphasis role=\"bold\">property</emphasis>: This optional element allows one to define how the properties of a dependent value class CMP field should be mapped to the persistent store. This is discussed further in <xref linkend=\"CMP_Fields-Dependent_Value_Classes_DVCs\"/>."
+msgstr "<emphasis role=\"bold\">property</emphasis>:这个可选元素允许你定义 dependent value 类的 CMP 字段的属性怎样映射到持久性存储。<xref linkend=\"CMP_Fields-Dependent_Value_Classes_DVCs\"/> 里将对它进行进一步讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:414
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">auto-increment</emphasis>: The presence of this "
-"optional field indicates that it is automatically incremented by the "
-"database layer. This is used to map a field to a generated column as well as "
-"to an externally manipulated column."
-msgstr ""
-"<emphasis role=\"bold\">auto-increment</emphasis>:这个可选字段指定数据库层进"
-"行自动递增。它被用来把字段映射到生成的列以及外部操作的列。 "
+msgid "<emphasis role=\"bold\">auto-increment</emphasis>: The presence of this optional field indicates that it is automatically incremented by the database layer. This is used to map a field to a generated column as well as to an externally manipulated column."
+msgstr "<emphasis role=\"bold\">auto-increment</emphasis>:这个可选字段指定数据库层进行自动递增。它被用来把字段映射到生成的列以及外部操作的列。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:419
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">dbindex</emphasis>: The presence of this optional "
-"field indicates that the server should create an index on the corresponding "
-"column in the database. The index name will be fieldname_index."
-msgstr ""
-"<emphasis role=\"bold\">dbindex</emphasis>:这个可选字段指定服务器应该创建数"
-"据库里对应的列的索引。索引名将为 fieldname_index。 "
+msgid "<emphasis role=\"bold\">dbindex</emphasis>: The presence of this optional field indicates that the server should create an index on the corresponding column in the database. The index name will be fieldname_index."
+msgstr "<emphasis role=\"bold\">dbindex</emphasis>:这个可选字段指定服务器应该创建数据库里对应的列的索引。索引名将为 fieldname_index。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:424
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">check-dirty-after-get</emphasis>: This value "
-"defaults to false for primitive types and the basic java.lang immutable "
-"wrappers (<literal>Integer</literal>, <literal>String</literal>, etc...). "
-"For potentially mutable objects, JBoss will mark they field as potentially "
-"dirty after a get operation. If the dirty check on an object is too "
-"expensive, you can optimize it away by setting <literal>check-dirty-after-"
-"get</literal> to false."
-msgstr ""
-"<emphasis role=\"bold\">check-dirty-after-get</emphasis>:对于原始类型和基本"
-"çš„ java.lang immutable wrappers (<literal>Integer</literal>, "
-"<literal>String</literal>, etc...) 来说,这个值缺省为 false。对于潜在的易变对"
-"象,在 get 操作后 JBoss 将把其字段标记为潜在的 dirty。如果 dirty 检查代价过"
-"大,你可以把 <literal>check-dirty-after-get</literal> 设为 false 来进行优化。 "
+msgid "<emphasis role=\"bold\">check-dirty-after-get</emphasis>: This value defaults to false for primitive types and the basic java.lang immutable wrappers (<literal>Integer</literal>, <literal>String</literal>, etc...). For potentially mutable objects, JBoss will mark they field as potentially dirty after a get operation. If the dirty check on an object is too expensive, you can optimize it away by setting <literal>check-dirty-after-get</literal> to false."
+msgstr "<emphasis role=\"bold\">check-dirty-after-get</emphasis>:对于原始类型和基本的 java.lang immutable wrappers (<literal>Integer</literal>, <literal>String</literal>, etc...) 来说,这个值缺省为 false。对于潜在的易变对象,在 get 操作后 JBoss 将把其字段标记为潜在的 dirty。如果 dirty 检查代价过大,你可以把 <literal>check-dirty-after-get</literal> 设为 false 来进行优化。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:429
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">state-factory</emphasis>: This specifies class name "
-"of a state factory object which can perform dirty checking for this field. "
-"State factory classes must implement the <literal>CMPFieldStateFactory</"
-"literal> interface."
-msgstr ""
-"<emphasis role=\"bold\">state-factory</emphasis>:它指定状态工厂(state "
-"factory)对象的类名,这个对象可以对该字段进行脏检查(dirty checking)。状态工"
-"厂类必须实现 <literal>CMPFieldStateFactory</literal> 接口。 "
+msgid "<emphasis role=\"bold\">state-factory</emphasis>: This specifies class name of a state factory object which can perform dirty checking for this field. State factory classes must implement the <literal>CMPFieldStateFactory</literal> interface."
+msgstr "<emphasis role=\"bold\">state-factory</emphasis>:它指定状态工厂(state factory)对象的类名,这个对象可以对该字段进行脏检查(dirty checking)。状态工厂类必须实现 <literal>CMPFieldStateFactory</literal> 接口。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:437
@@ -1825,26 +1174,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:438
 #, no-c-format
-msgid ""
-"JBoss allows for read-only CMP fields by setting the <literal>read-only</"
-"literal> and <literal>read-time-out</literal> elements in the <literal>cmp-"
-"field</literal> declaration. These elements work the same way as they do at "
-"the entity level. If a field is read-only, it will never be used in an "
-"<literal>INSERT</literal> or <literal>UPDATE</literal> statement. If a "
-"primary key field is <literal>read-only</literal>, the create method will "
-"throw a <literal>CreateException</literal>. If a set accessor is called for "
-"a read-only field, it throws an <literal>EJBException</literal>. Read-only "
-"fields are useful for fields that are filled in by database triggers, such "
-"as last update. A read-only CMP field declaration example follows:"
-msgstr ""
-"JBoss 可以设置 <literal>cmp-field</literal> 声明里的 <literal>read-only</"
-"literal> 和 <literal>read-time-out</literal> 元素来声明只读 CMP 字段。这些元"
-"素和 entity 级别的一样。如果字段为只读,它不能在 <literal>INSERT</literal> "
-"或 <literal>UPDATE</literal> 语句里使用。如果主键字段是<literal>只读</"
-"literal>的,那么 create 方法将抛出 <literal>CreateException</literal>。如果对"
-"只读字段调用 set 方法,它将抛出 <literal>EJBException</literal>。只读属性对于"
-"通过数据库触发器(trigger)填值的字段很有用,如最近的更新。下面是一个只读的 "
-"CMP 字段声明示例: "
+msgid "JBoss allows for read-only CMP fields by setting the <literal>read-only</literal> and <literal>read-time-out</literal> elements in the <literal>cmp-field</literal> declaration. These elements work the same way as they do at the entity level. If a field is read-only, it will never be used in an <literal>INSERT</literal> or <literal>UPDATE</literal> statement. If a primary key field is <literal>read-only</literal>, the create method will throw a <literal>CreateException</literal>. If a set accessor is called for a read-only field, it throws an <literal>EJBException</literal>. Read-only fields are useful for fields that are filled in by database triggers, such as last update. A read-only CMP field declaration example follows:"
+msgstr "JBoss 可以设置 <literal>cmp-field</literal> 声明里的 <literal>read-only</literal> 和 <literal>read-time-out</literal> 元素来声明只读 CMP 字段。这些元素和 entity 级别的一样。如果字段为只读,它不能在 <literal>INSERT</literal> 或 <literal>UPDATE</literal> 语句里使用。如果主键字段是<literal>只读</literal>的,那么 create 方法将抛出 <literal>CreateException</literal>。如果对只读字段调用 set 方法,它将抛出 <literal>EJBException</literal>。只读属性对于通过数据库触发器(trigger)填值的字段很有用,如最近的更新。下面是一个只读的 CMP 字段声明示例: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:441
@@ -1885,18 +1216,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:446
 #, no-c-format
-msgid ""
-"The <literal>audit</literal> element of the entity section allows one to "
-"specify how access to and entity bean is audited. This is only allowed when "
-"an entity bean is accessed under a security domain so that this is a caller "
-"identity established. The content model of the audit element is given <xref "
-"linkend=\"Auditing_Entity_Access-The_jbosscmp_jdbc."
-"xml_audit_element_content_model\"/>."
-msgstr ""
-"entity 部分的 <literal>audit</literal> 元素允许你指定如何审计对 entity bean "
-"的访问。这只有 entity bean 通过安全域访问时才被允许,所以要建立一个调用者标"
-"识。<xref linkend=\"Auditing_Entity_Access-The_jbosscmp_jdbc."
-"xml_audit_element_content_model\"/> 给出了 audit 元素的内容模型。 "
+msgid "The <literal>audit</literal> element of the entity section allows one to specify how access to and entity bean is audited. This is only allowed when an entity bean is accessed under a security domain so that this is a caller identity established. The content model of the audit element is given <xref linkend=\"Auditing_Entity_Access-The_jbosscmp_jdbc.xml_audit_element_content_model\"/>."
+msgstr "entity 部分的 <literal>audit</literal> 元素允许你指定如何审计对 entity bean 的访问。这只有 entity bean 通过安全域访问时才被允许,所以要建立一个调用者标识。<xref linkend=\"Auditing_Entity_Access-The_jbosscmp_jdbc.xml_audit_element_content_model\"/> 给出了 audit 元素的内容模型。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:450
@@ -1907,89 +1228,38 @@
 #. Tag: para
 #: The_CMP_Engine.xml:459
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">created-by</emphasis>: This optional element "
-"indicates that the caller who created the entity should be saved to either "
-"the indicated <literal>column-name</literal> or cmp <literal>field-name</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">created-by</emphasis>:这个可选元素指出创建 entity 的"
-"调用者应该保存为指定的 <literal>column-name</literal> 或 CMP 的 "
-"<literal>field-name</literal>。 "
+msgid "<emphasis role=\"bold\">created-by</emphasis>: This optional element indicates that the caller who created the entity should be saved to either the indicated <literal>column-name</literal> or cmp <literal>field-name</literal>."
+msgstr "<emphasis role=\"bold\">created-by</emphasis>:这个可选元素指出创建 entity 的调用者应该保存为指定的 <literal>column-name</literal> 或 CMP 的 <literal>field-name</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:464
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">created-time</emphasis>: This optional element "
-"indicates that the time of entity creation should be saved to either the "
-"indicated <literal>column-name</literal> or cmp <literal>field-name</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">created-time</emphasis>:这个可选元素指定 entity 创建"
-"的时间应该保存为 <literal>column-name</literal> 或 cmp <literal>field-name</"
-"literal>。 "
+msgid "<emphasis role=\"bold\">created-time</emphasis>: This optional element indicates that the time of entity creation should be saved to either the indicated <literal>column-name</literal> or cmp <literal>field-name</literal>."
+msgstr "<emphasis role=\"bold\">created-time</emphasis>:这个可选元素指定 entity 创建的时间应该保存为 <literal>column-name</literal> 或 cmp <literal>field-name</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:469
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">updated-by</emphasis>: This optional element "
-"indicates that the caller who last modified the entity should be saved to "
-"either the indicated <literal>column-name</literal> or CMP <literal>field-"
-"name</literal>."
-msgstr ""
-"<emphasis role=\"bold\">updated-by</emphasis>:这个可选元素指定最后修改 "
-"entity 的调用者应该保存在指定的 <literal>column-name</literal> 或 CMP "
-"<literal>field-name</literal>。 "
+msgid "<emphasis role=\"bold\">updated-by</emphasis>: This optional element indicates that the caller who last modified the entity should be saved to either the indicated <literal>column-name</literal> or CMP <literal>field-name</literal>."
+msgstr "<emphasis role=\"bold\">updated-by</emphasis>:这个可选元素指定最后修改 entity 的调用者应该保存在指定的 <literal>column-name</literal> 或 CMP <literal>field-name</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:474
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">updated-time</emphasis>: This optional element "
-"indicates that the last time of entity modification should be saved to "
-"either the indicated <literal>column-name</literal> or CMP <literal>field-"
-"name</literal>."
-msgstr ""
-"<emphasis role=\"bold\">LenientEjbLink</emphasis>:这个可选元素指定最后一次"
-"对 entity 的修改应该保存到指定的 <literal>column-name</literal> 或 CMP "
-"<literal>field-name</literal> 里。 "
+msgid "<emphasis role=\"bold\">updated-time</emphasis>: This optional element indicates that the last time of entity modification should be saved to either the indicated <literal>column-name</literal> or CMP <literal>field-name</literal>."
+msgstr "<emphasis role=\"bold\">LenientEjbLink</emphasis>:这个可选元素指定最后一次对 entity 的修改应该保存到指定的 <literal>column-name</literal> 或 CMP <literal>field-name</literal> 里。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:479
 #, no-c-format
-msgid ""
-"For each element, if a <literal>field-name</literal> is given, the "
-"corresponding audit information should be stored in the specified CMP field "
-"of the entity bean being accessed. Note that there does not have to be an "
-"corresponding CMP field declared on the entity. In case there are matching "
-"field names, you will be able to access audit fields in the application "
-"using the corresponding CMP field abstract getters and setters. Otherwise, "
-"the audit fields will be created and added to the entity internally. You "
-"will be able to access audit information in EJB-QL queries using the audit "
-"field names, but not directly through the entity accessors."
-msgstr ""
-"对于每个元素,如果给定了 <literal>field-name</literal>,相应的审计信息应该保"
-"存在被访问的 entity bean 的指定 CMP 字段里。请注意,你并不需要在这个 entity "
-"上声明相应的 CMP 字段。如果有匹配的字段名,你就可以在应用程序里用对应的 CMP "
-"字段的 abstract getter 和 setter 方法来访问审计字段。否则,审计字段将被创建并"
-"添加到 entity 内部。你可以在 EJB-QL 查询通过审计字段访问审计信息,但不能直接"
-"用 entity 的 accessor 进行访问。 "
+msgid "For each element, if a <literal>field-name</literal> is given, the corresponding audit information should be stored in the specified CMP field of the entity bean being accessed. Note that there does not have to be an corresponding CMP field declared on the entity. In case there are matching field names, you will be able to access audit fields in the application using the corresponding CMP field abstract getters and setters. Otherwise, the audit fields will be created and added to the entity internally. You will be able to access audit information in EJB-QL queries using the audit field names, but not directly through the entity accessors."
+msgstr "对于每个元素,如果给定了 <literal>field-name</literal>,相应的审计信息应该保存在被访问的 entity bean 的指定 CMP 字段里。请注意,你并不需要在这个 entity 上声明相应的 CMP 字段。如果有匹配的字段名,你就可以在应用程序里用对应的 CMP 字段的 abstract getter 和 setter 方法来访问审计字段。否则,审计字段将被创建并添加到 entity 内部。你可以在 EJB-QL 查询通过审计字段访问审计信息,但不能直接用 entity 的 accessor 进行访问。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:482
 #, no-c-format
-msgid ""
-"If, on the other hand, a <literal>column-name</literal> is specified, the "
-"corresponding audit information should be stored in the indicated column of "
-"the entity table. If JBoss is creating the table the <literal>jdbc-type</"
-"literal> and <literal>sql-type</literal> element can then be used to define "
-"the storage type."
-msgstr ""
-"从另外一方面将,如果指定了 <literal>column-name</literal>,对应的审计信息应该"
-"存储在 entity 表里指定的列里。如果 JBoss 正在创建表,<literal>jdbc-type</"
-"literal> 和 <literal>sql-type</literal> 元素可以用来定义存储类型。 "
+msgid "If, on the other hand, a <literal>column-name</literal> is specified, the corresponding audit information should be stored in the indicated column of the entity table. If JBoss is creating the table the <literal>jdbc-type</literal> and <literal>sql-type</literal> element can then be used to define the storage type."
+msgstr "从另外一方面将,如果指定了 <literal>column-name</literal>,对应的审计信息应该存储在 entity 表里指定的列里。如果 JBoss 正在创建表,<literal>jdbc-type</literal> 和 <literal>sql-type</literal> 元素可以用来定义存储类型。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:485
@@ -2014,8 +1284,7 @@
 "                    &lt;column-name&gt;createdtime&lt;/column-name&gt;\n"
 "                &lt;/created-time&gt;\n"
 "                &lt;updated-by&gt;\n"
-"                    &lt;column-name&gt;updatedby&lt;/column-name&gt;&lt;/"
-"updated-by&gt;\n"
+"                    &lt;column-name&gt;updatedby&lt;/column-name&gt;&lt;/updated-by&gt;\n"
 "                &lt;updated-time&gt;\n"
 "                    &lt;column-name&gt;updatedtime&lt;/column-name&gt;\n"
 "                &lt;/updated-time&gt;\n"
@@ -2037,8 +1306,7 @@
 "                    &lt;column-name&gt;createdtime&lt;/column-name&gt;\n"
 "                &lt;/created-time&gt;\n"
 "                &lt;updated-by&gt;\n"
-"                    &lt;column-name&gt;updatedby&lt;/column-name&gt;&lt;/"
-"updated-by&gt;\n"
+"                    &lt;column-name&gt;updatedby&lt;/column-name&gt;&lt;/updated-by&gt;\n"
 "                &lt;updated-time&gt;\n"
 "                    &lt;column-name&gt;updatedtime&lt;/column-name&gt;\n"
 "                &lt;/updated-time&gt;\n"
@@ -2056,59 +1324,20 @@
 #. Tag: para
 #: The_CMP_Engine.xml:493
 #, no-c-format
-msgid ""
-"A dependent value class (DVC) is a fancy term used to identity any Java "
-"class that is the type of a <literal>cmp-field</literal> other than the "
-"automatically recognized types core types such as strings and number values. "
-"By default, a DVC is serialized, and the serialized form is stored in a "
-"single database column. Although not discussed here, there are several known "
-"issues with the long-term storage of classes in serialized form."
-msgstr ""
-"Dependent value 类(DVC)是用来识别类型为某个 <literal>cmp-field</literal> 而"
-"不是可自动识别的核心类型如 String 或数字值的 Java 类。在缺省情况下,DVC 是可"
-"序列化的,且序列化的格式保存在单个的数据库列里。虽然我们在这里不会进行讨论,"
-"但以序列化形式对类进行长期保存有几个已知的问题。 "
+msgid "A dependent value class (DVC) is a fancy term used to identity any Java class that is the type of a <literal>cmp-field</literal> other than the automatically recognized types core types such as strings and number values. By default, a DVC is serialized, and the serialized form is stored in a single database column. Although not discussed here, there are several known issues with the long-term storage of classes in serialized form."
+msgstr "Dependent value 类(DVC)是用来识别类型为某个 <literal>cmp-field</literal> 而不是可自动识别的核心类型如 String 或数字值的 Java 类。在缺省情况下,DVC 是可序列化的,且序列化的格式保存在单个的数据库列里。虽然我们在这里不会进行讨论,但以序列化形式对类进行长期保存有几个已知的问题。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:496
 #, no-c-format
-msgid ""
-"JBoss also supports the storage of the internal data of a DVC into one or "
-"more columns. This is useful for supporting legacy JavaBeans and database "
-"structures. It is not uncommon to find a database with a highly flattened "
-"structure (e.g., a <literal>PURCHASE_ORDER</literal> table with the fields "
-"<literal>SHIP_LINE1</literal>, <literal>SHIP_LINE2</literal>, "
-"<literal>SHIP_CITY</literal>, etc. and an additional set of fields for the "
-"billing address). Other common database structures include telephone numbers "
-"with separate fields for area code, exchange, and extension, or a person&#39;"
-"s name spread across several fields. With a DVC, multiple columns can be "
-"mapped to one logical field."
-msgstr ""
-"JBoss 也支持把 DVC 的内部数据保存到一个或多列里。这对于支持遗留的 JavaBean 和"
-"数据库结构很有用。具有高度平行结构的数据库(如带有字段 <literal>SHIP_LINE1</"
-"literal>、<literal>SHIP_LINE2</literal>、<literal>SHIP_CITY</literal> 等并用"
-"于帐单地址的另外一系列字段的 <literal>PURCHASE_ORDER</literal> 表)并不少见。"
-"其他常见的数据库结构包括带有独立的地区、总机、分机字段的电话号码,或者跨多个"
-"字段的名称。使用 DVC,你可以把多列映射至一个逻辑字段。 "
+msgid "JBoss also supports the storage of the internal data of a DVC into one or more columns. This is useful for supporting legacy JavaBeans and database structures. It is not uncommon to find a database with a highly flattened structure (e.g., a <literal>PURCHASE_ORDER</literal> table with the fields <literal>SHIP_LINE1</literal>, <literal>SHIP_LINE2</literal>, <literal>SHIP_CITY</literal>, etc. and an additional set of fields for the billing address). Other common database structures include telephone numbers with separate fields for area code, exchange, and extension, or a person&#39;s name spread across several fields. With a DVC, multiple columns can be mapped to one logical field."
+msgstr "JBoss 也支持把 DVC 的内部数据保存到一个或多列里。这对于支持遗留的 JavaBean 和数据库结构很有用。具有高度平行结构的数据库(如带有字段 <literal>SHIP_LINE1</literal>、<literal>SHIP_LINE2</literal>、<literal>SHIP_CITY</literal> 等并用于帐单地址的另外一系列字段的 <literal>PURCHASE_ORDER</literal> 表)并不少见。其他常见的数据库结构包括带有独立的地区、总机、分机字段的电话号码,或者跨多个字段的名称。使用 DVC,你可以把多列映射至一个逻辑字段。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:499
 #, no-c-format
-msgid ""
-"JBoss requires that a DVC to be mapped must follow the JavaBeans naming "
-"specification for simple properties, and that each property to be stored in "
-"the database must have both a getter and a setter method. Furthermore, the "
-"bean must be serializable and must have a no argument constructor. A "
-"property can be any simple type, an unmapped DVC or a mapped DVC, but cannot "
-"be an EJB. A DVC mapping is specified in a <literal>dependent-value-class</"
-"literal> element within the <literal>dependent-value-classes</literal> "
-"element."
-msgstr ""
-"JBoss 要求 DVC 的映射必须遵循 JavaBean 用于简单属性的命名规则,以及每个存储在"
-"数据库里的属性都必须有 getter 和 setter 方法。而且,这个 bean 序列化且必须有"
-"一个无参数的构造函数。属性可以为任何简单类型,未映射的 DVC 或映射的 DVC,但不"
-"能是 EJB。DVC 映射在 <literal>dependent-value-classes</literal> 元素的 "
-"<literal>dependent-value-class</literal> 元素里进行指定。 "
+msgid "JBoss requires that a DVC to be mapped must follow the JavaBeans naming specification for simple properties, and that each property to be stored in the database must have both a getter and a setter method. Furthermore, the bean must be serializable and must have a no argument constructor. A property can be any simple type, an unmapped DVC or a mapped DVC, but cannot be an EJB. A DVC mapping is specified in a <literal>dependent-value-class</literal> element within the <literal>dependent-value-classes</literal> element."
+msgstr "JBoss 要求 DVC 的映射必须遵循 JavaBean 用于简单属性的命名规则,以及每个存储在数据库里的属性都必须有 getter 和 setter 方法。而且,这个 bean 序列化且必须有一个无参数的构造函数。属性可以为任何简单类型,未映射的 DVC 或映射的 DVC,但不能是 EJB。DVC 映射在 <literal>dependent-value-classes</literal> 元素的 <literal>dependent-value-class</literal> 元素里进行指定。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:503
@@ -2221,9 +1450,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:514
 #, no-c-format
-msgid ""
-"The contact info includes a phone number, which is represented by another "
-"DVC class."
+msgid "The contact info includes a phone number, which is represented by another DVC class."
 msgstr "这里的联系信息包括由另外一个 DVC 类表示的电话号码。 "
 
 #. Tag: programlisting
@@ -2353,52 +1580,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:522
 #, no-c-format
-msgid ""
-"Each DVC is declared with a <literal>dependent-value-class</literal> "
-"element. A DVC is identified by the Java class type declared in the class "
-"element. Each property to be persisted is declared with a property element. "
-"This specification is based on the <literal>cmp-field</literal> element, so "
-"it should be self-explanatory. This restriction will also be removed in a "
-"future release. The current proposal involves storing the primary key fields "
-"in the case of a local entity and the entity handle in the case of a remote "
-"entity."
-msgstr ""
-"每个 DVC 都用 <literal>dependent-value-class</literal> 元素进行声明。DVC 由 "
-"class 元素里声明的 Java 类的类型来标识。property 元素声明将被持久化的属性。这"
-"个规格是基于 <literal>cmp-field</literal> 元素的,所以不需加以说明。这个限制"
-"也将在将来的版本里删除。目前的计划包括在本地 entity 情况下保存主键字段而在远"
-"程 entity 情况下保存 entity 句柄。 "
+msgid "Each DVC is declared with a <literal>dependent-value-class</literal> element. A DVC is identified by the Java class type declared in the class element. Each property to be persisted is declared with a property element. This specification is based on the <literal>cmp-field</literal> element, so it should be self-explanatory. This restriction will also be removed in a future release. The current proposal involves storing the primary key fields in the case of a local entity and the entity handle in the case of a remote entity."
+msgstr "每个 DVC 都用 <literal>dependent-value-class</literal> 元素进行声明。DVC 由 class 元素里声明的 Java 类的类型来标识。property 元素声明将被持久化的属性。这个规格是基于 <literal>cmp-field</literal> 元素的,所以不需加以说明。这个限制也将在将来的版本里删除。目前的计划包括在本地 entity 情况下保存主键字段而在远程 entity 情况下保存 entity 句柄。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:525
 #, no-c-format
-msgid ""
-"The <literal>dependent-value-classes</literal> section defines the internal "
-"structure and default mapping of the classes. When JBoss encounters a field "
-"that has an unknown type, it searches the list of registered DVCs, and if a "
-"DVC is found, it persists this field into a set of columns, otherwise the "
-"field is stored in serialized form in a single column. JBoss does not "
-"support inheritance of DVCs; therefore, this search is only based on the "
-"declared type of the field. A DVC can be constructed from other DVCs, so "
-"when JBoss runs into a DVC, it flattens the DVC tree structure into a set of "
-"columns. If JBoss finds a DVC circuit during startup, it will throw an "
-"<literal>EJBException</literal>. The default column name of a property is "
-"the column name of the base <literal>cmp-field</literal> followed by an "
-"underscore and then the column name of the property. If the property is a "
-"DVC, the process is repeated. For example, a <literal>cmp-field</literal> "
-"named <literal>info</literal> that uses the <literal>ContactInfo</literal> "
-"DVC would have the following columns:"
-msgstr ""
-"<literal>dependent-value-classes</literal> 部分定义了这个类的内部结构和缺省映"
-"射。当 JBoss 遇到具有未知类型的字段时,它将搜索注册的 DVC 列表,如果找到了一"
-"个 DVC,它将以序列化的形式把这个字段存储在某个单列里。JBoss 不支持 DVC 的继"
-"承;因此,这种搜索只局限于已声明的类型。DVC 可以根据其他 DVC 来构造,所以当 "
-"JBoss 采用 DVC 时,它把 DVC 树的结构简化为一系列的列。如果 JBoss 在启动时发"
-"现 DVC 循环,它将抛出 <literal>EJBException</literal>。属性的缺省列名称是 "
-"<literal>cmp-field</literal> 的列名后接下划线,然后是属性的列名。如果这个属性"
-"是一个 DVC,这个过程将被重复。令人,名为 <literal>info</literal> 并使用 "
-"<literal>ContactInfo</literal> DVC  的 <literal>cmp-field</literal> 将具有下"
-"列的列: "
+msgid "The <literal>dependent-value-classes</literal> section defines the internal structure and default mapping of the classes. When JBoss encounters a field that has an unknown type, it searches the list of registered DVCs, and if a DVC is found, it persists this field into a set of columns, otherwise the field is stored in serialized form in a single column. JBoss does not support inheritance of DVCs; therefore, this search is only based on the declared type of the field. A DVC can be constructed from other DVCs, so when JBoss runs into a DVC, it flattens the DVC tree structure into a set of columns. If JBoss finds a DVC circuit during startup, it will throw an <literal>EJBException</literal>. The default column name of a property is the column name of the base <literal>cmp-field</literal> followed by an underscore and then the column name of the property. If the property is a DVC, the process is repeated. For example, a <literal>cmp-field</literal> named <literal>info</!
 literal> that uses the <literal>ContactInfo</literal> DVC would have the following columns:"
+msgstr "<literal>dependent-value-classes</literal> 部分定义了这个类的内部结构和缺省映射。当 JBoss 遇到具有未知类型的字段时,它将搜索注册的 DVC 列表,如果找到了一个 DVC,它将以序列化的形式把这个字段存储在某个单列里。JBoss 不支持 DVC 的继承;因此,这种搜索只局限于已声明的类型。DVC 可以根据其他 DVC 来构造,所以当 JBoss 采用 DVC 时,它把 DVC 树的结构简化为一系列的列。如果 JBoss 在启动时发现 DVC 循环,它将抛出 <literal>EJBException</literal>。属性的缺省列名称是 <literal>cmp-field</literal> 的列名后接下划线,然后是属性的列名。如果这个属性是一个 DVC,这个过程将被重复。令人,名为 <literal>info</literal> 并使用 <literal>ContactInfo</literal> DVC  的 <literal>cmp-field</literal> 将具有下列的列: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:528
@@ -2423,13 +1612,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:529
 #, no-c-format
-msgid ""
-"The automatically generated column names can quickly become excessively long "
-"and awkward. The default mappings of columns can be overridden in the entity "
-"element as follows:"
-msgstr ""
-"自动生成的列名可以很快变得很冗长且糟糕。如下所示,列的自动映射可以在 entity "
-"元素里进行覆盖: "
+msgid "The automatically generated column names can quickly become excessively long and awkward. The default mappings of columns can be overridden in the entity element as follows:"
+msgstr "自动生成的列名可以很快变得很冗长且糟糕。如下所示,列的自动映射可以在 entity 元素里进行覆盖: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:532
@@ -2442,34 +1626,28 @@
 "            &lt;cmp-field&gt;\n"
 "                &lt;field-name&gt;contactInfo&lt;/field-name&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;cell.areaCode&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;cell.areaCode&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;cell_area&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;cell.exchange&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;cell.exchange&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;cell_exch&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;cell.extension&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;cell.extension&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;cell_ext&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                \n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;pager.areaCode&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;pager.areaCode&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;page_area&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;pager.exchange&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;pager.exchange&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;page_exch&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;pager.extension&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;pager.extension&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;page_ext&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                 \n"
@@ -2491,34 +1669,28 @@
 "            &lt;cmp-field&gt;\n"
 "                &lt;field-name&gt;contactInfo&lt;/field-name&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;cell.areaCode&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;cell.areaCode&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;cell_area&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;cell.exchange&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;cell.exchange&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;cell_exch&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;cell.extension&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;cell.extension&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;cell_ext&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                \n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;pager.areaCode&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;pager.areaCode&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;page_area&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;pager.exchange&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;pager.exchange&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;page_exch&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                &lt;property&gt;\n"
-"                    &lt;property-name&gt;pager.extension&lt;/property-"
-"name&gt;\n"
+"                    &lt;property-name&gt;pager.extension&lt;/property-name&gt;\n"
 "                    &lt;column-name&gt;page_ext&lt;/column-name&gt;\n"
 "                &lt;/property&gt;\n"
 "                 \n"
@@ -2536,12 +1708,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:533
 #, no-c-format
-msgid ""
-"When overriding property info for the entity, you need to refer to the "
-"property from a flat perspective as in <literal>cell.areaCode</literal>."
-msgstr ""
-"当覆盖 entity 的属性信息时,你需要象 <literal>cell.areaCode</literal> 里一样"
-"从平面的角度来引用这个属性。 "
+msgid "When overriding property info for the entity, you need to refer to the property from a flat perspective as in <literal>cell.areaCode</literal>."
+msgstr "当覆盖 entity 的属性信息时,你需要象 <literal>cell.areaCode</literal> 里一样从平面的角度来引用这个属性。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:541
@@ -2552,42 +1720,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:542
 #, no-c-format
-msgid ""
-"Container Managed Relationships (CMRs) are a powerful new feature of CMP "
-"2.0. Programmers have been creating relationships between entity objects "
-"since EJB 1.0 was introduced (not to mention since the introduction of "
-"databases), but before CMP 2.0 the programmer had to write a lot of code for "
-"each relationship in order to extract the primary key of the related entity "
-"and store it in a pseudo foreign key field. The simplest relationships were "
-"tedious to code, and complex relationships with referential integrity "
-"required many hours to code. With CMP 2.0 there is no need to code "
-"relationships by hand. The container can manage one-to-one, one-to-many and "
-"many-to-many relationships, with referential integrity. One restriction with "
-"CMRs is that they are only defined between local interfaces. This means that "
-"a relationship cannot be created between two entities in separate "
-"applications, even in the same application server."
-msgstr ""
-"容器管理的关系(Container Managed Relationships,CMR)是 CMP 2.0 的一个强大功"
-"能。自从引入 EJB 1.0 后,程序员已经在创建 entity 对象之间的关系,但在 CMP "
-"2.0 出现之前,程序员不得不为每种关系编写大量代码并将之存储在伪外部键字段里。"
-"即使最简单的关系都需要冗长的代码,而带有引用完整性(referential integrity)的"
-"复杂关系则需要数小时的编码。而使用 CMP 2.0 不需要手工对关系进行编程。容器可以"
-"管理一对一、一对多和多对多的带有引用完整性的关系。CMR 的限制是它们只定义本地"
-"接口之间的关系。这意味着不能创建处于不同应用程序里的两个 entity 之间的关系,"
-"即使它们位于相同的应用服务器里。 "
+msgid "Container Managed Relationships (CMRs) are a powerful new feature of CMP 2.0. Programmers have been creating relationships between entity objects since EJB 1.0 was introduced (not to mention since the introduction of databases), but before CMP 2.0 the programmer had to write a lot of code for each relationship in order to extract the primary key of the related entity and store it in a pseudo foreign key field. The simplest relationships were tedious to code, and complex relationships with referential integrity required many hours to code. With CMP 2.0 there is no need to code relationships by hand. The container can manage one-to-one, one-to-many and many-to-many relationships, with referential integrity. One restriction with CMRs is that they are only defined between local interfaces. This means that a relationship cannot be created between two entities in separate applications, even in the same application server."
+msgstr "容器管理的关系(Container Managed Relationships,CMR)是 CMP 2.0 的一个强大功能。自从引入 EJB 1.0 后,程序员已经在创建 entity 对象之间的关系,但在 CMP 2.0 出现之前,程序员不得不为每种关系编写大量代码并将之存储在伪外部键字段里。即使最简单的关系都需要冗长的代码,而带有引用完整性(referential integrity)的复杂关系则需要数小时的编码。而使用 CMP 2.0 不需要手工对关系进行编程。容器可以管理一对一、一对多和多对多的带有引用完整性的关系。CMR 的限制是它们只定义本地接口之间的关系。这意味着不能创建处于不同应用程序里的两个 entity 之间的关系,即使它们位于相同的应用服务器里。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:545
 #, no-c-format
-msgid ""
-"There are two basic steps to create a container managed relationship: create "
-"the <literal>cmr-field</literal> abstract accessors and declare the "
-"relationship in the <literal>ejb-jar.xml</literal> file. The following two "
-"sections describe these steps."
-msgstr ""
-"创建容器管理的关系(container managed relationship)需要两个基本步骤:创建 "
-"<literal>cmr-field</literal> 的 abstract accessor 并在 <literal>ejb-jar.xml</"
-"literal> 文件里声明关系。下面的两节描述了这些步骤。 "
+msgid "There are two basic steps to create a container managed relationship: create the <literal>cmr-field</literal> abstract accessors and declare the relationship in the <literal>ejb-jar.xml</literal> file. The following two sections describe these steps."
+msgstr "创建容器管理的关系(container managed relationship)需要两个基本步骤:创建 <literal>cmr-field</literal> 的 abstract accessor 并在 <literal>ejb-jar.xml</literal> 文件里声明关系。下面的两节描述了这些步骤。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:549
@@ -2598,21 +1738,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:550
 #, no-c-format
-msgid ""
-"CMR-Field abstract accessors have the same signatures as <literal>cmp-"
-"fields</literal>, except that single-valued relationships must return the "
-"local interface of the related entity, and multi-valued relationships can "
-"only return a <literal>java.util.Collection</literal> (or <literal>java.util."
-"Set</literal>) object. For example, to declare a one-to-many relationship "
-"between organization and gangster, we declare the relationship from "
-"organization to gangster in the <literal>OrganizationBean</literal> class:"
-msgstr ""
-"CMR-Field 的 abstract accessor 具有和 <literal>cmp-fields</literal> 相同的签"
-"名,除了单一值的关系必须返回相关 entity 的本地接口,且多值的关系可以只返回一"
-"个 <literal>java.util.Collection</literal> (或 <literal>java.util.Set</"
-"literal>) 对象。例如,要声明 organization 和 gangster 之间的一个一对多的关"
-"系,我们可以在 <literal>OrganizationBean</literal> 类里声明 organization 到 "
-"gangster 的关系: "
+msgid "CMR-Field abstract accessors have the same signatures as <literal>cmp-fields</literal>, except that single-valued relationships must return the local interface of the related entity, and multi-valued relationships can only return a <literal>java.util.Collection</literal> (or <literal>java.util.Set</literal>) object. For example, to declare a one-to-many relationship between organization and gangster, we declare the relationship from organization to gangster in the <literal>OrganizationBean</literal> class:"
+msgstr "CMR-Field 的 abstract accessor 具有和 <literal>cmp-fields</literal> 相同的签名,除了单一值的关系必须返回相关 entity 的本地接口,且多值的关系可以只返回一个 <literal>java.util.Collection</literal> (或 <literal>java.util.Set</literal>) 对象。例如,要声明 organization 和 gangster 之间的一个一对多的关系,我们可以在 <literal>OrganizationBean</literal> 类里声明 organization 到 gangster 的关系: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:553
@@ -2635,12 +1762,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:554
 #, no-c-format
-msgid ""
-"We also can declare the relationship from gangster to organization in the "
-"<literal>GangsterBean</literal> class:"
-msgstr ""
-"我们也可以在 <literal>GangsterBean</literal> 类里声明 gangster 到 "
-"organization 的关系: "
+msgid "We also can declare the relationship from gangster to organization in the <literal>GangsterBean</literal> class:"
+msgstr "我们也可以在 <literal>GangsterBean</literal> 类里声明 gangster 到 organization 的关系: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:557
@@ -2663,13 +1786,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:558
 #, no-c-format
-msgid ""
-"Although each bean declared a CMR field, only one of the two beans in a "
-"relationship must have a set of accessors. As with CMP fields, a CMR field "
-"is required to have both a getter and a setter method."
-msgstr ""
-"虽然每个 bean 都声明了一个 CMR 字段,但只有其中一个 bean 必须具有 accessor。"
-"和 CMP 字段相比,CMR 字段必须具有 getter 以及 setter 方法。 "
+msgid "Although each bean declared a CMR field, only one of the two beans in a relationship must have a set of accessors. As with CMP fields, a CMR field is required to have both a getter and a setter method."
+msgstr "虽然每个 bean 都声明了一个 CMR 字段,但只有其中一个 bean 必须具有 accessor。和 CMP 字段相比,CMR 字段必须具有 getter 以及 setter 方法。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:564
@@ -2680,16 +1798,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:565
 #, no-c-format
-msgid ""
-"The declaration of relationships in the <literal>ejb-jar.xml</literal> file "
-"is complicated and error prone. Although we recommend using a tool like "
-"XDoclet to manage the deployment descriptors for CMR fields, it&#39;s still "
-"important to understand how the descriptor works. The following illustrates "
-"the declaration of the organization/gangster relationship:"
-msgstr ""
-"<literal>ejb-jar.xml</literal> 文件里的关系声明比较复杂且容易出错。虽然我们推"
-"荐使用工具(如 XDoclet)来管理 CMR 字段的部署描述符,理解描述符的内容仍然重"
-"要。下面演示了对 organization/gangster 关系的声明: "
+msgid "The declaration of relationships in the <literal>ejb-jar.xml</literal> file is complicated and error prone. Although we recommend using a tool like XDoclet to manage the deployment descriptors for CMR fields, it&#39;s still important to understand how the descriptor works. The following illustrates the declaration of the organization/gangster relationship:"
+msgstr "<literal>ejb-jar.xml</literal> 文件里的关系声明比较复杂且容易出错。虽然我们推荐使用工具(如 XDoclet)来管理 CMR 字段的部署描述符,理解描述符的内容仍然重要。下面演示了对 organization/gangster 关系的声明: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:568
@@ -2698,20 +1808,16 @@
 "&lt;ejb-jar&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-name&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;org-has-gangsters &lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;org-has-gangsters &lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;multiplicity&gt;One&lt;/multiplicity&gt;\n"
 "                &lt;relationship-role-source&gt;\n"
 "                    &lt;ejb-name&gt;OrganizationEJB&lt;/ejb-name&gt;\n"
 "                &lt;/relationship-role-source&gt;\n"
 "                &lt;cmr-field&gt;\n"
-"                    &lt;cmr-field-name&gt;memberGangsters&lt;/cmr-field-"
-"name&gt;\n"
-"                    &lt;cmr-field-type&gt;java.util.Set&lt;/cmr-field-"
-"type&gt;\n"
+"                    &lt;cmr-field-name&gt;memberGangsters&lt;/cmr-field-name&gt;\n"
+"                    &lt;cmr-field-type&gt;java.util.Set&lt;/cmr-field-type&gt;\n"
 "                &lt;/cmr-field&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
@@ -2724,8 +1830,7 @@
 "                    &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "                &lt;/relationship-role-source&gt;\n"
 "                &lt;cmr-field&gt;\n"
-"                    &lt;cmr-field-name&gt;organization&lt;/cmr-field-"
-"name&gt;\n"
+"                    &lt;cmr-field-name&gt;organization&lt;/cmr-field-name&gt;\n"
 "                &lt;/cmr-field&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "        &lt;/ejb-relation&gt;\n"
@@ -2735,20 +1840,16 @@
 "&lt;ejb-jar&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-name&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;org-has-gangsters &lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;org-has-gangsters &lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;multiplicity&gt;One&lt;/multiplicity&gt;\n"
 "                &lt;relationship-role-source&gt;\n"
 "                    &lt;ejb-name&gt;OrganizationEJB&lt;/ejb-name&gt;\n"
 "                &lt;/relationship-role-source&gt;\n"
 "                &lt;cmr-field&gt;\n"
-"                    &lt;cmr-field-name&gt;memberGangsters&lt;/cmr-field-"
-"name&gt;\n"
-"                    &lt;cmr-field-type&gt;java.util.Set&lt;/cmr-field-"
-"type&gt;\n"
+"                    &lt;cmr-field-name&gt;memberGangsters&lt;/cmr-field-name&gt;\n"
+"                    &lt;cmr-field-type&gt;java.util.Set&lt;/cmr-field-type&gt;\n"
 "                &lt;/cmr-field&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
@@ -2761,8 +1862,7 @@
 "                    &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "                &lt;/relationship-role-source&gt;\n"
 "                &lt;cmr-field&gt;\n"
-"                    &lt;cmr-field-name&gt;organization&lt;/cmr-field-"
-"name&gt;\n"
+"                    &lt;cmr-field-name&gt;organization&lt;/cmr-field-name&gt;\n"
 "                &lt;/cmr-field&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "        &lt;/ejb-relation&gt;\n"
@@ -2772,68 +1872,26 @@
 #. Tag: para
 #: The_CMP_Engine.xml:569
 #, no-c-format
-msgid ""
-"As you can see, each relationship is declared with an <literal>ejb-relation</"
-"literal> element within the top level <literal>relationships</literal> "
-"element. The relation is given a name in the <literal>ejb-relation-name</"
-"literal> element. This is important because we will need to refer to the "
-"role by name in the <literal>jbosscmp-jdbc.xml</literal> file. Each "
-"<literal>ejb-relation</literal> contains two <literal>ejb-relationship-role</"
-"literal> elements (one for each side of the relationship). The <literal>ejb-"
-"relationship-role</literal> tags are as follows:"
-msgstr ""
-"如你所看到的,每个关系都用顶层的 <literal>relationships</literal> 元素里的 "
-"<literal>ejb-relation</literal> 元素进行声明。<literal>ejb-relation-name</"
-"literal> 元素指定了关系的名称。这很重要,因为我们需要在 <literal>jbosscmp-"
-"jdbc.xml</literal> 文件里通过名称来进行引用。每个 <literal>ejb-relation</"
-"literal> 都包含两个 <literal>ejb-relationship-role</literal> 元素(分别用于关"
-"系的两方)。下面是 <literal>ejb-relationship-role</literal> 标签: "
+msgid "As you can see, each relationship is declared with an <literal>ejb-relation</literal> element within the top level <literal>relationships</literal> element. The relation is given a name in the <literal>ejb-relation-name</literal> element. This is important because we will need to refer to the role by name in the <literal>jbosscmp-jdbc.xml</literal> file. Each <literal>ejb-relation</literal> contains two <literal>ejb-relationship-role</literal> elements (one for each side of the relationship). The <literal>ejb-relationship-role</literal> tags are as follows:"
+msgstr "如你所看到的,每个关系都用顶层的 <literal>relationships</literal> 元素里的 <literal>ejb-relation</literal> 元素进行声明。<literal>ejb-relation-name</literal> 元素指定了关系的名称。这很重要,因为我们需要在 <literal>jbosscmp-jdbc.xml</literal> 文件里通过名称来进行引用。每个 <literal>ejb-relation</literal> 都包含两个 <literal>ejb-relationship-role</literal> 元素(分别用于关系的两方)。下面是 <literal>ejb-relationship-role</literal> 标签: "
 
 #. Tag: para
 #: The_CMP_Engine.xml:574
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ejb-relationshiprole-name</emphasis>: This optional "
-"element is used to identify the role and match the database mapping the "
-"<literal>jbosscmp-jdbc.xml</literal> file. The relationship role names for "
-"each side of a relationship must be different."
-msgstr ""
-"<emphasis role=\"bold\">ejb-relationshiprole-name</emphasis>:这个可选元素用"
-"来标识角色并映射 <literal>jbosscmp-jdbc.xml</literal> 文件定义的数据库。关系"
-"的每边的角色名称都必须不同。 "
+msgid "<emphasis role=\"bold\">ejb-relationshiprole-name</emphasis>: This optional element is used to identify the role and match the database mapping the <literal>jbosscmp-jdbc.xml</literal> file. The relationship role names for each side of a relationship must be different."
+msgstr "<emphasis role=\"bold\">ejb-relationshiprole-name</emphasis>:这个可选元素用来标识角色并映射 <literal>jbosscmp-jdbc.xml</literal> 文件定义的数据库。关系的每边的角色名称都必须不同。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:579
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">multiplicity</emphasis>: This indicates the "
-"multiplicity of this side of the relationship. The valid values are "
-"<literal>One</literal> or <literal>Many</literal>. In this example, the "
-"multiplicity of the organization is <literal>One</literal> and the "
-"multiplicity of the gangster is <literal>Many</literal> because the "
-"relationship is from one organization to many gangsters. Note, as with all "
-"XML elements, this element is case sensitive."
-msgstr ""
-"<emphasis role=\"bold\">multiplicity</emphasis>:它指定关系的一边的多重性"
-"(multiplicity)。其有效值是 <literal>One</literal> 或 <literal>Many</"
-"literal>。在这个例子里,organization 的多重性是 <literal>One</literal>,而 "
-"gangster 的多重性是 <literal>Many</literal>,这是因为一个 organization  对应"
-"多个 gangster。请注意,和所有 XML 元素不同,这个元素对大小写敏感。 "
+msgid "<emphasis role=\"bold\">multiplicity</emphasis>: This indicates the multiplicity of this side of the relationship. The valid values are <literal>One</literal> or <literal>Many</literal>. In this example, the multiplicity of the organization is <literal>One</literal> and the multiplicity of the gangster is <literal>Many</literal> because the relationship is from one organization to many gangsters. Note, as with all XML elements, this element is case sensitive."
+msgstr "<emphasis role=\"bold\">multiplicity</emphasis>:它指定关系的一边的多重性(multiplicity)。其有效值是 <literal>One</literal> 或 <literal>Many</literal>。在这个例子里,organization 的多重性是 <literal>One</literal>,而 gangster 的多重性是 <literal>Many</literal>,这是因为一个 organization  对应多个 gangster。请注意,和所有 XML 元素不同,这个元素对大小写敏感。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:584
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">cascade-delete</emphasis>: When this optional "
-"element is present, JBoss will delete the child entity when the parent "
-"entity is deleted. Cascade deletion is only allowed for a role where the "
-"other side of the relationship has a multiplicity of one. The default is to "
-"not cascade delete."
-msgstr ""
-"<emphasis role=\"bold\">cascade-delete</emphasis>:如使用这个可选元素,在父 "
-"entity 被删除时,JBoss 将删除其子 entity。层叠删除(Cascade deletion)只有在"
-"关系的另外一边的多重性为 One 时才允许层叠删除(Cascade deletion)。它缺省是被"
-"禁止的。 "
+msgid "<emphasis role=\"bold\">cascade-delete</emphasis>: When this optional element is present, JBoss will delete the child entity when the parent entity is deleted. Cascade deletion is only allowed for a role where the other side of the relationship has a multiplicity of one. The default is to not cascade delete."
+msgstr "<emphasis role=\"bold\">cascade-delete</emphasis>:如使用这个可选元素,在父 entity 被删除时,JBoss 将删除其子 entity。层叠删除(Cascade deletion)只有在关系的另外一边的多重性为 One 时才允许层叠删除(Cascade deletion)。它缺省是被禁止的。 "
 
 #. Tag: emphasis
 #: The_CMP_Engine.xml:590
@@ -2844,12 +1902,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:594
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ejb-name</emphasis>: This required element gives the "
-"name of the entity that has the role."
-msgstr ""
-"<emphasis role=\"bold\">ejb-name</emphasis>:这是必需的元素,它指定具有这个角"
-"色的 entity 的名称。 "
+msgid "<emphasis role=\"bold\">ejb-name</emphasis>: This required element gives the name of the entity that has the role."
+msgstr "<emphasis role=\"bold\">ejb-name</emphasis>:这是必需的元素,它指定具有这个角色的 entity 的名称。 "
 
 #. Tag: emphasis
 #: The_CMP_Engine.xml:602
@@ -2860,35 +1914,20 @@
 #. Tag: para
 #: The_CMP_Engine.xml:606
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">cmr-field-name</emphasis>: This is the name of the "
-"CMR field of the entity has one, if it has one."
-msgstr ""
-"<emphasis role=\"bold\">cmr-field-name</emphasis>:如果 entity 具有 CMR 字段"
-"的话,这是该字段的名称。 "
+msgid "<emphasis role=\"bold\">cmr-field-name</emphasis>: This is the name of the CMR field of the entity has one, if it has one."
+msgstr "<emphasis role=\"bold\">cmr-field-name</emphasis>:如果 entity 具有 CMR 字段的话,这是该字段的名称。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:611
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">cmr-field-type</emphasis>: This is the type of the "
-"CMR field, if the field is a collection type. It must be <literal>java.util."
-"Collection</literal> or <literal>java.util.Set</literal>."
-msgstr ""
-"<emphasis role=\"bold\">cmr-field-type</emphasis>:这个 CMR 字段的类型(如果"
-"它是集合类型)。它必须是 <literal>java.util.Collection</literal> 或者 "
-"<literal>java.util.Set</literal>。 "
+msgid "<emphasis role=\"bold\">cmr-field-type</emphasis>: This is the type of the CMR field, if the field is a collection type. It must be <literal>java.util.Collection</literal> or <literal>java.util.Set</literal>."
+msgstr "<emphasis role=\"bold\">cmr-field-type</emphasis>:这个 CMR 字段的类型(如果它是集合类型)。它必须是 <literal>java.util.Collection</literal> 或者 <literal>java.util.Set</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:618
 #, no-c-format
-msgid ""
-"After adding the CMR field abstract accessors and declaring the "
-"relationship, the relationship should be functional. The next section "
-"discusses the database mapping of the relationship."
-msgstr ""
-"在添加了 CMR 字段 abstract accessor 并声明了关系后,你就可以使用关系了。下节"
-"我们将讨论关系的数据库映射。 "
+msgid "After adding the CMR field abstract accessors and declaring the relationship, the relationship should be functional. The next section discusses the database mapping of the relationship."
+msgstr "在添加了 CMR 字段 abstract accessor 并声明了关系后,你就可以使用关系了。下节我们将讨论关系的数据库映射。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:624
@@ -2899,27 +1938,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:625
 #, no-c-format
-msgid ""
-"Relationships can be mapped using either a foreign key or a separate "
-"relation table. One-to-one and one-to-many relationships use the foreign key "
-"mapping style by default, and many-to-many relationships use only the "
-"relation table mapping style. The mapping of a relationship is declared in "
-"the <literal>relationships</literal> section of the <literal>jbosscmp-jdbc."
-"xml</literal> descriptor via <literal>ejb-relation</literal> elements. "
-"Relationships are identified by the <literal>ejb-relation-name</literal> "
-"from the <literal>ejb-jar.xml</literal> file. The <literal>jbosscmp-jdbc."
-"xml</literal><literal>ejb-relation</literal> element content model is shown "
-"in <xref linkend=\"Relationship_Mapping-The_jbosscmp_jdbc."
-"xml_ejb_relation_element_content_model\"/>."
-msgstr ""
-"关系可以用外键或者独立的关系型表来映射。一对一和一对多的关系缺省使用外键的映"
-"射风格,而多对多关系则只使用关系型表风格。关系的映射在 <literal>jbosscmp-"
-"jdbc.xml</literal> 描述符的 <literal>relationships</literal> 部分里通过 "
-"<literal>ejb-relation</literal> 元素进行声明。<literal>ejb-jar.xml</literal> "
-"文件里的 <literal>ejb-relation-name</literal> 标识关系。<xref linkend="
-"\"Relationship_Mapping-The_jbosscmp_jdbc."
-"xml_ejb_relation_element_content_model\"/> 展示了 <literal>jbosscmp-jdbc."
-"xml</literal> 里的 <literal>ejb-relation</literal> 元素的内容格式。 "
+msgid "Relationships can be mapped using either a foreign key or a separate relation table. One-to-one and one-to-many relationships use the foreign key mapping style by default, and many-to-many relationships use only the relation table mapping style. The mapping of a relationship is declared in the <literal>relationships</literal> section of the <literal>jbosscmp-jdbc.xml</literal> descriptor via <literal>ejb-relation</literal> elements. Relationships are identified by the <literal>ejb-relation-name</literal> from the <literal>ejb-jar.xml</literal> file. The <literal>jbosscmp-jdbc.xml</literal><literal>ejb-relation</literal> element content model is shown in <xref linkend=\"Relationship_Mapping-The_jbosscmp_jdbc.xml_ejb_relation_element_content_model\"/>."
+msgstr "关系可以用外键或者独立的关系型表来映射。一对一和一对多的关系缺省使用外键的映射风格,而多对多关系则只使用关系型表风格。关系的映射在 <literal>jbosscmp-jdbc.xml</literal> 描述符的 <literal>relationships</literal> 部分里通过 <literal>ejb-relation</literal> 元素进行声明。<literal>ejb-jar.xml</literal> 文件里的 <literal>ejb-relation-name</literal> 标识关系。<xref linkend=\"Relationship_Mapping-The_jbosscmp_jdbc.xml_ejb_relation_element_content_model\"/> 展示了 <literal>jbosscmp-jdbc.xml</literal> 里的 <literal>ejb-relation</literal> 元素的内容格式。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:629
@@ -2930,9 +1950,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:636
 #, no-c-format
-msgid ""
-"The basic template of the relationship mapping declaration for "
-"<literal>Organization-Gangster</literal> relationship follows:"
+msgid "The basic template of the relationship mapping declaration for <literal>Organization-Gangster</literal> relationship follows:"
 msgstr "<literal>Organization-Gangster</literal> 关系映射声明遵循下面的基本模板: "
 
 #. Tag: programlisting
@@ -2942,12 +1960,10 @@
 "&lt;jbosscmp-jdbc&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-name&gt;\n"
 "            &lt;foreign-key-mapping/&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields&gt;\n"
 "                    &lt;key-field&gt;\n"
 "                        &lt;field-name&gt;name&lt;/field-name&gt;\n"
@@ -2956,8 +1972,7 @@
 "                &lt;/key-fields&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-"
-"org&lt;/ejb-relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-org&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields/&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "        &lt;/ejb-relation&gt;\n"
@@ -2967,12 +1982,10 @@
 "&lt;jbosscmp-jdbc&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-name&gt;\n"
 "            &lt;foreign-key-mapping/&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields&gt;\n"
 "                    &lt;key-field&gt;\n"
 "                        &lt;field-name&gt;name&lt;/field-name&gt;\n"
@@ -2981,8 +1994,7 @@
 "                &lt;/key-fields&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-"
-"org&lt;/ejb-relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-org&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields/&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "        &lt;/ejb-relation&gt;\n"
@@ -2992,34 +2004,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:640
 #, no-c-format
-msgid ""
-"After the <literal>ejb-relation-name</literal> of the relationship being "
-"mapped is declared, the relationship can be declared as read only using the "
-"<literal>read-only</literal> and <literal>read-time-out</literal> elements. "
-"They have the same semantics as their counterparts in the entity element."
-msgstr ""
-"在声明了映射的关系的 <literal>ejb-relation-name</literal> 后,关系可以用 "
-"<literal>read-only</literal> 和 <literal>read-time-out</literal> 元素声明为只"
-"读模式。它们具有和 entity 元素里对应部分相同的模式。 "
+msgid "After the <literal>ejb-relation-name</literal> of the relationship being mapped is declared, the relationship can be declared as read only using the <literal>read-only</literal> and <literal>read-time-out</literal> elements. They have the same semantics as their counterparts in the entity element."
+msgstr "在声明了映射的关系的 <literal>ejb-relation-name</literal> 后,关系可以用 <literal>read-only</literal> 和 <literal>read-time-out</literal> 元素声明为只读模式。它们具有和 entity 元素里对应部分相同的模式。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:643
 #, no-c-format
-msgid ""
-"The <literal>ejb-relation</literal> element must contain either a "
-"<literal>foreign-key-mapping</literal> element or a <literal>relation-table-"
-"mapping</literal> element, which are described in <xref linkend="
-"\"Relationship_Mapping-Foreign_Key_Mapping\"/> and <xref linkend="
-"\"Relationship_Mapping-Relation_table_Mapping\"/>. This element may also "
-"contain a pair of <literal>ejb-relationship-role</literal> elements as "
-"described in the following section."
-msgstr ""
-"<literal>ejb-relation</literal> 元素必须包含 <literal>foreign-key-mapping</"
-"literal> 或  <literal>relation-table-mapping</literal> 元素,我们分别在 "
-"<xref linkend=\"Relationship_Mapping-Foreign_Key_Mapping\"/> 和 <xref "
-"linkend=\"Relationship_Mapping-Relation_table_Mapping\"/> 里对它们进行描述。"
-"这个元素也可以包含下面章节里描述的一对 <literal>ejb-relationship-role</"
-"literal> 元素。 "
+msgid "The <literal>ejb-relation</literal> element must contain either a <literal>foreign-key-mapping</literal> element or a <literal>relation-table-mapping</literal> element, which are described in <xref linkend=\"Relationship_Mapping-Foreign_Key_Mapping\"/> and <xref linkend=\"Relationship_Mapping-Relation_table_Mapping\"/>. This element may also contain a pair of <literal>ejb-relationship-role</literal> elements as described in the following section."
+msgstr "<literal>ejb-relation</literal> 元素必须包含 <literal>foreign-key-mapping</literal> 或  <literal>relation-table-mapping</literal> 元素,我们分别在 <xref linkend=\"Relationship_Mapping-Foreign_Key_Mapping\"/> 和 <xref linkend=\"Relationship_Mapping-Relation_table_Mapping\"/> 里对它们进行描述。这个元素也可以包含下面章节里描述的一对 <literal>ejb-relationship-role</literal> 元素。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:647
@@ -3030,17 +2022,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:648
 #, no-c-format
-msgid ""
-"Each of the two <literal>ejb-relationship-role</literal> elements contains "
-"mapping information specific to an entity in the relationship. The content "
-"model of the <literal>ejb-relationship-role</literal> element is shown in "
-"<xref linkend=\"Relationship_Role_Mapping-"
-"The_jbosscmp_jdbc_ejb_relationship_role_element_content_model\"/> ."
-msgstr ""
-"两个 <literal>ejb-relationship-role</literal> 元素都包含关于 entity 的映射信"
-"息。<xref linkend=\"Relationship_Role_Mapping-"
-"The_jbosscmp_jdbc_ejb_relationship_role_element_content_model\"/> 展示了 "
-"<literal>ejb-relationship-role</literal> 元素的内容格式。 "
+msgid "Each of the two <literal>ejb-relationship-role</literal> elements contains mapping information specific to an entity in the relationship. The content model of the <literal>ejb-relationship-role</literal> element is shown in <xref linkend=\"Relationship_Role_Mapping-The_jbosscmp_jdbc_ejb_relationship_role_element_content_model\"/> ."
+msgstr "两个 <literal>ejb-relationship-role</literal> 元素都包含关于 entity 的映射信息。<xref linkend=\"Relationship_Role_Mapping-The_jbosscmp_jdbc_ejb_relationship_role_element_content_model\"/> 展示了 <literal>ejb-relationship-role</literal> 元素的内容格式。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:652
@@ -3057,111 +2040,38 @@
 #. Tag: para
 #: The_CMP_Engine.xml:664
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">ejb-relationship-role-name</emphasis>: This required "
-"element gives the name of the role to which this configuration applies. It "
-"must match the name of one of the roles declared for this relationship in "
-"the <literal>ejb-jar.xml</literal> file."
-msgstr ""
-"<emphasis role=\"bold\">ejb-relationship-role-name</emphasis>:这是一个必需元"
-"素,它给出这个配置所适用的角色的名称。它必须匹配 <literal>ejb-jar.xml</"
-"literal> 文件里针对这个关系所声明的角色的名称。 "
+msgid "<emphasis role=\"bold\">ejb-relationship-role-name</emphasis>: This required element gives the name of the role to which this configuration applies. It must match the name of one of the roles declared for this relationship in the <literal>ejb-jar.xml</literal> file."
+msgstr "<emphasis role=\"bold\">ejb-relationship-role-name</emphasis>:这是一个必需元素,它给出这个配置所适用的角色的名称。它必须匹配 <literal>ejb-jar.xml</literal> 文件里针对这个关系所声明的角色的名称。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:669
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">fk-constraint</emphasis>: This optional element is a "
-"true/false value that indicates whether JBoss should add a foreign key "
-"constraint to the tables for this side of the relationship. JBoss will only "
-"add generate the constraint if both the primary table and the related table "
-"were created by JBoss during deployment."
-msgstr ""
-"<emphasis role=\"bold\">fk-constraint</emphasis>:这个值为 true/false 的可选"
-"元素指定 JBoss 是否应该在这一边的关系的表里添加外键约束。只有主表和相关的表都"
-"在部署期间创建时,JBoss 才生成这个约束。 "
+msgid "<emphasis role=\"bold\">fk-constraint</emphasis>: This optional element is a true/false value that indicates whether JBoss should add a foreign key constraint to the tables for this side of the relationship. JBoss will only add generate the constraint if both the primary table and the related table were created by JBoss during deployment."
+msgstr "<emphasis role=\"bold\">fk-constraint</emphasis>:这个值为 true/false 的可选元素指定 JBoss 是否应该在这一边的关系的表里添加外键约束。只有主表和相关的表都在部署期间创建时,JBoss 才生成这个约束。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:674
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">key-fields</emphasis>: This optional element "
-"specifies the mapping of the primary key fields of the current entity, "
-"whether it is mapped in the relation table or in the related object. The "
-"<literal>key-fields</literal> element must contain a <literal>key-field</"
-"literal> element for each primary key field of the current entity. The "
-"<literal>key-fields</literal> element can be empty if no foreign key mapping "
-"is needed for this side of the relation. An example of this would be the "
-"many side of a one-to-many relationship. The details of this element are "
-"described below."
-msgstr ""
-"<emphasis role=\"bold\">key-fields</emphasis>:这个可选元素指定当前 entity 的"
-"主键字段的映射,无论它是在关系表还是对象里进行映射。对于当前 entity 的每个主"
-"键字段,<literal>key-fields</literal> 元素都必须包含一个 <literal>key-field</"
-"literal> 元素。如果这一侧的关系不需要外键映射,则 <literal>key-fields</"
-"literal> 元素可以为空。在一对多的关系里,“多”的一侧就是这样的一个例子。下面是"
-"关于这个元素的细节。 "
+msgid "<emphasis role=\"bold\">key-fields</emphasis>: This optional element specifies the mapping of the primary key fields of the current entity, whether it is mapped in the relation table or in the related object. The <literal>key-fields</literal> element must contain a <literal>key-field</literal> element for each primary key field of the current entity. The <literal>key-fields</literal> element can be empty if no foreign key mapping is needed for this side of the relation. An example of this would be the many side of a one-to-many relationship. The details of this element are described below."
+msgstr "<emphasis role=\"bold\">key-fields</emphasis>:这个可选元素指定当前 entity 的主键字段的映射,无论它是在关系表还是对象里进行映射。对于当前 entity 的每个主键字段,<literal>key-fields</literal> 元素都必须包含一个 <literal>key-field</literal> 元素。如果这一侧的关系不需要外键映射,则 <literal>key-fields</literal> 元素可以为空。在一对多的关系里,“多”的一侧就是这样的一个例子。下面是关于这个元素的细节。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:679
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-ahead</emphasis>: This optional element "
-"controls the caching of this relationship. This option is discussed in <xref "
-"linkend=\"Lazy_loading_Process-Relationships\"/>."
-msgstr ""
-"<emphasis role=\"bold\">read-ahead</emphasis>:这是一个可选元素,它控制关系的"
-"缓存。<xref linkend=\"Lazy_loading_Process-Relationships\"/> 将讨论这个选项。 "
+msgid "<emphasis role=\"bold\">read-ahead</emphasis>: This optional element controls the caching of this relationship. This option is discussed in <xref linkend=\"Lazy_loading_Process-Relationships\"/>."
+msgstr "<emphasis role=\"bold\">read-ahead</emphasis>:这是一个可选元素,它控制关系的缓存。<xref linkend=\"Lazy_loading_Process-Relationships\"/> 将讨论这个选项。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:684
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">batch-cascade-delete</emphasis>: This indicates that "
-"a cascade delete on this relationship should be performed with a single SQL "
-"statement. This requires that the relationship be marked as <literal>batch-"
-"delete</literal> in the <literal>ejb-jar.xml</literal>."
-msgstr ""
-"<emphasis role=\"bold\">batch-cascade-delete</emphasis>:它指出对这个关系的层"
-"叠删除(cascade delete)应该用单个的 SQL 语句来完成。这要求这个关系在 "
-"<literal>ejb-jar.xml</literal> 里标记为 <literal>batch-delete</literal>。 "
+msgid "<emphasis role=\"bold\">batch-cascade-delete</emphasis>: This indicates that a cascade delete on this relationship should be performed with a single SQL statement. This requires that the relationship be marked as <literal>batch-delete</literal> in the <literal>ejb-jar.xml</literal>."
+msgstr "<emphasis role=\"bold\">batch-cascade-delete</emphasis>:它指出对这个关系的层叠删除(cascade delete)应该用单个的 SQL 语句来完成。这要求这个关系在 <literal>ejb-jar.xml</literal> 里标记为 <literal>batch-delete</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:689
 #, no-c-format
-msgid ""
-"As noted above, the <literal>key-fields</literal> element contains a "
-"<literal>key-field</literal> for each primary key field of the current "
-"entity. The <literal>key-field</literal> element uses the same syntax as the "
-"<literal>cmp-field</literal> element of the entity, except that <literal>key-"
-"field</literal> does not support the <literal>not-null</literal> option. Key "
-"fields of a <literal>relation-table</literal> are automatically not null, "
-"because they are the primary key of the table. On the other hand, foreign "
-"key fields must be nullable by default. This is because the CMP "
-"specification requires an insert into the database after the "
-"<literal>ejbCreate</literal> method and an update to it after to pick up CMR "
-"changes made in <literal>ejbPostCreate</literal>. Since the EJB "
-"specification does not allow a relationship to be modified until "
-"<literal>ejbPostCreate</literal>, a foreign key will be initially set to "
-"null. There is a similar problem with removal. You can change this insert "
-"behavior using the <literal>jboss.xml</literal><literal>insert-after-ejb-"
-"post-create</literal> container configuration flag. The following example "
-"illustrates the creation of a new bean configuration that uses "
-"<literal>insert-after-ejb-post-create</literal> by default."
-msgstr ""
-"如上所述,<literal>key-fields</literal> 元素包含用于当前 entity 的每个主键字"
-"段的 <literal>key-field</literal>。<literal>key-field</literal> 元素使用和 "
-"entity 的 <literal>cmp-field</literal> 元素相同的语法,除了 <literal>key-"
-"field</literal> 不支持 <literal>not-null</literal> 选项。<literal>relation-"
-"table</literal> 的关键字段自动为非空值,这是因为它们是表里的主键。从另外一方"
-"面来说,外键字段必须缺省为非空值。这是因为 CMP 规格要求对数据库的插入发生在 "
-"<literal>ejbCreate</literal> 方法后、而在 <literal>ejbPostCreate</literal> 里"
-"进行更新来反映 CMR 的变动。既然 EJB 规格不允许关系在调用 "
-"<literal>ejbPostCreate</literal> 前被修改,外键的初始值将为空(null)。删除也"
-"有类似的问题。你可以用 <literal>jboss.xml</literal> 文件里的 <literal>insert-"
-"after-ejb-post-create</literal> 容器配置标签来修改这个插入行为。下面的例子演"
-"示了对一个缺省使用 <literal>insert-after-ejb-post-create</literal> 的新的 "
-"bean 的配置的创建过程。 "
+msgid "As noted above, the <literal>key-fields</literal> element contains a <literal>key-field</literal> for each primary key field of the current entity. The <literal>key-field</literal> element uses the same syntax as the <literal>cmp-field</literal> element of the entity, except that <literal>key-field</literal> does not support the <literal>not-null</literal> option. Key fields of a <literal>relation-table</literal> are automatically not null, because they are the primary key of the table. On the other hand, foreign key fields must be nullable by default. This is because the CMP specification requires an insert into the database after the <literal>ejbCreate</literal> method and an update to it after to pick up CMR changes made in <literal>ejbPostCreate</literal>. Since the EJB specification does not allow a relationship to be modified until <literal>ejbPostCreate</literal>, a foreign key will be initially set to null. There is a similar problem with removal. You can cha!
 nge this insert behavior using the <literal>jboss.xml</literal><literal>insert-after-ejb-post-create</literal> container configuration flag. The following example illustrates the creation of a new bean configuration that uses <literal>insert-after-ejb-post-create</literal> by default."
+msgstr "如上所述,<literal>key-fields</literal> 元素包含用于当前 entity 的每个主键字段的 <literal>key-field</literal>。<literal>key-field</literal> 元素使用和 entity çš„ <literal>cmp-field</literal> 元素相同的语法,除了 <literal>key-field</literal> 不支持 <literal>not-null</literal> 选项。<literal>relation-table</literal> 的关键字段自动为非空值,这是因为它们是表里的主键。从另外一方面来说,外键字段必须缺省为非空值。这是因为 CMP 规格要求对数据库的插入发生在 <literal>ejbCreate</literal> 方法后、而在 <literal>ejbPostCreate</literal> 里进行更新来反映 CMR 的变动。既然 EJB 规格不允许关系在调用 <literal>ejbPostCreate</literal> 前被修改,外键的初始值将为空(null)。删除也有类似的问题。你可以用 <literal>jboss.xml</literal> 文件里的 <literal>insert-after-ejb-post-create</literal> 容器配置标签来修改这个æ!
 ’入行为。下面的例子演示了对一个缺省使用 <literal>insert-after-ejb-post-create</literal> çš„æ–°çš„ bean 的配置的创建过程。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:692
@@ -3170,12 +2080,9 @@
 "&lt;jboss&gt;\n"
 "    &lt;!-- ... --&gt;\n"
 "    &lt;container-configurations&gt;\n"
-"        &lt;container-configuration extends=\"Standard CMP 2.x EntityBean"
-"\"&gt;\n"
-"            &lt;container-name&gt;INSERT after ejbPostCreate Container&lt;/"
-"container-name&gt;\n"
-"            <emphasis role=\"bold\">&lt;insert-after-ejb-post-create&gt;"
-"true&lt;/insert-after-ejb-post-create&gt;</emphasis>\n"
+"        &lt;container-configuration extends=\"Standard CMP 2.x EntityBean\"&gt;\n"
+"            &lt;container-name&gt;INSERT after ejbPostCreate Container&lt;/container-name&gt;\n"
+"            <emphasis role=\"bold\">&lt;insert-after-ejb-post-create&gt;true&lt;/insert-after-ejb-post-create&gt;</emphasis>\n"
 "        &lt;/container-configuration&gt;\n"
 "    &lt;/container-configurations&gt;                     \n"
 "&lt;/jboss&gt;"
@@ -3183,12 +2090,9 @@
 "&lt;jboss&gt;\n"
 "    &lt;!-- ... --&gt;\n"
 "    &lt;container-configurations&gt;\n"
-"        &lt;container-configuration extends=\"Standard CMP 2.x EntityBean"
-"\"&gt;\n"
-"            &lt;container-name&gt;INSERT after ejbPostCreate Container&lt;/"
-"container-name&gt;\n"
-"            <emphasis role=\"bold\">&lt;insert-after-ejb-post-create&gt;"
-"true&lt;/insert-after-ejb-post-create&gt;</emphasis>\n"
+"        &lt;container-configuration extends=\"Standard CMP 2.x EntityBean\"&gt;\n"
+"            &lt;container-name&gt;INSERT after ejbPostCreate Container&lt;/container-name&gt;\n"
+"            <emphasis role=\"bold\">&lt;insert-after-ejb-post-create&gt;true&lt;/insert-after-ejb-post-create&gt;</emphasis>\n"
 "        &lt;/container-configuration&gt;\n"
 "    &lt;/container-configurations&gt;                     \n"
 "&lt;/jboss&gt;"
@@ -3196,27 +2100,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:693
 #, no-c-format
-msgid ""
-"An alternate means of working around the non-null foreign key issue is to "
-"map the foreign key elements onto non-null CMP fields. In this case you "
-"simply populate the foreign key fields in <literal>ejbCreate</literal> using "
-"the associated CMP field setters."
-msgstr ""
-"绕开非空外键问题的另外一个办法是把 foreign key 元素映射到非空的 CMP 字段上。"
-"在这种情况下,你只要简单地用相关的 CMP 字段的 setter 方法传递 "
-"<literal>ejbCreate</literal> 里的外键字段就可以了。 "
+msgid "An alternate means of working around the non-null foreign key issue is to map the foreign key elements onto non-null CMP fields. In this case you simply populate the foreign key fields in <literal>ejbCreate</literal> using the associated CMP field setters."
+msgstr "绕开非空外键问题的另外一个办法是把 foreign key 元素映射到非空的 CMP 字段上。在这种情况下,你只要简单地用相关的 CMP 字段的 setter 方法传递 <literal>ejbCreate</literal> 里的外键字段就可以了。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:696
 #, no-c-format
-msgid ""
-"The content model of the key-fields element is <xref linkend="
-"\"Relationship_Role_Mapping-"
-"The_jbosscmp_jdbc_key_fields_element_content_model\"/>."
-msgstr ""
-"<xref linkend=\"Relationship_Role_Mapping-"
-"The_jbosscmp_jdbc_key_fields_element_content_model\"/> 描述了 key-fields 元素"
-"的内容格式。 "
+msgid "The content model of the key-fields element is <xref linkend=\"Relationship_Role_Mapping-The_jbosscmp_jdbc_key_fields_element_content_model\"/>."
+msgstr "<xref linkend=\"Relationship_Role_Mapping-The_jbosscmp_jdbc_key_fields_element_content_model\"/> 描述了 key-fields 元素的内容格式。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:700
@@ -3227,85 +2118,44 @@
 #. Tag: para
 #: The_CMP_Engine.xml:707
 #, no-c-format
-msgid ""
-"A detailed description of the elements contained in the <literal>key-field</"
-"literal> element follows:"
+msgid "A detailed description of the elements contained in the <literal>key-field</literal> element follows:"
 msgstr "下面是对 <literal>key-field</literal> 元素包含的元素的详细描述: "
 
 #. Tag: para
 #: The_CMP_Engine.xml:712
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">field-name</emphasis>: This required element "
-"identifies the field to which this mapping applies. This name must match a "
-"primary key field of the current entity."
-msgstr ""
-"<emphasis role=\"bold\">field-name</emphasis>:这是一个必需元素,它指定该映射"
-"适用的字段。这个名字必须匹配当前 entity 的主键字段。 "
+msgid "<emphasis role=\"bold\">field-name</emphasis>: This required element identifies the field to which this mapping applies. This name must match a primary key field of the current entity."
+msgstr "<emphasis role=\"bold\">field-name</emphasis>:这是一个必需元素,它指定该映射适用的字段。这个名字必须匹配当前 entity 的主键字段。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:717
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">column-name</emphasis>: Use this element to specify "
-"the column name in which this primary key field will be stored. If this is "
-"relationship uses <literal>foreign-key-mapping</literal>, this column will "
-"be added to the table for the related entity. If this relationship uses "
-"<literal>relation-table-mapping</literal>, this column is added to the "
-"<literal>relation-table</literal>. This element is not allowed for mapped "
-"dependent value class; instead use the property element."
-msgstr ""
-"<emphasis role=\"bold\">column-name</emphasis>:主键字段将被存储的列名。如果"
-"这个关系使用 <literal>foreign-key-mapping</literal>,那么这一列将被添加到相"
-"关 entity 的表里。如果这个关系使用 <literal>relation-table-mapping</"
-"literal>,那么这一列将被添加到 <literal>relation-table</literal> 里。映射的 "
-"dependent value 类不被允许使用这个元素,它可以使用 perperty 元素。 "
+msgid "<emphasis role=\"bold\">column-name</emphasis>: Use this element to specify the column name in which this primary key field will be stored. If this is relationship uses <literal>foreign-key-mapping</literal>, this column will be added to the table for the related entity. If this relationship uses <literal>relation-table-mapping</literal>, this column is added to the <literal>relation-table</literal>. This element is not allowed for mapped dependent value class; instead use the property element."
+msgstr "<emphasis role=\"bold\">column-name</emphasis>:主键字段将被存储的列名。如果这个关系使用 <literal>foreign-key-mapping</literal>,那么这一列将被添加到相关 entity 的表里。如果这个关系使用 <literal>relation-table-mapping</literal>,那么这一列将被添加到 <literal>relation-table</literal> 里。映射的 dependent value 类不被允许使用这个元素,它可以使用 perperty 元素。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:722
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">jdbc-type</emphasis>: This is the JDBC type that is "
-"used when setting parameters in a JDBC <literal>PreparedStatement</literal> "
-"or loading data from a JDBC ResultSet. The valid types are defined in "
-"<literal>java.sql.Types</literal>."
-msgstr ""
-"<emphasis role=\"bold\">jdbc-type</emphasis>:这是在设置 JDBC "
-"<literal>PreparedStatement</literal>  的参数或从 JDBC ResultSet 载入数据时使"
-"用的 JDBC 类型。<literal>java.sql.Types</literal> 里定义了其有效值。 "
+msgid "<emphasis role=\"bold\">jdbc-type</emphasis>: This is the JDBC type that is used when setting parameters in a JDBC <literal>PreparedStatement</literal> or loading data from a JDBC ResultSet. The valid types are defined in <literal>java.sql.Types</literal>."
+msgstr "<emphasis role=\"bold\">jdbc-type</emphasis>:这是在设置 JDBC <literal>PreparedStatement</literal>  的参数或从 JDBC ResultSet 载入数据时使用的 JDBC 类型。<literal>java.sql.Types</literal> 里定义了其有效值。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:727
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">sql-type</emphasis>: This is the SQL type that is "
-"used in create table statements for this field. Valid types are only limited "
-"by your database vendor."
-msgstr ""
-"<emphasis role=\"bold\">sql-type</emphasis>:这是用于该字段的 create table 语"
-"句所使用的 SQL 类型。其有效值依你的数据库供应商而定。 "
+msgid "<emphasis role=\"bold\">sql-type</emphasis>: This is the SQL type that is used in create table statements for this field. Valid types are only limited by your database vendor."
+msgstr "<emphasis role=\"bold\">sql-type</emphasis>:这是用于该字段的 create table 语句所使用的 SQL 类型。其有效值依你的数据库供应商而定。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:732
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">property</emphasis>: Use this element for to specify "
-"the mapping of a primary key field which is a dependent value class."
-msgstr ""
-"<emphasis role=\"bold\">property</emphasis>:这个元素指定值为 dependent "
-"value 类的主键字段的映射。 "
+msgid "<emphasis role=\"bold\">property</emphasis>: Use this element for to specify the mapping of a primary key field which is a dependent value class."
+msgstr "<emphasis role=\"bold\">property</emphasis>:这个元素指定值为 dependent value 类的主键字段的映射。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:737
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">dbindex</emphasis>: The presence of this optional "
-"field indicates that the server should create an index on the corresponding "
-"column in the database, and the index name will be <literal>fieldname_index</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">dbindex</emphasis>:这个可选字段指定服务器应该在数据"
-"库里对应的列上创建索引,且索引名将是 <literal>fieldname_index</literal>。 "
+msgid "<emphasis role=\"bold\">dbindex</emphasis>: The presence of this optional field indicates that the server should create an index on the corresponding column in the database, and the index name will be <literal>fieldname_index</literal>."
+msgstr "<emphasis role=\"bold\">dbindex</emphasis>:这个可选字段指定服务器应该在数据库里对应的列上创建索引,且索引名将是 <literal>fieldname_index</literal>。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:745
@@ -3316,54 +2166,20 @@
 #. Tag: para
 #: The_CMP_Engine.xml:746
 #, no-c-format
-msgid ""
-"Foreign key mapping is the most common mapping style for one-to-one and one-"
-"to-many relationships, but is not allowed for many-to many relationships. "
-"The foreign key mapping element is simply declared by adding an empty "
-"foreign <literal>key-mapping</literal> element to the <literal>ejb-relation</"
-"literal> element."
-msgstr ""
-"对于一对一和一对多的关系来说,外键映射(Foreign key mapping)是最常用的映射风"
-"格,但它不能用在多对多的关系里。简单地把空的外部 <literal>key-mapping</"
-"literal> 元素添加到 <literal>ejb-relation</literal> 元素里就可以声明外键映射"
-"元素。 "
+msgid "Foreign key mapping is the most common mapping style for one-to-one and one-to-many relationships, but is not allowed for many-to many relationships. The foreign key mapping element is simply declared by adding an empty foreign <literal>key-mapping</literal> element to the <literal>ejb-relation</literal> element."
+msgstr "对于一对一和一对多的关系来说,外键映射(Foreign key mapping)是最常用的映射风格,但它不能用在多对多的关系里。简单地把空的外部 <literal>key-mapping</literal> 元素添加到 <literal>ejb-relation</literal> 元素里就可以声明外键映射元素。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:749
 #, no-c-format
-msgid ""
-"As noted in the previous section, with a foreign key mapping the "
-"<literal>key-fields</literal> declared in the <literal>ejb-relationship-"
-"role</literal> are added to the table of the related entity. If the "
-"<literal>key-fields</literal> element is empty, a foreign key will not be "
-"created for the entity. In a one-to-many relationship, the many side "
-"(<literal>Gangster</literal> in the example) must have an empty <literal>key-"
-"fields</literal> element, and the one side (<literal>Organization</literal> "
-"in the example) must have a <literal>key-fields</literal> mapping. In one-to-"
-"one relationships, one or both roles can have foreign keys."
-msgstr ""
-"如前面章节里所述,在 <literal>ejb-relationship-role</literal> 里声明的使用外"
-"键映射的 <literal>key-fields</literal> 将被添加到相关的 entity 的表里。如果 "
-"<literal>key-fields</literal> 元素为空,这个 entity 将不能创建外键。在一对多"
-"的关系里,“多”的一侧(如这个例子里的 <literal>Gangster</literal>)必须具有一"
-"个空的 <literal>key-fields</literal> 元素,而“一”这一侧(如 "
-"<literal>Organization</literal>)则必须具有一个 <literal>key-fields</"
-"literal> 映射。在一对一的关系里,两个角色都可以具有外键。 "
+msgid "As noted in the previous section, with a foreign key mapping the <literal>key-fields</literal> declared in the <literal>ejb-relationship-role</literal> are added to the table of the related entity. If the <literal>key-fields</literal> element is empty, a foreign key will not be created for the entity. In a one-to-many relationship, the many side (<literal>Gangster</literal> in the example) must have an empty <literal>key-fields</literal> element, and the one side (<literal>Organization</literal> in the example) must have a <literal>key-fields</literal> mapping. In one-to-one relationships, one or both roles can have foreign keys."
+msgstr "如前面章节里所述,在 <literal>ejb-relationship-role</literal> 里声明的使用外键映射的 <literal>key-fields</literal> 将被添加到相关的 entity 的表里。如果 <literal>key-fields</literal> 元素为空,这个 entity 将不能创建外键。在一对多的关系里,“多”的一侧(如这个例子里的 <literal>Gangster</literal>)必须具有一个空的 <literal>key-fields</literal> 元素,而“一”这一侧(如 <literal>Organization</literal>)则必须具有一个 <literal>key-fields</literal> 映射。在一对一的关系里,两个角色都可以具有外键。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:752
 #, no-c-format
-msgid ""
-"The foreign key mapping is not dependent on the direction of the "
-"relationship. This means that in a one-to-one unidirectional relationship "
-"(only one side has an accessor) one or both roles can still have foreign "
-"keys. The complete foreign key mapping for the <literal>Organization-"
-"Gangster</literal> relationship is shown below with the foreign key elements "
-"highlighted in bold:"
-msgstr ""
-"外键映射不依赖于关系的方向。这意味着在一对一的单向(只有一边有 accessor 方"
-"法)的关系里,两个角色都可以拥有外键。下面是 <literal>Organization-Gangster</"
-"literal> 关系的完整外键映射,其中外键元素以黑体突出显示: "
+msgid "The foreign key mapping is not dependent on the direction of the relationship. This means that in a one-to-one unidirectional relationship (only one side has an accessor) one or both roles can still have foreign keys. The complete foreign key mapping for the <literal>Organization-Gangster</literal> relationship is shown below with the foreign key elements highlighted in bold:"
+msgstr "外键映射不依赖于关系的方向。这意味着在一对一的单向(只有一边有 accessor 方法)的关系里,两个角色都可以拥有外键。下面是 <literal>Organization-Gangster</literal> 关系的完整外键映射,其中外键元素以黑体突出显示: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:755
@@ -3372,20 +2188,14 @@
 "&lt;jbosscmp-jdbc&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-name&gt;\n"
 "            <emphasis role=\"bold\">&lt;foreign-key-mapping/&gt;</emphasis>\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-"
-"relationship-role-name&gt;\n"
-"                <emphasis role=\"bold\">&lt;key-fields&gt; &lt;key-field&gt; "
-"&lt;field-name&gt;name&lt;/field-name&gt; &lt;column-name&gt;"
-"organization&lt;/column-name&gt; &lt;/key-field&gt; &lt;/key-fields&gt;</"
-"emphasis>\n"
+"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-relationship-role-name&gt;\n"
+"                <emphasis role=\"bold\">&lt;key-fields&gt; &lt;key-field&gt; &lt;field-name&gt;name&lt;/field-name&gt; &lt;column-name&gt;organization&lt;/column-name&gt; &lt;/key-field&gt; &lt;/key-fields&gt;</emphasis>\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-"
-"org&lt;/ejb-relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-org&lt;/ejb-relationship-role-name&gt;\n"
 "                <emphasis role=\"bold\">&lt;key-fields/&gt;</emphasis>\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "        &lt;/ejb-relation&gt;\n"
@@ -3395,20 +2205,14 @@
 "&lt;jbosscmp-jdbc&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Organization-Gangster&lt;/ejb-relation-name&gt;\n"
 "            <emphasis role=\"bold\">&lt;foreign-key-mapping/&gt;</emphasis>\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-"
-"relationship-role-name&gt;\n"
-"                <emphasis role=\"bold\">&lt;key-fields&gt; &lt;key-field&gt; "
-"&lt;field-name&gt;name&lt;/field-name&gt; &lt;column-name&gt;"
-"organization&lt;/column-name&gt; &lt;/key-field&gt; &lt;/key-fields&gt;</"
-"emphasis>\n"
+"                &lt;ejb-relationship-role-name&gt;org-has-gangsters&lt;/ejb-relationship-role-name&gt;\n"
+"                <emphasis role=\"bold\">&lt;key-fields&gt; &lt;key-field&gt; &lt;field-name&gt;name&lt;/field-name&gt; &lt;column-name&gt;organization&lt;/column-name&gt; &lt;/key-field&gt; &lt;/key-fields&gt;</emphasis>\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-"
-"org&lt;/ejb-relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;gangster-belongs-to-org&lt;/ejb-relationship-role-name&gt;\n"
 "                <emphasis role=\"bold\">&lt;key-fields/&gt;</emphasis>\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "        &lt;/ejb-relation&gt;\n"
@@ -3424,15 +2228,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:760
 #, no-c-format
-msgid ""
-"Relation table mapping is less common for one-to-one and one-to-many "
-"relationships, but is the only mapping style allowed for many-to-many "
-"relationships. Relation table mapping is defined using the <literal>relation-"
-"table-mapping</literal> element, the content model of which is shown below."
-msgstr ""
-"对于一对一和一对多关系来说,关系表映射(Relation table Mapping)不是那么常"
-"用,但它是多对对关系唯一允许的映射风格。关系表映射用 <literal>relation-table-"
-"mapping</literal> 元素进行定义,下面是其内容格式。 "
+msgid "Relation table mapping is less common for one-to-one and one-to-many relationships, but is the only mapping style allowed for many-to-many relationships. Relation table mapping is defined using the <literal>relation-table-mapping</literal> element, the content model of which is shown below."
+msgstr "对于一对一和一对多关系来说,关系表映射(Relation table Mapping)不是那么常用,但它是多对对关系唯一允许的映射风格。关系表映射用 <literal>relation-table-mapping</literal> 元素进行定义,下面是其内容格式。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:764
@@ -3443,12 +2240,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:771
 #, no-c-format
-msgid ""
-"The relation-table-mapping for the <literal>Gangster-Job</literal> "
-"relationship is shown in with table mapping elements highlighted in bold:"
-msgstr ""
-"下面是 <literal>Gangster-Job</literal> 关系的 relation-table-mapping 定义,"
-"其 table mapping 元素以黑体突出显示: "
+msgid "The relation-table-mapping for the <literal>Gangster-Job</literal> relationship is shown in with table mapping elements highlighted in bold:"
+msgstr "下面是 <literal>Gangster-Job</literal> 关系的 relation-table-mapping 定义,其 table mapping 元素以黑体突出显示: "
 
 #. Tag: title
 #: The_CMP_Engine.xml:774
@@ -3463,14 +2256,12 @@
 "&lt;jbosscmp-jdbc&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Gangster-Jobs&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Gangster-Jobs&lt;/ejb-relation-name&gt;\n"
 "            &lt;relation-table-mapping&gt;\n"
 "                &lt;table-name&gt;gangster_job&lt;/table-name&gt;\n"
 "            &lt;/relation-table-mapping&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;gangster-has-jobs&lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;gangster-has-jobs&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields&gt;\n"
 "                    &lt;key-field&gt;\n"
 "                        &lt;field-name&gt;gangsterId&lt;/field-name&gt;\n"
@@ -3479,8 +2270,7 @@
 "                &lt;/key-fields&gt;\n"
 "            &lt;/ejb-relationship-role&gt;   \n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;job-has-gangsters&lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;job-has-gangsters&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields&gt;\n"
 "                    &lt;key-field&gt;\n"
 "                        &lt;field-name&gt;name&lt;/field-name&gt;\n"
@@ -3495,14 +2285,12 @@
 "&lt;jbosscmp-jdbc&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Gangster-Jobs&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Gangster-Jobs&lt;/ejb-relation-name&gt;\n"
 "            &lt;relation-table-mapping&gt;\n"
 "                &lt;table-name&gt;gangster_job&lt;/table-name&gt;\n"
 "            &lt;/relation-table-mapping&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;gangster-has-jobs&lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;gangster-has-jobs&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields&gt;\n"
 "                    &lt;key-field&gt;\n"
 "                        &lt;field-name&gt;gangsterId&lt;/field-name&gt;\n"
@@ -3511,8 +2299,7 @@
 "                &lt;/key-fields&gt;\n"
 "            &lt;/ejb-relationship-role&gt;   \n"
 "            &lt;ejb-relationship-role&gt;\n"
-"                &lt;ejb-relationship-role-name&gt;job-has-gangsters&lt;/ejb-"
-"relationship-role-name&gt;\n"
+"                &lt;ejb-relationship-role-name&gt;job-has-gangsters&lt;/ejb-relationship-role-name&gt;\n"
 "                &lt;key-fields&gt;\n"
 "                    &lt;key-field&gt;\n"
 "                        &lt;field-name&gt;name&lt;/field-name&gt;\n"
@@ -3527,108 +2314,50 @@
 #. Tag: para
 #: The_CMP_Engine.xml:776
 #, no-c-format
-msgid ""
-"The <literal>relation-table-mapping</literal> element contains a subset of "
-"the options available in the <literal>entity</literal> element. A detailed "
-"description of these elements is reproduced here for convenience:"
-msgstr ""
-"<literal>relation-table-mapping</literal> 元素包含 <literal>entity</literal> "
-"元素的选项的一个子集。为方便起见,下面是对这些元素的详细描述: "
+msgid "The <literal>relation-table-mapping</literal> element contains a subset of the options available in the <literal>entity</literal> element. A detailed description of these elements is reproduced here for convenience:"
+msgstr "<literal>relation-table-mapping</literal> 元素包含 <literal>entity</literal> 元素的选项的一个子集。为方便起见,下面是对这些元素的详细描述: "
 
 #. Tag: para
 #: The_CMP_Engine.xml:781
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">table-name</emphasis>: This optional element gives "
-"the name of the table that will hold data for this relationship. The default "
-"table name is based on the entity and <literal>cmr-field</literal> names."
-msgstr ""
-"<emphasis role=\"bold\">table-name</emphasis>:这是一个可选元素,它指定将保存"
-"这个关系的数据的表的名称。缺省的表名基于 entity 和 <literal>cmr-field</"
-"literal> 名称。 "
+msgid "<emphasis role=\"bold\">table-name</emphasis>: This optional element gives the name of the table that will hold data for this relationship. The default table name is based on the entity and <literal>cmr-field</literal> names."
+msgstr "<emphasis role=\"bold\">table-name</emphasis>:这是一个可选元素,它指定将保存这个关系的数据的表的名称。缺省的表名基于 entity 和 <literal>cmr-field</literal> 名称。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:786
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">datasource</emphasis>: This optional element gives "
-"the <literal>jndi-name</literal> used to look up the datasource. All "
-"database connections are obtained from the datasource. Having different "
-"datasources for entities is not recommended, as it vastly constrains the "
-"domain over which finders and <literal>ejbSelect</literal>s can query."
-msgstr ""
-"<emphasis role=\"bold\">datasource</emphasis>:这个可选元素指定用来查找数据源"
-"的 <literal>jndi-name</literal>。所有的数据库连接都从数据源获得。我们不推荐 "
-"entity 拥有多个数据源,因为这会极大地限制 finders 和 <literal>ejbSelect</"
-"literal> 可以查找的范围。 "
+msgid "<emphasis role=\"bold\">datasource</emphasis>: This optional element gives the <literal>jndi-name</literal> used to look up the datasource. All database connections are obtained from the datasource. Having different datasources for entities is not recommended, as it vastly constrains the domain over which finders and <literal>ejbSelect</literal>s can query."
+msgstr "<emphasis role=\"bold\">datasource</emphasis>:这个可选元素指定用来查找数据源的 <literal>jndi-name</literal>。所有的数据库连接都从数据源获得。我们不推荐 entity 拥有多个数据源,因为这会极大地限制 finders 和 <literal>ejbSelect</literal> 可以查找的范围。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:791
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">datasourcemapping</emphasis>: This optional element "
-"allows one to specify the name of the <literal>type-mapping</literal> to use."
-msgstr ""
-"<emphasis role=\"bold\">datasourcemapping</emphasis>:这是一个可选元素,它允"
-"许你指定所使用的 <literal>type-mapping</literal> 的名字。 "
+msgid "<emphasis role=\"bold\">datasourcemapping</emphasis>: This optional element allows one to specify the name of the <literal>type-mapping</literal> to use."
+msgstr "<emphasis role=\"bold\">datasourcemapping</emphasis>:这是一个可选元素,它允许你指定所使用的 <literal>type-mapping</literal> 的名字。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:796
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">create-table</emphasis>: This optional element if "
-"true indicates JBoss should attempt to create a table for the relationship. "
-"When the application is deployed, JBoss checks if a table already exists "
-"before creating the table. If a table is found, it is logged, and the table "
-"is not created. This option is very useful during the early stages of "
-"development when the table structure changes often."
-msgstr ""
-"<emphasis role=\"bold\">create-table</emphasis>:这个可选元素如果为 true,表"
-"示 JBoss 应该试图为这个关系创建一个表。当应用程序被部署时,JBoss 会在创建表之"
-"前检查它是否已经存在。如果已经存在,JBoss 将登记日志并不再创建。这个选项在部"
-"署早期表结构经常改变时很有用处。 "
+msgid "<emphasis role=\"bold\">create-table</emphasis>: This optional element if true indicates JBoss should attempt to create a table for the relationship. When the application is deployed, JBoss checks if a table already exists before creating the table. If a table is found, it is logged, and the table is not created. This option is very useful during the early stages of development when the table structure changes often."
+msgstr "<emphasis role=\"bold\">create-table</emphasis>:这个可选元素如果为 true,表示 JBoss 应该试图为这个关系创建一个表。当应用程序被部署时,JBoss 会在创建表之前检查它是否已经存在。如果已经存在,JBoss 将登记日志并不再创建。这个选项在部署早期表结构经常改变时很有用处。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:806
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">remove-table</emphasis>: This optional element if "
-"true indicates JBoss should attempt to drop the <literal>relation-table</"
-"literal> when the application is undeployed. This option is very useful "
-"during the early stages of development when the table structure changes "
-"often."
-msgstr ""
-"<emphasis role=\"bold\">remove-table</emphasis>:这个可选元素如果为 true,表"
-"示在卸载应用程序时 JBoss 应该试图删除 <literal>relation-table</literal>。这个"
-"选项在部署早期表结构经常改变时很有用处。 "
+msgid "<emphasis role=\"bold\">remove-table</emphasis>: This optional element if true indicates JBoss should attempt to drop the <literal>relation-table</literal> when the application is undeployed. This option is very useful during the early stages of development when the table structure changes often."
+msgstr "<emphasis role=\"bold\">remove-table</emphasis>:这个可选元素如果为 true,表示在卸载应用程序时 JBoss 应该试图删除 <literal>relation-table</literal>。这个选项在部署早期表结构经常改变时很有用处。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:811
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">row-locking</emphasis>: This optional element if "
-"true indicates JBoss should lock all rows loaded in a transaction. Most "
-"databases implement this by using the <literal>SELECT FOR UPDATE</literal> "
-"syntax when loading the entity, but the actual syntax is determined by the "
-"<literal>row-locking-template</literal> in the <literal>datasource-mapping</"
-"literal> used by this entity."
-msgstr ""
-"<emphasis role=\"bold\">row-locking</emphasis>:这个可选元素如果为 true,表"
-"示 JBoss 应该锁定在事务里加载的所有记录。在载入 entity 时,大多数数据库都用 "
-"<literal>SELECT FOR UPDATE</literal> 语法来实现这一点,但实际的语法由 entity "
-"使用的 <literal>datasource-mapping</literal> 里的 <literal>row-locking-"
-"template</literal> 所决定。 "
+msgid "<emphasis role=\"bold\">row-locking</emphasis>: This optional element if true indicates JBoss should lock all rows loaded in a transaction. Most databases implement this by using the <literal>SELECT FOR UPDATE</literal> syntax when loading the entity, but the actual syntax is determined by the <literal>row-locking-template</literal> in the <literal>datasource-mapping</literal> used by this entity."
+msgstr "<emphasis role=\"bold\">row-locking</emphasis>:这个可选元素如果为 true,表示 JBoss 应该锁定在事务里加载的所有记录。在载入 entity 时,大多数数据库都用 <literal>SELECT FOR UPDATE</literal> 语法来实现这一点,但实际的语法由 entity 使用的 <literal>datasource-mapping</literal> 里的 <literal>row-locking-template</literal> 所决定。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:816
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">pk-constraint</emphasis>: This optional element if "
-"true indicates JBoss should add a primary key constraint when creating "
-"tables."
-msgstr ""
-"<emphasis role=\"bold\">pk-constraint</emphasis>:这个可选元素如果为 true,表"
-"示在创建表时 JBoss 应该添加一个主键约束。 "
+msgid "<emphasis role=\"bold\">pk-constraint</emphasis>: This optional element if true indicates JBoss should add a primary key constraint when creating tables."
+msgstr "<emphasis role=\"bold\">pk-constraint</emphasis>:这个可选元素如果为 true,表示在创建表时 JBoss 应该添加一个主键约束。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:828
@@ -3639,21 +2368,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:829
 #, no-c-format
-msgid ""
-"Entity beans allow for two types of queries: finders and selects. A finder "
-"provides queries on an entity bean to clients of the bean. The select method "
-"is designed to provide private query statements to an entity implementation. "
-"Unlike finders, which are restricted to only return entities of the same "
-"type as the home interface on which they are defined, select methods can "
-"return any entity type or just one field of the entity. EJB-QL is the query "
-"language used to specify finders and select methods in a platform "
-"independent way."
-msgstr ""
-"Entity bean 允许两种类型的查询:finder 和 select。finder 提供对 bean 的客户的"
-"查询。select 方法则提供对 entity 实现的查询语句。不象 finder 只能返回和所定义"
-"的 home 接口相同类型的 entity,select 方法可以返回任何类型的 entity 或者仅是 "
-"entity 的一个字段。EJB-QL 是用来以独立于平台的方式指定 finder 和 select 的查"
-"询语言。 "
+msgid "Entity beans allow for two types of queries: finders and selects. A finder provides queries on an entity bean to clients of the bean. The select method is designed to provide private query statements to an entity implementation. Unlike finders, which are restricted to only return entities of the same type as the home interface on which they are defined, select methods can return any entity type or just one field of the entity. EJB-QL is the query language used to specify finders and select methods in a platform independent way."
+msgstr "Entity bean 允许两种类型的查询:finder 和 select。finder 提供对 bean 的客户的查询。select 方法则提供对 entity 实现的查询语句。不象 finder 只能返回和所定义的 home 接口相同类型的 entity,select 方法可以返回任何类型的 entity 或者仅是 entity 的一个字段。EJB-QL 是用来以独立于平台的方式指定 finder 和 select 的查询语言。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:833
@@ -3664,20 +2380,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:834
 #, no-c-format
-msgid ""
-"The declaration of finders has not changed in CMP 2.0. Finders are still "
-"declared in the home interface (local or remote) of the entity. Finders "
-"defined on the local home interface do not throw a RemoteException. The "
-"following code declares the <literal>findBadDudes_ejbql</literal> finder on "
-"the <literal>GangsterHome</literal> interface. The <literal>ejbql</literal> "
-"suffix here is not required. It is simply a naming convention used here to "
-"differentiate the different types of query specifications we will be looking "
-"at."
-msgstr ""
-"Finder 的声明在 CMP 2.0 里没有变化。Finder 仍然在 entity 的 home 接口(local "
-"或 remote)里进行声明。下面的代码声明了 <literal>GangsterHome</literal> 接口"
-"上的 <literal>findBadDudes_ejbql</literal> finder。这里所使用的命名规则用来区"
-"分不同的查询类型。 "
+msgid "The declaration of finders has not changed in CMP 2.0. Finders are still declared in the home interface (local or remote) of the entity. Finders defined on the local home interface do not throw a RemoteException. The following code declares the <literal>findBadDudes_ejbql</literal> finder on the <literal>GangsterHome</literal> interface. The <literal>ejbql</literal> suffix here is not required. It is simply a naming convention used here to differentiate the different types of query specifications we will be looking at."
+msgstr "Finder 的声明在 CMP 2.0 里没有变化。Finder 仍然在 entity 的 home 接口(local 或 remote)里进行声明。下面的代码声明了 <literal>GangsterHome</literal> 接口上的 <literal>findBadDudes_ejbql</literal> finder。这里所使用的命名规则用来区分不同的查询类型。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:837
@@ -3698,15 +2402,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:838
 #, no-c-format
-msgid ""
-"Select methods are declared in the entity implementation class, and must be "
-"public and abstract just like CMP and CMR field abstract accessors and must "
-"throw a <literal>FinderException</literal>. The following code declares an "
-"select method:"
-msgstr ""
-"Select 方法在 entity 实现类进行声明,且必须为 public 和 abstract,就象 CMP "
-"和 CMR 字段的 abstract accessor 一样,它也必须抛出 <literal>FinderException</"
-"literal>。下面的代码声明了一个 select 方法: "
+msgid "Select methods are declared in the entity implementation class, and must be public and abstract just like CMP and CMR field abstract accessors and must throw a <literal>FinderException</literal>. The following code declares an select method:"
+msgstr "Select 方法在 entity 实现类进行声明,且必须为 public 和 abstract,就象 CMP 和 CMR 字段的 abstract accessor 一样,它也必须抛出 <literal>FinderException</literal>。下面的代码声明了一个 select 方法: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:841
@@ -3735,18 +2432,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:846
 #, no-c-format
-msgid ""
-"Every select or finder method (except <literal>findByPrimaryKey</literal>) "
-"must have an EJB-QL query defined in the <literal>ejb-jar.xml</literal> "
-"file. The EJB-QL query is declared in a query element, which is contained in "
-"the entity element. The following are the declarations for "
-"<literal>findBadDudes_ejbql</literal> and <literal>ejbSelectBoss_ejbql</"
-"literal> queries:"
-msgstr ""
-"每个 select 或 finder 方法(除了 <literal>findByPrimaryKey</literal>)都必须"
-"在 <literal>ejb-jar.xml</literal> 文件里定义一个 EJB-QL 查询。EJB-QL 查询在 "
-"entity 元素的 query 元素里进行定义。下面是对 <literal>findBadDudes_ejbql</"
-"literal> 和 <literal>ejbSelectBoss_ejbql</literal> 查询的声明: "
+msgid "Every select or finder method (except <literal>findByPrimaryKey</literal>) must have an EJB-QL query defined in the <literal>ejb-jar.xml</literal> file. The EJB-QL query is declared in a query element, which is contained in the entity element. The following are the declarations for <literal>findBadDudes_ejbql</literal> and <literal>ejbSelectBoss_ejbql</literal> queries:"
+msgstr "每个 select 或 finder 方法(除了 <literal>findByPrimaryKey</literal>)都必须在 <literal>ejb-jar.xml</literal> 文件里定义一个 EJB-QL 查询。EJB-QL 查询在 entity 元素的 query 元素里进行定义。下面是对 <literal>findBadDudes_ejbql</literal> 和 <literal>ejbSelectBoss_ejbql</literal> 查询的声明: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:849
@@ -3759,30 +2446,24 @@
 "            &lt;!-- ... --&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;<emphasis role=\"bold"
-"\">findBadDudes_ejbql</emphasis>&lt;/method-name&gt;\n"
+"                    &lt;method-name&gt;<emphasis role=\"bold\">findBadDudes_ejbql</emphasis>&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;ejb-ql&gt;&lt;![CDATA[\n"
-"                 <emphasis role=\"bold\">SELECT OBJECT(g) FROM gangster g "
-"WHERE g.badness &gt; ?1</emphasis>\n"
+"                 <emphasis role=\"bold\">SELECT OBJECT(g) FROM gangster g WHERE g.badness &gt; ?1</emphasis>\n"
 "                 ]]&gt;&lt;/ejb-ql&gt;\n"
 "            &lt;/query&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;<emphasis role=\"bold"
-"\">ejbSelectBoss_ejbql</emphasis>&lt;/method-name&gt;\n"
+"                    &lt;method-name&gt;<emphasis role=\"bold\">ejbSelectBoss_ejbql</emphasis>&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;ejb-ql&gt;&lt;![CDATA[\n"
-"                 <emphasis role=\"bold\">SELECT DISTINCT underling."
-"organization.theBoss FROM gangster underling WHERE underling.name = ?1 OR "
-"underling.nickName = ?1</emphasis>\n"
+"                 <emphasis role=\"bold\">SELECT DISTINCT underling.organization.theBoss FROM gangster underling WHERE underling.name = ?1 OR underling.nickName = ?1</emphasis>\n"
 "                 ]]&gt;&lt;/ejb-ql&gt;\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
@@ -3796,30 +2477,24 @@
 "            &lt;!-- ... --&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;<emphasis role=\"bold"
-"\">findBadDudes_ejbql</emphasis>&lt;/method-name&gt;\n"
+"                    &lt;method-name&gt;<emphasis role=\"bold\">findBadDudes_ejbql</emphasis>&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;ejb-ql&gt;&lt;![CDATA[\n"
-"                 <emphasis role=\"bold\">SELECT OBJECT(g) FROM gangster g "
-"WHERE g.badness &gt; ?1</emphasis>\n"
+"                 <emphasis role=\"bold\">SELECT OBJECT(g) FROM gangster g WHERE g.badness &gt; ?1</emphasis>\n"
 "                 ]]&gt;&lt;/ejb-ql&gt;\n"
 "            &lt;/query&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;<emphasis role=\"bold"
-"\">ejbSelectBoss_ejbql</emphasis>&lt;/method-name&gt;\n"
+"                    &lt;method-name&gt;<emphasis role=\"bold\">ejbSelectBoss_ejbql</emphasis>&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;ejb-ql&gt;&lt;![CDATA[\n"
-"                 <emphasis role=\"bold\">SELECT DISTINCT underling."
-"organization.theBoss FROM gangster underling WHERE underling.name = ?1 OR "
-"underling.nickName = ?1</emphasis>\n"
+"                 <emphasis role=\"bold\">SELECT DISTINCT underling.organization.theBoss FROM gangster underling WHERE underling.name = ?1 OR underling.nickName = ?1</emphasis>\n"
 "                 ]]&gt;&lt;/ejb-ql&gt;\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
@@ -3829,29 +2504,19 @@
 #. Tag: para
 #: The_CMP_Engine.xml:850
 #, no-c-format
-msgid ""
-"EJB-QL is similar to SQL but has some surprising differences. The following "
-"are some important things to note about EJB-QL:"
-msgstr ""
-"EJB-QL 和 SQL 类似,但它有一些令人惊讶的区别。下面是 EJB-QL 一些值得注意的东"
-"西: "
+msgid "EJB-QL is similar to SQL but has some surprising differences. The following are some important things to note about EJB-QL:"
+msgstr "EJB-QL 和 SQL 类似,但它有一些令人惊讶的区别。下面是 EJB-QL 一些值得注意的东西: "
 
 #. Tag: para
 #: The_CMP_Engine.xml:855
 #, no-c-format
-msgid ""
-"EJB-QL is a typed language, meaning that it only allows comparison of like "
-"types (i.e., strings can only be compared with strings)."
-msgstr ""
-"EJB-QL 是一个强类型的语言,这意味着它只允许同类型间的比较(也就是说,字符串只"
-"能和字符串比较)。 "
+msgid "EJB-QL is a typed language, meaning that it only allows comparison of like types (i.e., strings can only be compared with strings)."
+msgstr "EJB-QL 是一个强类型的语言,这意味着它只允许同类型间的比较(也就是说,字符串只能和字符串比较)。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:860
 #, no-c-format
-msgid ""
-"In an equals comparison a variable (single valued path) must be on the left "
-"hand side. Some examples follow:"
+msgid "In an equals comparison a variable (single valued path) must be on the left hand side. Some examples follow:"
 msgstr "在等式里,变量必须在左侧。下面是一些例子: "
 
 #. Tag: programlisting
@@ -3879,9 +2544,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:873
 #, no-c-format
-msgid ""
-"Parameters are only allowed on the right hand side of a comparison. For "
-"example:"
+msgid "Parameters are only allowed on the right hand side of a comparison. For example:"
 msgstr "参数只被允许在等式的右边。例如: "
 
 #. Tag: programlisting
@@ -3903,22 +2566,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:883
 #, 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 "
-"declaration, but the <literal>ejb-ql</literal> element can be left empty. "
-"Currently the SQL can be overridden with JBossQL, DynamicQL, DeclaredSQL or "
-"a BMP style custom <literal>ejbFind</literal> method. All EJB-QL overrides "
-"are non-standard extensions to the EJB specification, so use of these "
-"extensions will limit portability of your application. All of the EJB-QL "
-"overrides, except for BMP custom finders, are declared using a "
-"<literal>query</literal> element in the jbosscmp-jdbc.xml file. Tthe content "
-"model is shown in <xref linkend=\"Overriding_the_EJB_QL_to_SQL_Mapping-"
-"The_jbosscmp_jdbc_query_element_content_model\"/>."
-msgstr ""
-"EJB-QL 查询可以在 <literal>jbosscmp-jdbc.xml</"
-"literal> 文件里进行覆盖。EJB-QL 查询仍然需要 finder 或 select,但 <literal>ejb-ql</literal> 元素可以为空。目前 SQL 可以用 JBossQL、 DynamicQL、DeclaredSQL 或 BMP 风格的自定义 <literal>ejbFind</literal> 方法来覆盖。所有的 EJB-QL 覆盖都是对 EJB 规格的非标准扩展,所有对这些扩展的使用将限制应用程序的可移植性。所有的 EJB-QL 覆盖,除了 BMP 自定义的 finder,都在 jbosscmp-jdbc.xml 里使用 <literal>query</literal> 元素进行声明。<xref linkend=\"Overriding_the_EJB_QL_to_SQL_Mapping-"
-"The_jbosscmp_jdbc_query_element_content_model\"/> 展示了其内容模型。"
+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 declaration, but the <literal>ejb-ql</literal> element can be left empty. Currently the SQL can be overridden with JBossQL, DynamicQL, DeclaredSQL or a BMP style custom <literal>ejbFind</literal> method. All EJB-QL overrides are non-standard extensions to the EJB specification, so use of these extensions will limit portability of your application. All of the EJB-QL overrides, except for BMP custom finders, are declared using a <literal>query</literal> element in the jbosscmp-jdbc.xml file. Tthe content model is shown in <xref linkend=\"Overriding_the_EJB_QL_to_SQL_Mapping-The_jbosscmp_jdbc_query_element_content_model\"/>."
+msgstr "EJB-QL 查询可以在 <literal>jbosscmp-jdbc.xml</literal> 文件里进行覆盖。EJB-QL 查询仍然需要 finder 或 select,但 <literal>ejb-ql</literal> 元素可以为空。目前 SQL 可以用 JBossQL、 DynamicQL、DeclaredSQL 或 BMP 风格的自定义 <literal>ejbFind</literal> 方法来覆盖。所有的 EJB-QL 覆盖都是对 EJB 规格的非标准扩展,所有对这些扩展的使用将限制应用程序的可移植性。所有的 EJB-QL 覆盖,除了 BMP 自定义的 finder,都在 jbosscmp-jdbc.xml 里使用 <literal>query</literal> 元素进行声明。<xref linkend=\"Overriding_the_EJB_QL_to_SQL_Mapping-The_jbosscmp_jdbc_query_element_content_model\"/> 展示了其内容模型。"
 
 #. Tag: title
 #: The_CMP_Engine.xml:887
@@ -3929,69 +2578,38 @@
 #. Tag: para
 #: The_CMP_Engine.xml:896
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">description</emphasis>: An optional description for "
-"the query."
+msgid "<emphasis role=\"bold\">description</emphasis>: An optional description for the query."
 msgstr "<emphasis role=\"bold\">description</emphasis>:查询的可选描述。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:901
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">query-method</emphasis>: This required element "
-"specifies the query method that being configured. This must match a "
-"<literal>query-method</literal> declared for this entity in the <literal>ejb-"
-"jar.xml</literal> file."
-msgstr ""
-"<emphasis role=\"bold\">query-method</emphasis>:这个可选元素指定了所配置的查"
-"询方法。它必须匹配 <literal>ejb-jar.xml</literal> 文件里为这个 entity 声明的 "
-"<literal>query-method</literal>。 "
+msgid "<emphasis role=\"bold\">query-method</emphasis>: This required element specifies the query method that being configured. This must match a <literal>query-method</literal> declared for this entity in the <literal>ejb-jar.xml</literal> file."
+msgstr "<emphasis role=\"bold\">query-method</emphasis>:这个可选元素指定了所配置的查询方法。它必须匹配 <literal>ejb-jar.xml</literal> 文件里为这个 entity 声明的 <literal>query-method</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:906
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">jboss-ql</emphasis>: This is a JBossQL query to use "
-"in place of the EJB-QL query. JBossQL is discussed in <xref linkend="
-"\"Queries-JBossQL\"/>."
-msgstr ""
-"<emphasis role=\"bold\">jboss-ql</emphasis>:这是用来替代 EJB-QL 查询的 "
-"JBossQL 查询。JBossQL 将在 <xref linkend=\"Queries-JBossQL\"/> 里进行讨论。 "
+msgid "<emphasis role=\"bold\">jboss-ql</emphasis>: This is a JBossQL query to use in place of the EJB-QL query. JBossQL is discussed in <xref linkend=\"Queries-JBossQL\"/>."
+msgstr "<emphasis role=\"bold\">jboss-ql</emphasis>:这是用来替代 EJB-QL 查询的 JBossQL 查询。JBossQL 将在 <xref linkend=\"Queries-JBossQL\"/> 里进行讨论。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:911
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">dynamic-ql</emphasis>: This indicated that the "
-"method is a dynamic query method and not an EJB-QL query. Dynamic queries "
-"are discussed in <xref linkend=\"Queries-DynamicQL\"/>."
-msgstr ""
-"<emphasis role=\"bold\">dynamic-ql</emphasis>:它指出该方法是一个动态查询方法"
-"而不是 EJB-QL 查询。<xref linkend=\"Queries-DynamicQL\"/> 将讨论动态查询。 "
+msgid "<emphasis role=\"bold\">dynamic-ql</emphasis>: This indicated that the method is a dynamic query method and not an EJB-QL query. Dynamic queries are discussed in <xref linkend=\"Queries-DynamicQL\"/>."
+msgstr "<emphasis role=\"bold\">dynamic-ql</emphasis>:它指出该方法是一个动态查询方法而不是 EJB-QL 查询。<xref linkend=\"Queries-DynamicQL\"/> 将讨论动态查询。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:916
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">declared-sql</emphasis>: This query uses declared "
-"SQL in place of the EJB-QL query. Declared SQL is discussed in <xref linkend="
-"\"Queries-DeclaredSQL\"/>."
-msgstr ""
-"<emphasis role=\"bold\">declared-sql</emphasis>:这个查询使用声明式 SQL 来代"
-"替 EJB-QL 查询。<xref linkend=\"Queries-DeclaredSQL\"/> 将讨论声明式 SQL。 "
+msgid "<emphasis role=\"bold\">declared-sql</emphasis>: This query uses declared SQL in place of the EJB-QL query. Declared SQL is discussed in <xref linkend=\"Queries-DeclaredSQL\"/>."
+msgstr "<emphasis role=\"bold\">declared-sql</emphasis>:这个查询使用声明式 SQL 来代替 EJB-QL 查询。<xref linkend=\"Queries-DeclaredSQL\"/> 将讨论声明式 SQL。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:921
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-ahead</emphasis>: This optional element allows "
-"one to optimize the loading of additional fields for use with the entities "
-"referenced by the query. This is discussed in detail in <xref linkend="
-"\"The_CMP_Engine-Optimized_Loading\"/>."
-msgstr ""
-"<emphasis role=\"bold\">read-ahead</emphasis>:这个可选元素允许你优化对查询所"
-"引用的 entity 的其他字段的加载。这将在 <xref linkend=\"The_CMP_Engine-"
-"Optimized_Loading\"/> 里进行详细讨论。 "
+msgid "<emphasis role=\"bold\">read-ahead</emphasis>: This optional element allows one to optimize the loading of additional fields for use with the entities referenced by the query. This is discussed in detail in <xref linkend=\"The_CMP_Engine-Optimized_Loading\"/>."
+msgstr "<emphasis role=\"bold\">read-ahead</emphasis>:这个可选元素允许你优化对查询所引用的 entity 的其他字段的加载。这将在 <xref linkend=\"The_CMP_Engine-Optimized_Loading\"/> 里进行详细讨论。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:929
@@ -4002,37 +2620,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:930
 #, no-c-format
-msgid ""
-"JBossQL is a superset of EJB-QL that is designed to address some of the "
-"inadequacies of EJB-QL. In addition to a more flexible syntax, new "
-"functions, key words, and clauses have been added to JBossQL. At the time of "
-"this writing, JBossQL includes support for an <literal>ORDER BY</literal>, "
-"<literal>OFFSET</literal> and <literal>LIMIT</literal> clauses, parameters "
-"in the <literal>IN</literal> and <literal>LIKE</literal> operators, the "
-"<literal>COUNT</literal>, <literal>MAX</literal>, <literal>MIN</literal>, "
-"<literal>AVG</literal>, <literal>SUM</literal>, <literal>UCASE</literal> and "
-"<literal>LCASE</literal> functions. Queries can also include functions in "
-"the <literal>SELECT</literal> clause for select methods."
-msgstr ""
-"JBossQL 是 EJB-QL 的一个超集,它的设计目的是解决 EJB-QL 的不足。出了更为灵活"
-"的语法JBossQL 也添加了新的功能、关键字和子句。在编写本文档之时,JBossQL 已支"
-"持 <literal>ORDER BY</literal>、<literal>OFFSET</literal> 和 <literal>LIMIT</"
-"literal> 子句,<literal>IN</literal> 和 <literal>LIKE</literal> 操作符里的参"
-"数,<literal>COUNT</literal>、<literal>MAX</literal>、 <literal>MIN</"
-"literal>、<literal>AVG</literal>、<literal>SUM</literal>、<literal>UCASE</"
-"literal> 和 <literal>LCASE</literal> 函数。查询也可以在 <literal>SELECT</"
-"literal> 子句里包含函数。 "
+msgid "JBossQL is a superset of EJB-QL that is designed to address some of the inadequacies of EJB-QL. In addition to a more flexible syntax, new functions, key words, and clauses have been added to JBossQL. At the time of this writing, JBossQL includes support for an <literal>ORDER BY</literal>, <literal>OFFSET</literal> and <literal>LIMIT</literal> clauses, parameters in the <literal>IN</literal> and <literal>LIKE</literal> operators, the <literal>COUNT</literal>, <literal>MAX</literal>, <literal>MIN</literal>, <literal>AVG</literal>, <literal>SUM</literal>, <literal>UCASE</literal> and <literal>LCASE</literal> functions. Queries can also include functions in the <literal>SELECT</literal> clause for select methods."
+msgstr "JBossQL 是 EJB-QL 的一个超集,它的设计目的是解决 EJB-QL 的不足。出了更为灵活的语法JBossQL 也添加了新的功能、关键字和子句。在编写本文档之时,JBossQL 已支持 <literal>ORDER BY</literal>、<literal>OFFSET</literal> 和 <literal>LIMIT</literal> 子句,<literal>IN</literal> 和 <literal>LIKE</literal> 操作符里的参数,<literal>COUNT</literal>、<literal>MAX</literal>、 <literal>MIN</literal>、<literal>AVG</literal>、<literal>SUM</literal>、<literal>UCASE</literal> 和 <literal>LCASE</literal> 函数。查询也可以在 <literal>SELECT</literal> 子句里包含函数。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:933
 #, no-c-format
-msgid ""
-"JBossQL is declared in the <literal>jbosscmp-jdbc.xml</literal> file with a "
-"<literal>jboss-ql</literal> element containing the JBossQL query. The "
-"following example provides an example JBossQL declaration."
-msgstr ""
-"JBossQL 在 <literal>jbosscmp-jdbc.xml</literal> 文件里用包含 JBossQL 查询的 "
-"<literal>jboss-ql</literal> 元素进行声明。下面是一个 JBossQL 声明的例子。 "
+msgid "JBossQL is declared in the <literal>jbosscmp-jdbc.xml</literal> file with a <literal>jboss-ql</literal> element containing the JBossQL query. The following example provides an example JBossQL declaration."
+msgstr "JBossQL 在 <literal>jbosscmp-jdbc.xml</literal> 文件里用包含 JBossQL 查询的 <literal>jboss-ql</literal> 元素进行声明。下面是一个 JBossQL 声明的例子。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:936
@@ -4044,15 +2639,12 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;findBadDudes_jbossql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;findBadDudes_jbossql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
-"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT "
-"OBJECT(g) FROM gangster g WHERE g.badness &gt; ?1 ORDER BY g.badness DESC ]]"
-"&gt;&lt;/jboss-ql&gt;</emphasis>\n"
+"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT OBJECT(g) FROM gangster g WHERE g.badness &gt; ?1 ORDER BY g.badness DESC ]]&gt;&lt;/jboss-ql&gt;</emphasis>\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
 "    &lt;/enterprise-beans&gt;\n"
@@ -4064,15 +2656,12 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;findBadDudes_jbossql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;findBadDudes_jbossql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
-"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT "
-"OBJECT(g) FROM gangster g WHERE g.badness &gt; ?1 ORDER BY g.badness DESC ]]"
-"&gt;&lt;/jboss-ql&gt;</emphasis>\n"
+"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT OBJECT(g) FROM gangster g WHERE g.badness &gt; ?1 ORDER BY g.badness DESC ]]&gt;&lt;/jboss-ql&gt;</emphasis>\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
 "    &lt;/enterprise-beans&gt;\n"
@@ -4101,16 +2690,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:941
 #, no-c-format
-msgid ""
-"Another capability of JBossQL is the ability to retrieve finder results in "
-"blocks using the <literal>LIMIT</literal> and <literal>OFFSET</literal> "
-"functions. For example, to iterate through the large number of jobs "
-"performed, the following <literal>findManyJobs_jbossql</literal> finder may "
-"be defined."
-msgstr ""
-"JBossQL 的另外一个能力是用 <literal>LIMIT</literal> 和 <literal>OFFSET</"
-"literal> 函数从块里获取 finder 结果。例如,要重复大量的任务,你可以定义下面"
-"的 <literal>findManyJobs_jbossql</literal> finder。 "
+msgid "Another capability of JBossQL is the ability to retrieve finder results in blocks using the <literal>LIMIT</literal> and <literal>OFFSET</literal> functions. For example, to iterate through the large number of jobs performed, the following <literal>findManyJobs_jbossql</literal> finder may be defined."
+msgstr "JBossQL 的另外一个能力是用 <literal>LIMIT</literal> 和 <literal>OFFSET</literal> 函数从块里获取 finder 结果。例如,要重复大量的任务,你可以定义下面的 <literal>findManyJobs_jbossql</literal> finder。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:944
@@ -4122,8 +2703,7 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;findManyJobs_jbossql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;findManyJobs_jbossql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
@@ -4131,8 +2711,7 @@
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
-"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT "
-"OBJECT(j) FROM jobs j OFFSET ?1 LIMIT ?2 ]]&gt;&lt;/jboss-ql&gt;</emphasis>\n"
+"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT OBJECT(j) FROM jobs j OFFSET ?1 LIMIT ?2 ]]&gt;&lt;/jboss-ql&gt;</emphasis>\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
 "    &lt;/enterprise-beans&gt;\n"
@@ -4144,8 +2723,7 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;findManyJobs_jbossql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;findManyJobs_jbossql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
@@ -4153,8 +2731,7 @@
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
-"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT "
-"OBJECT(j) FROM jobs j OFFSET ?1 LIMIT ?2 ]]&gt;&lt;/jboss-ql&gt;</emphasis>\n"
+"                <emphasis role=\"bold\">&lt;jboss-ql&gt;&lt;![CDATA[ SELECT OBJECT(j) FROM jobs j OFFSET ?1 LIMIT ?2 ]]&gt;&lt;/jboss-ql&gt;</emphasis>\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
 "    &lt;/enterprise-beans&gt;\n"
@@ -4169,17 +2746,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:949
 #, no-c-format
-msgid ""
-"DynamicQL allows the runtime generation and execution of JBossQL queries. A "
-"DynamicQL query method is an abstract method that takes a JBossQL query and "
-"the query arguments as parameters. JBoss compiles the JBossQL and executes "
-"the generated SQL. The following generates a JBossQL query that selects all "
-"the gangsters that have a hangout in any state in the states set:"
-msgstr ""
-"DynamicQL 允许在运行时生成和执行 JBossQL 查询。DynamicQL 查询方法是一个 "
-"abstract 方法,它把 JBossQL 查询及其参数作为参数。JBoss 编译 JBossQL 并执行所"
-"生成的 SQL。下面的例子生成了一个 JBossQL 查询,它选择了所有在州集合里的任何州"
-"里具有聚齐处的 gangster: "
+msgid "DynamicQL allows the runtime generation and execution of JBossQL queries. A DynamicQL query method is an abstract method that takes a JBossQL query and the query arguments as parameters. JBoss compiles the JBossQL and executes the generated SQL. The following generates a JBossQL query that selects all the gangsters that have a hangout in any state in the states set:"
+msgstr "DynamicQL 允许在运行时生成和执行 JBossQL 查询。DynamicQL 查询方法是一个 abstract 方法,它把 JBossQL 查询及其参数作为参数。JBoss 编译 JBossQL 并执行所生成的 SQL。下面的例子生成了一个 JBossQL 查询,它选择了所有在州集合里的任何州里具有聚齐处的 gangster: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:952
@@ -4248,17 +2816,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:953
 #, no-c-format
-msgid ""
-"The DynamicQL select method may have any valid select method name, but the "
-"method must always take a string and an object array as parameters. "
-"DynamicQL is declared in the <literal>jbosscmp-jdbc.xml</literal> file with "
-"an empty <literal>dynamic-ql</literal> element. The following is the "
-"declaration for <literal>ejbSelectGeneric</literal>."
-msgstr ""
-"DynamicQL 的 select 方法可能具有任何有效的名称,但这个方法必须把一个字符串和"
-"一个对象数组作为参数。DynamicQL 在 <literal>jbosscmp-jdbc.xml</literal> 文件"
-"里用一个空的 <literal>dynamic-ql</literal> 元素进行声明。下面是对 "
-"<literal>ejbSelectGeneric</literal> 的声明。 "
+msgid "The DynamicQL select method may have any valid select method name, but the method must always take a string and an object array as parameters. DynamicQL is declared in the <literal>jbosscmp-jdbc.xml</literal> file with an empty <literal>dynamic-ql</literal> element. The following is the declaration for <literal>ejbSelectGeneric</literal>."
+msgstr "DynamicQL 的 select 方法可能具有任何有效的名称,但这个方法必须把一个字符串和一个对象数组作为参数。DynamicQL 在 <literal>jbosscmp-jdbc.xml</literal> 文件里用一个空的 <literal>dynamic-ql</literal> 元素进行声明。下面是对 <literal>ejbSelectGeneric</literal> 的声明。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:956
@@ -4272,10 +2831,8 @@
 "                &lt;query-method&gt;\n"
 "                    &lt;method-name&gt;ejbSelectGeneric&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
-"                        &lt;method-param&gt;java.lang.Object[]&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
+"                        &lt;method-param&gt;java.lang.Object[]&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                <emphasis role=\"bold\">&lt;dynamic-ql/&gt;</emphasis>\n"
@@ -4292,10 +2849,8 @@
 "                &lt;query-method&gt;\n"
 "                    &lt;method-name&gt;ejbSelectGeneric&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
-"                        &lt;method-param&gt;java.lang.Object[]&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
+"                        &lt;method-param&gt;java.lang.Object[]&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                <emphasis role=\"bold\">&lt;dynamic-ql/&gt;</emphasis>\n"
@@ -4313,19 +2868,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:961
 #, no-c-format
-msgid ""
-"DeclaredSQL is based on the legacy JAWS CMP 1.1 engine finder declaration, "
-"but has been updated for CMP 2.0. Commonly this declaration is used to limit "
-"a query with a <literal>WHERE</literal> clause that cannot be represented in "
-"q EJB-QL or JBossQL. The content model for the declared-sql element is given "
-"in <xref linkend=\"DeclaredSQL-"
-"The_jbosscmp_jdbc_declared_sql_element_content_model.\"/>."
-msgstr ""
-"DeclaredSQL 基于遗留的JAWS CMP 1.1 engine finder 的声明,但它现在已升级到 "
-"CMP 2.0 了。通常这个声明用来限制带有不能在 EJB-QL 或 JBossQL 里使用的 "
-"<literal>WHERE</literal> 子句的查询。<xref linkend=\"DeclaredSQL-"
-"The_jbosscmp_jdbc_declared_sql_element_content_model.\"/> 给出了 declared-"
-"sql 元素的内容模型。 "
+msgid "DeclaredSQL is based on the legacy JAWS CMP 1.1 engine finder declaration, but has been updated for CMP 2.0. Commonly this declaration is used to limit a query with a <literal>WHERE</literal> clause that cannot be represented in q EJB-QL or JBossQL. The content model for the declared-sql element is given in <xref linkend=\"DeclaredSQL-The_jbosscmp_jdbc_declared_sql_element_content_model.\"/>."
+msgstr "DeclaredSQL 基于遗留的JAWS CMP 1.1 engine finder 的声明,但它现在已升级到 CMP 2.0 了。通常这个声明用来限制带有不能在 EJB-QL 或 JBossQL 里使用的 <literal>WHERE</literal> 子句的查询。<xref linkend=\"DeclaredSQL-The_jbosscmp_jdbc_declared_sql_element_content_model.\"/> 给出了 declared-sql 元素的内容模型。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:965
@@ -4336,114 +2880,62 @@
 #. Tag: para
 #: The_CMP_Engine.xml:974
 #, 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> 元素指定"
-"所选择的内容,它由下面的元素组成: "
+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
-msgid ""
-"<emphasis role=\"bold\">distinct</emphasis>: If this empty element is "
-"present, JBoss will add the <literal>DISTINCT</literal> keyword to the "
-"generated <literal>SELECT</literal> clause. The default is to use "
-"<literal>DISTINCT</literal> if method returns a <literal>java.util.Set</"
-"literal>"
-msgstr ""
-"<emphasis role=\"bold\">distinct</emphasis>:如果使用了这个空的元素,JBoss 将"
-"把 <literal>DISTINCT</literal> 关键字添加到生成的 <literal>SELECT</literal> "
-"子句里。如果方法返回 <literal>java.util.Set</literal> 则会缺省使用 "
-"<literal>DISTINCT</literal>。 "
+msgid "<emphasis role=\"bold\">distinct</emphasis>: If this empty element is present, JBoss will add the <literal>DISTINCT</literal> keyword to the generated <literal>SELECT</literal> clause. The default is to use <literal>DISTINCT</literal> if method returns a <literal>java.util.Set</literal>"
+msgstr "<emphasis role=\"bold\">distinct</emphasis>:如果使用了这个空的元素,JBoss 将把 <literal>DISTINCT</literal> 关键字添加到生成的 <literal>SELECT</literal> 子句里。如果方法返回 <literal>java.util.Set</literal> 则会缺省使用 <literal>DISTINCT</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:984
 #, 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 方法时才是必需的。 "
+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 方法时才是必需的。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:989
 #, 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。 "
+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。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:994
 #, 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>。 "
+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>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:999
 #, no-c-format
-msgid ""
-"<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 ""
-"<emphasis role=\"bold\">additional-columns</emphasis>:声明其他列来满足按任意"
-"带有 finder 的列排序的需要或者利用 select 里的集合函数(aggregate "
-"function)。 "
+msgid "<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 "<emphasis role=\"bold\">additional-columns</emphasis>:声明其他列来满足按任意带有 finder 的列排序的需要或者利用 select 里的集合函数(aggregate function)。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1006
 #, 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。 "
+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。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1011
 #, 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> 子句。 "
+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> 子句。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1016
 #, 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> 子句。 "
+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> 子句。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1021
 #, 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。 "
+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。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1026
@@ -4461,17 +2953,14 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;findBadDudes_declaredsql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;findBadDudes_declaredsql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;declared-sql&gt;\n"
-"                    &lt;where&gt;&lt;![CDATA[ badness &gt; {0} ]]&gt;&lt;/"
-"where&gt;\n"
-"                    &lt;order&gt;&lt;![CDATA[ badness DESC ]]&gt;&lt;/"
-"order&gt;\n"
+"                    &lt;where&gt;&lt;![CDATA[ badness &gt; {0} ]]&gt;&lt;/where&gt;\n"
+"                    &lt;order&gt;&lt;![CDATA[ badness DESC ]]&gt;&lt;/order&gt;\n"
 "                &lt;/declared-sql&gt;\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
@@ -4484,17 +2973,14 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;findBadDudes_declaredsql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;findBadDudes_declaredsql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
 "                        &lt;method-param&gt;int&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;declared-sql&gt;\n"
-"                    &lt;where&gt;&lt;![CDATA[ badness &gt; {0} ]]&gt;&lt;/"
-"where&gt;\n"
-"                    &lt;order&gt;&lt;![CDATA[ badness DESC ]]&gt;&lt;/"
-"order&gt;\n"
+"                    &lt;where&gt;&lt;![CDATA[ badness &gt; {0} ]]&gt;&lt;/where&gt;\n"
+"                    &lt;order&gt;&lt;![CDATA[ badness DESC ]]&gt;&lt;/order&gt;\n"
 "                &lt;/declared-sql&gt;\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
@@ -4502,7 +2988,9 @@
 "&lt;/jbosscmp-jdbc&gt;"
 
 #. Tag: para
-#: The_CMP_Engine.xml:1030 The_CMP_Engine.xml:1038 The_CMP_Engine.xml:1641
+#: The_CMP_Engine.xml:1030
+#: The_CMP_Engine.xml:1038
+#: The_CMP_Engine.xml:1641
 #, no-c-format
 msgid "The generated SQL would be:"
 msgstr "生成的 SQL 将是: "
@@ -4524,19 +3012,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1034
 #, no-c-format
-msgid ""
-"As you can see, JBoss generates the <literal>SELECT</literal> and "
-"<literal>FROM</literal> clauses necessary to select the primary key for this "
-"entity. If desired an additional <literal>FROM</literal> clause can be "
-"specified that is appended to the end of the automatically generated "
-"<literal>FROM</literal> clause. The following is example DeclaredSQL "
-"declaration with an additional <literal>FROM</literal> clause."
-msgstr ""
-"你可以看到,JBoss 生成必需的 <literal>SELECT</literal> 和 <literal>FROM</"
-"literal> 子句来选择这个 entity 的主键。如果需要的话,你可以指定额外的 "
-"<literal>FROM</literal> 子句,它附加在自动生成的 <literal>FROM</literal> 子句"
-"的后面。下面是一个带有额外 <literal>FROM</literal> 子句的 DeclaredSQL 声明的"
-"例子。 "
+msgid "As you can see, JBoss generates the <literal>SELECT</literal> and <literal>FROM</literal> clauses necessary to select the primary key for this entity. If desired an additional <literal>FROM</literal> clause can be specified that is appended to the end of the automatically generated <literal>FROM</literal> clause. The following is example DeclaredSQL declaration with an additional <literal>FROM</literal> clause."
+msgstr "你可以看到,JBoss 生成必需的 <literal>SELECT</literal> 和 <literal>FROM</literal> 子句来选择这个 entity 的主键。如果需要的话,你可以指定额外的 <literal>FROM</literal> 子句,它附加在自动生成的 <literal>FROM</literal> 子句的后面。下面是一个带有额外 <literal>FROM</literal> 子句的 DeclaredSQL 声明的例子。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1037
@@ -4548,11 +3025,9 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;ejbSelectBoss_declaredsql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;ejbSelectBoss_declaredsql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;declared-sql&gt;\n"
@@ -4561,8 +3036,7 @@
 "                        &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "                        &lt;alias&gt;boss&lt;/alias&gt;\n"
 "                    &lt;/select&gt;\n"
-"                    &lt;from&gt;&lt;![CDATA[, gangster g, organization o]]"
-"&gt;&lt;/from&gt;\n"
+"                    &lt;from&gt;&lt;![CDATA[, gangster g, organization o]]&gt;&lt;/from&gt;\n"
 "                    &lt;where&gt;&lt;![CDATA[\n"
 "                     (LCASE(g.name) = {0} OR LCASE(g.nick_name) = {0}) AND\n"
 "                     g.organization = o.name AND o.the_boss = boss.id\n"
@@ -4579,11 +3053,9 @@
 "            &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;ejbSelectBoss_declaredsql&lt;/method-"
-"name&gt;\n"
+"                    &lt;method-name&gt;ejbSelectBoss_declaredsql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
 "                &lt;declared-sql&gt;\n"
@@ -4592,8 +3064,7 @@
 "                        &lt;ejb-name&gt;GangsterEJB&lt;/ejb-name&gt;\n"
 "                        &lt;alias&gt;boss&lt;/alias&gt;\n"
 "                    &lt;/select&gt;\n"
-"                    &lt;from&gt;&lt;![CDATA[, gangster g, organization o]]"
-"&gt;&lt;/from&gt;\n"
+"                    &lt;from&gt;&lt;![CDATA[, gangster g, organization o]]&gt;&lt;/from&gt;\n"
 "                    &lt;where&gt;&lt;![CDATA[\n"
 "                     (LCASE(g.name) = {0} OR LCASE(g.nick_name) = {0}) AND\n"
 "                     g.organization = o.name AND o.the_boss = boss.id\n"
@@ -4621,43 +3092,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1042
 #, no-c-format
-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 "
-"the end of the generated <literal>FROM</literal> clause. It is also possible "
-"for the <literal>FROM</literal> clause to start with a SQL <literal>JOIN</"
-"literal> statement. Since this is a select method, it must have a "
-"<literal>select</literal> element to declare the entity that will be "
-"selected. Note that an alias is also declared for the query. If an alias is "
-"not declared, the <literal>table-name</literal> is used as the alias, "
-"resulting in a <literal>SELECT</literal> clause with the <literal>table_name."
-"field_name</literal> style column declarations. Not all database vendors "
-"support the that syntax, so the declaration of an alias is preferred. The "
-"optional empty <literal>distinct</literal> element causes the "
-"<literal>SELECT</literal> clause to use the <literal>SELECT DISTINCT</"
-"literal> declaration. The DeclaredSQL declaration can also be used in select "
-"methods to select a CMP field."
-msgstr ""
-"请注意 <literal>FROM</literal> 子句由逗号开始。这是因为容器把声明的 "
-"<literal>FROM</literal> 子句附加在生成的 <literal>FROM</literal> 子句后面。"
-"<literal>FROM</literal> 子句也可能以 SQL <literal>JOIN</literal> 语句开始。既"
-"然这是一个 select 方法,它必须用 <literal>select</literal> 元素来声明要选择"
-"的 entity。请注意,查询也会声明一个别名。如果没有声明别名,<literal>table-"
-"name</literal> 将作为别名使用,这会生成带有 <literal>table_name.field_name</"
-"literal> 风格的列声明的 <literal>SELECT</literal> 子句。但不是所有的数据库厂"
-"商都支持这种语法,所以最好是声明别名。可选的空的 <literal>distinct</literal> "
-"元素使 <literal>SELECT</literal> 子句使用 <literal>SELECT DISTINCT</literal> "
-"声明。select 方法也可以用 DeclaredSQL 声明来查询 CMP 字段。 "
+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 the end of the generated <literal>FROM</literal> clause. It is also possible for the <literal>FROM</literal> clause to start with a SQL <literal>JOIN</literal> statement. Since this is a select method, it must have a <literal>select</literal> element to declare the entity that will be selected. Note that an alias is also declared for the query. If an alias is not declared, the <literal>table-name</literal> is used as the alias, resulting in a <literal>SELECT</literal> clause with the <literal>table_name.field_name</literal> style column declarations. Not all database vendors support the that syntax, so the declaration of an alias is preferred. The optional empty <literal>distinct</literal> element causes the <literal>SELECT</literal> clause to use the <literal>SELECT DISTINCT</literal> declaration. The DeclaredSQL de!
 claration can also be used in select methods to select a CMP field."
+msgstr "请注意 <literal>FROM</literal> 子句由逗号开始。这是因为容器把声明的 <literal>FROM</literal> 子句附加在生成的 <literal>FROM</literal> 子句后面。<literal>FROM</literal> 子句也可能以 SQL <literal>JOIN</literal> 语句开始。既然这是一个 select 方法,它必须用 <literal>select</literal> 元素来声明要选择的 entity。请注意,查询也会声明一个别名。如果没有声明别名,<literal>table-name</literal> 将作为别名使用,这会生成带有 <literal>table_name.field_name</literal> 风格的列声明的 <literal>SELECT</literal> 子句。但不是所有的数据库厂商都支持这种语法,所以最好是声明别名。可选的空的 <literal>distinct</literal> 元素使 <literal>SELECT</literal> 子句使用 <literal>SELECT DISTINCT</literal> 声明。select 方法也可以用 DeclaredSQL 声明来查询 CMP 字段。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1045
 #, no-c-format
-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。 "
+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。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1048
@@ -4669,21 +3111,12 @@
 "            &lt;ejb-name&gt;OrganizationEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;"
-"ejbSelectOperatingZipCodes_declaredsql&lt;/method-name&gt;\n"
+"                    &lt;method-name&gt;ejbSelectOperatingZipCodes_declaredsql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
-"                <emphasis role=\"bold\">&lt;declared-sql&gt; &lt;select&gt; "
-"&lt;distinct/&gt; &lt;ejb-name&gt;LocationEJB&lt;/ejb-name&gt; &lt;field-"
-"name&gt;zipCode&lt;/field-name&gt; &lt;alias&gt;hangout&lt;/alias&gt; &lt;/"
-"select&gt; &lt;from&gt;&lt;![CDATA[ , organization o, gangster g ]]&gt;&lt;/"
-"from&gt; &lt;where&gt;&lt;![CDATA[ LCASE(o.name) = {0} AND o.name = g."
-"organization AND g.hangout = hangout.id ]]&gt;&lt;/where&gt; &lt;order&gt;"
-"&lt;![CDATA[ hangout.zip ]]&gt;&lt;/order&gt; &lt;/declared-sql&gt;</"
-"emphasis>\n"
+"                <emphasis role=\"bold\">&lt;declared-sql&gt; &lt;select&gt; &lt;distinct/&gt; &lt;ejb-name&gt;LocationEJB&lt;/ejb-name&gt; &lt;field-name&gt;zipCode&lt;/field-name&gt; &lt;alias&gt;hangout&lt;/alias&gt; &lt;/select&gt; &lt;from&gt;&lt;![CDATA[ , organization o, gangster g ]]&gt;&lt;/from&gt; &lt;where&gt;&lt;![CDATA[ LCASE(o.name) = {0} AND o.name = g.organization AND g.hangout = hangout.id ]]&gt;&lt;/where&gt; &lt;order&gt;&lt;![CDATA[ hangout.zip ]]&gt;&lt;/order&gt; &lt;/declared-sql&gt;</emphasis>\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
 "    &lt;/enterprise-beans&gt;\n"
@@ -4695,21 +3128,12 @@
 "            &lt;ejb-name&gt;OrganizationEJB&lt;/ejb-name&gt;\n"
 "            &lt;query&gt;\n"
 "                &lt;query-method&gt;\n"
-"                    &lt;method-name&gt;"
-"ejbSelectOperatingZipCodes_declaredsql&lt;/method-name&gt;\n"
+"                    &lt;method-name&gt;ejbSelectOperatingZipCodes_declaredsql&lt;/method-name&gt;\n"
 "                    &lt;method-params&gt;\n"
-"                        &lt;method-param&gt;java.lang.String&lt;/method-"
-"param&gt;\n"
+"                        &lt;method-param&gt;java.lang.String&lt;/method-param&gt;\n"
 "                    &lt;/method-params&gt;\n"
 "                &lt;/query-method&gt;\n"
-"                <emphasis role=\"bold\">&lt;declared-sql&gt; &lt;select&gt; "
-"&lt;distinct/&gt; &lt;ejb-name&gt;LocationEJB&lt;/ejb-name&gt; &lt;field-"
-"name&gt;zipCode&lt;/field-name&gt; &lt;alias&gt;hangout&lt;/alias&gt; &lt;/"
-"select&gt; &lt;from&gt;&lt;![CDATA[ , organization o, gangster g ]]&gt;&lt;/"
-"from&gt; &lt;where&gt;&lt;![CDATA[ LCASE(o.name) = {0} AND o.name = g."
-"organization AND g.hangout = hangout.id ]]&gt;&lt;/where&gt; &lt;order&gt;"
-"&lt;![CDATA[ hangout.zip ]]&gt;&lt;/order&gt; &lt;/declared-sql&gt;</"
-"emphasis>\n"
+"                <emphasis role=\"bold\">&lt;declared-sql&gt; &lt;select&gt; &lt;distinct/&gt; &lt;ejb-name&gt;LocationEJB&lt;/ejb-name&gt; &lt;field-name&gt;zipCode&lt;/field-name&gt; &lt;alias&gt;hangout&lt;/alias&gt; &lt;/select&gt; &lt;from&gt;&lt;![CDATA[ , organization o, gangster g ]]&gt;&lt;/from&gt; &lt;where&gt;&lt;![CDATA[ LCASE(o.name) = {0} AND o.name = g.organization AND g.hangout = hangout.id ]]&gt;&lt;/where&gt; &lt;order&gt;&lt;![CDATA[ hangout.zip ]]&gt;&lt;/order&gt; &lt;/declared-sql&gt;</emphasis>\n"
 "            &lt;/query&gt;\n"
 "        &lt;/entity&gt;\n"
 "    &lt;/enterprise-beans&gt;\n"
@@ -4727,14 +3151,12 @@
 msgid ""
 "SELECT DISTINCT hangout.zip\n"
 "    FROM location hangout, organization o, gangster g\n"
-"    WHERE LCASE(o.name) = ? AND o.name = g.organization AND g.hangout = "
-"hangout.id\n"
+"    WHERE LCASE(o.name) = ? AND o.name = g.organization AND g.hangout = hangout.id\n"
 "                ORDER BY hangout.zip"
 msgstr ""
 "SELECT DISTINCT hangout.zip\n"
 "    FROM location hangout, organization o, gangster g\n"
-"    WHERE LCASE(o.name) = ? AND o.name = g.organization AND g.hangout = "
-"hangout.id\n"
+"    WHERE LCASE(o.name) = ? AND o.name = g.organization AND g.hangout = hangout.id\n"
 "                ORDER BY hangout.zip"
 
 #. Tag: title
@@ -4746,82 +3168,26 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1055
 #, no-c-format
-msgid ""
-"DeclaredSQL uses a completely new parameter handling system, which supports "
-"entity and DVC parameters. Parameters are enclosed in curly brackets and use "
-"a zero-based index, which is different from the one-based EJB-QL parameters. "
-"There are three categories of parameters: simple, DVC, and entity."
-msgstr ""
-"DeclaredSQL 使用一个全新的参数处理系统,它支持 entity 和 DVC 参数。参数括在花"
-"括号里且使用基于 0 的索引,这和基于 1 的 EJB-QL 的参数不同。它有 3 中参数类"
-"别:simple、DVC 和 entity。 "
+msgid "DeclaredSQL uses a completely new parameter handling system, which supports entity and DVC parameters. Parameters are enclosed in curly brackets and use a zero-based index, which is different from the one-based EJB-QL parameters. There are three categories of parameters: simple, DVC, and entity."
+msgstr "DeclaredSQL 使用一个全新的参数处理系统,它支持 entity 和 DVC 参数。参数括在花括号里且使用基于 0 的索引,这和基于 1 的 EJB-QL 的参数不同。它有 3 中参数类别:simple、DVC 和 entity。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1060
 #, no-c-format
-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 "
-"contains the argument number, such as <literal>{0}</literal>. When a simple "
-"parameter is set, the JDBC type used to set the parameter is determined by "
-"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 ""
-"<emphasis role=\"bold\">simple</emphasis>:simple 参数可以是任何类型,除了已"
-"知的(映射的)DVC 或 entity。simple 参数之包含参数序号,如 <literal>{0}</"
-"literal>。在设置了 simple 参数后,该 entity 的 <literal>datasourcemapping</"
-"literal> 决定用来设置这个参数的 JDBC 类型。未知的 DVC 会被序列化之后再设置为"
-"参数。请注意大多数数据库都不支持在 WHERE 子句里使用 BLOB 值。 "
+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 contains the argument number, such as <literal>{0}</literal>. When a simple parameter is set, the JDBC type used to set the parameter is determined by 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 "<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
 #, no-c-format
-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 "
-"(one that is not another DVC). For example, if we had a CVS property of type "
-"<literal>ContactInfo</literal>, valid parameter declarations would be "
-"<literal>{0.email}</literal> and <literal>{0.cell.areaCode}</literal> but "
-"not <literal>{0.cell}</literal>. The JDBC type used to set a parameter is "
-"based on the class type of the property and the <literal>datasourcemapping</"
-"literal> of the entity. The JDBC type used to set the parameter is the JDBC "
-"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 类型被用来设置这个参数。 "
+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 (one that is not another DVC). For example, if we had a CVS property of type <literal>ContactInfo</literal>, valid parameter declarations would be <literal>{0.email}</literal> and <literal>{0.cell.areaCode}</literal> but not <literal>{0.cell}</literal>. The JDBC type used to set a parameter is based on the class type of the property and the <literal>datasourcemapping</literal> of the entity. The JDBC type used to set the parameter is the JDBC 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
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">entity</emphasis>: An entity parameter can be any "
-"entity in the application. An entity parameter must be dereferenced down to "
-"a simple primary key field or simple property of a DVC primary key field. "
-"For example, if we had a parameter of type <literal>Gangster</literal>, a "
-"valid parameter declaration would be <literal>{0.gangsterId}</literal>. If "
-"we had some entity with a primary key field named info of type "
-"<literal>ContactInfo</literal>, a <literal>valid parameter</literal> "
-"declaration would be <literal>{0.info.cell.areaCode}</literal>. Only fields "
-"that are members of the primary key of the entity can be dereferenced (this "
-"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 ""
-"<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 类型被用来设置这个参数。 "
+msgid "<emphasis role=\"bold\">entity</emphasis>: An entity parameter can be any entity in the application. An entity parameter must be dereferenced down to a simple primary key field or simple property of a DVC primary key field. For example, if we had a parameter of type <literal>Gangster</literal>, a valid parameter declaration would be <literal>{0.gangsterId}</literal>. If we had some entity with a primary key field named info of type <literal>ContactInfo</literal>, a <literal>valid parameter</literal> declaration would be <literal>{0.info.cell.areaCode}</literal>. Only fields that are members of the primary key of the entity can be dereferenced (this 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 "<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
@@ -4832,15 +3198,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1081
 #, no-c-format
-msgid ""
-"The default query compiler doesn&#39;t fully support EJB-QL 2.1 or the SQL92 "
-"standard. If you need either of these functions, you can replace the query "
-"compiler. The default compiler is specified in <literal>standardjbosscmp-"
-"jdbc.xml</literal>."
-msgstr ""
-"缺省的查询编译器不完全支持 EJB-QL 2.1 或 SQL92 标准。如果你需要使用它们的函"
-"数,你可以替换查询编译器。你可以在 <literal>standardjbosscmp-jdbc.xml</"
-"literal> 里指定缺省的编译器。 "
+msgid "The default query compiler doesn&#39;t fully support EJB-QL 2.1 or the SQL92 standard. If you need either of these functions, you can replace the query compiler. The default compiler is specified in <literal>standardjbosscmp-jdbc.xml</literal>."
+msgstr "缺省的查询编译器不完全支持 EJB-QL 2.1 或 SQL92 标准。如果你需要使用它们的函数,你可以替换查询编译器。你可以在 <literal>standardjbosscmp-jdbc.xml</literal> 里指定缺省的编译器。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1084
@@ -4848,27 +3207,21 @@
 msgid ""
 "&lt;defaults&gt;\n"
 "    ...\n"
-"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler&lt;/"
-"ql-compiler&gt;\n"
+"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler&lt;/ql-compiler&gt;\n"
 "    ...\n"
 "&lt;/defaults&gt;"
 msgstr ""
 "&lt;defaults&gt;\n"
 "    ...\n"
-"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler&lt;/"
-"ql-compiler&gt;\n"
+"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler&lt;/ql-compiler&gt;\n"
 "    ...\n"
 "&lt;/defaults&gt;"
 
 #. Tag: para
 #: The_CMP_Engine.xml:1085
 #, no-c-format
-msgid ""
-"To use the SQL92 compiler, simply specify the SQL92 compiler in <literal>ql-"
-"compiler</literal> element."
-msgstr ""
-"要使用 SQL92 编译器,简单地在 <literal>ql-compiler</literal> 元素里指定 "
-"SQL92 编译器就可以了。 "
+msgid "To use the SQL92 compiler, simply specify the SQL92 compiler in <literal>ql-compiler</literal> element."
+msgstr "要使用 SQL92 编译器,简单地在 <literal>ql-compiler</literal> 元素里指定 SQL92 编译器就可以了。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1088
@@ -4876,29 +3229,21 @@
 msgid ""
 "&lt;defaults&gt;\n"
 "    ...\n"
-"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc."
-"EJBQLToSQL92Compiler&lt;/ql-compiler&gt;\n"
+"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.EJBQLToSQL92Compiler&lt;/ql-compiler&gt;\n"
 "    ...\n"
 "&lt;/defaults&gt;"
 msgstr ""
 "&lt;defaults&gt;\n"
 "    ...\n"
-"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc."
-"EJBQLToSQL92Compiler&lt;/ql-compiler&gt;\n"
+"    &lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.EJBQLToSQL92Compiler&lt;/ql-compiler&gt;\n"
 "    ...\n"
 "&lt;/defaults&gt;"
 
 #. Tag: para
 #: The_CMP_Engine.xml:1089
 #, no-c-format
-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</"
-"literal>. Here is an example using one of our earlier queries."
-msgstr ""
-"这会改变整个系统里的所有 bean 使用的查询编译器。你也可以在 <literal>jbosscmp-"
-"jdbc.xml</literal> 里为每个元素指定查询编译器。下面是使用其中一个早前的查询的"
-"例子。 "
+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</literal>. Here is an example using one of our earlier queries."
+msgstr "这会改变整个系统里的所有 bean 使用的查询编译器。你也可以在 <literal>jbosscmp-jdbc.xml</literal> 里为每个元素指定查询编译器。下面是使用其中一个早前的查询的例子。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1092
@@ -4916,8 +3261,7 @@
 "        FROM gangster g\n"
 "        WHERE g.badness &gt; ?1]]&gt;\n"
 "    &lt;/ejb-ql&gt;\n"
-"    <emphasis role=\"bold\">&lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp."
-"jdbc.EJBQLToSQL92Compiler&lt;/ql-compiler&gt;</emphasis>\n"
+"    <emphasis role=\"bold\">&lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.EJBQLToSQL92Compiler&lt;/ql-compiler&gt;</emphasis>\n"
 "&lt;/query&gt;"
 msgstr ""
 "&lt;query&gt;\n"
@@ -4932,31 +3276,14 @@
 "        FROM gangster g\n"
 "        WHERE g.badness &gt; ?1]]&gt;\n"
 "    &lt;/ejb-ql&gt;\n"
-"    <emphasis role=\"bold\">&lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp."
-"jdbc.EJBQLToSQL92Compiler&lt;/ql-compiler&gt;</emphasis>\n"
+"    <emphasis role=\"bold\">&lt;ql-compiler&gt;org.jboss.ejb.plugins.cmp.jdbc.EJBQLToSQL92Compiler&lt;/ql-compiler&gt;</emphasis>\n"
 "&lt;/query&gt;"
 
 #. Tag: para
 #: The_CMP_Engine.xml:1093
 #, no-c-format
-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> "
-"strategy in use. For example, if a query is configured with the <literal>on-"
-"load</literal><literal>read-ahead</literal> strategy, the first query will "
-"include all the fields, not just primary key fields but only the primary key "
-"fields will be read from the <literal>ResultSet</literal>. Then, on load, "
-"other fields will be actually loaded into the read-ahead cache. The "
-"<literal>on-find</literal><literal>read-ahead</literal> with the default "
-"load group <literal>*</literal> works as expected."
-msgstr ""
-"SQL92 查询编译器的一个重要限制是它总是选择 entity 所有的字段而不管是否使用了 "
-"<literal>read-ahead</literal> 策略。例如,如果查询使用了 <literal>on-load</"
-"literal><literal>read-ahead</literal> 策略,第一个查询将包括所有的字段而不仅"
-"仅是主键字段,但只有主键字段会从 <literal>ResultSet</literal> 里读取。然后其"
-"他字段也实际上将被载入 read-ahead 缓存。运行带有缺省的 load group 的 "
-"<literal>on-find</literal><literal>read-ahead</literal> 则和我们所预期的相"
-"同。 "
+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> strategy in use. For example, if a query is configured with the <literal>on-load</literal><literal>read-ahead</literal> strategy, the first query will include all the fields, not just primary key fields but only the primary key fields will be read from the <literal>ResultSet</literal>. Then, on load, other fields will be actually loaded into the read-ahead cache. The <literal>on-find</literal><literal>read-ahead</literal> with the default load group <literal>*</literal> works as expected."
+msgstr "SQL92 查询编译器的一个重要限制是它总是选择 entity 所有的字段而不管是否使用了 <literal>read-ahead</literal> 策略。例如,如果查询使用了 <literal>on-load</literal><literal>read-ahead</literal> 策略,第一个查询将包括所有的字段而不仅仅是主键字段,但只有主键字段会从 <literal>ResultSet</literal> 里读取。然后其他字段也实际上将被载入 read-ahead 缓存。运行带有缺省的 load group 的 <literal>on-find</literal><literal>read-ahead</literal> 则和我们所预期的相同。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1099
@@ -4967,18 +3294,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1100
 #, no-c-format
-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, "
-"JBoss will always call the custom finder over any other implementation "
-"declared in the <literal>ejb-jar.xml</literal> or <literal>jbosscmp-jdbc."
-"xml</literal> files. The following simple example finds the entities by a "
-"collection of primary keys:"
-msgstr ""
-"JBoss 也支持 bean 管理的持久性自定义 finder。如果自定义的 finder 方法和 home "
-"或 local home 接口里声明的 finder 相符,JBoss 将总是先于 <literal>ejb-jar."
-"xml</literal> 或 <literal>jbosscmp-jdbc.xml</literal> 里声明的其他实现调用自"
-"定义的 finder。下面的简单示例根据主键集合来查找 entity: "
+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, JBoss will always call the custom finder over any other implementation declared in the <literal>ejb-jar.xml</literal> or <literal>jbosscmp-jdbc.xml</literal> files. The following simple example finds the entities by a collection of primary keys:"
+msgstr "JBoss 也支持 bean 管理的持久性自定义 finder。如果自定义的 finder 方法和 home 或 local home 接口里声明的 finder 相符,JBoss 将总是先于 <literal>ejb-jar.xml</literal> 或 <literal>jbosscmp-jdbc.xml</literal> 里声明的其他实现调用自定义的 finder。下面的简单示例根据主键集合来查找 entity: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1103
@@ -5005,22 +3322,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1104
 #, no-c-format
-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 "
-"can create an Entity object with a primary key that does not exist in the "
-"database. If any method is invoked on the bad Entity, a "
-"NoSuchEntityException will be thrown. Another drawback is that the resulting "
-"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 ""
-"这是一个非常有用的 finder,因为它可以快速地把主键转换成实际的Eentity 对象而不"
-"需要连接数据库。它一个缺点是创建了一个带有不存在于数据库里的主键的 Entity 对"
-"象。如果在这个“坏”的 Entity 上调用了任何方法,NoSuchEntityException 将被抛"
-"出。它的另外一个缺点是结果 entity bean 违背了 EJB 规格,因为它实现了一个 "
-"finder,除非把 StrictVerifier 属性设为 false,否则 JBoss EJB verifier 在部署"
-"它时就会失败。 "
+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 can create an Entity object with a primary key that does not exist in the database. If any method is invoked on the bad Entity, a NoSuchEntityException will be thrown. Another drawback is that the resulting 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 "这是一个非常有用的 finder,因为它可以快速地把主键转换成实际的Eentity 对象而不需要连接数据库。它一个缺点是创建了一个带有不存在于数据库里的主键的 Entity 对象。如果在这个“坏”的 Entity 上调用了任何方法,NoSuchEntityException 将被抛出。它的另外一个缺点是结果 entity bean 违背了 EJB 规格,因为它实现了一个 finder,除非把 StrictVerifier 属性设为 false,否则 JBoss EJB verifier 在部署它时就会失败。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1112
@@ -5031,19 +3334,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1113
 #, no-c-format
-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 "
-"tuning of JBoss depends on a detailed knowledge of the loading process. This "
-"section describes the internals of the JBoss loading process and its "
-"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 ""
-"优化加载的目的是使用最少的查询次数、加载最少的数据来完成事务。JBoss 的调整需"
-"要对加载过程有着详细了解。本节描述了 JBoss 加载过程的内部细节及其配置。对加载"
-"过程的调整确实需要完整地理解加载系统,所以你可能需要对本节内容进行多次反复阅"
-"读。 "
+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 tuning of JBoss depends on a detailed knowledge of the loading process. This section describes the internals of the JBoss loading process and its 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 "优化加载的目的是使用最少的查询次数、加载最少的数据来完成事务。JBoss 的调整需要对加载过程有着详细了解。本节描述了 JBoss 加载过程的内部细节及其配置。对加载过程的调整确实需要完整地理解加载系统,所以你可能需要对本节内容进行多次反复阅读。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1117
@@ -5054,14 +3346,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1118
 #, no-c-format
-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 "
-"iterate over the results performing some operation. The following example "
-"generates an html table containing all of the gangsters:"
-msgstr ""
-"了解加载过程的最容易的方法就是查看其使用模式。最常用的模式是选定一个 entity "
-"集合并重复某个操作。下面的例子生成了一个包含所有 gangster 的 HTML 表格: "
+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 iterate over the results performing some operation. The following example generates an html table containing all of the gangsters:"
+msgstr "了解加载过程的最容易的方法就是查看其使用模式。最常用的模式是选定一个 entity 集合并重复某个操作。下面的例子生成了一个包含所有 gangster 的 HTML 表格: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1121
@@ -5114,13 +3400,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1122
 #, no-c-format
-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 将执行下面的查询: "
+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 将执行下面的查询: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1125
@@ -5137,9 +3418,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1126
 #, no-c-format
-msgid ""
-"Then as each of the eight gangster in the sample database is accessed, JBoss "
-"will execute the following eight queries:"
+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 个查询: "
 
 #. Tag: programlisting
@@ -5183,40 +3462,18 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1130
 #, no-c-format
-msgid ""
-"There are two problems with this scenario. First, an excessive number of "
-"queries are executed because JBoss executes one query for the "
-"<literal>findAll</literal> and one query to access each element found. The "
-"reason for this behavior has to do with the handling of query results inside "
-"the JBoss container. Although it appears that the actual entity beans "
-"selected are returned when a query is executed, JBoss really only returns "
-"the primary keys of the matching entities, and does not load the entity "
-"until a method is invoked on it. This is known as the <emphasis>n+1</"
-"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 策略则可以解决这个问题。 "
+msgid "There are two problems with this scenario. First, an excessive number of queries are executed because JBoss executes one query for the <literal>findAll</literal> and one query to access each element found. The reason for this behavior has to do with the handling of query results inside the JBoss container. Although it appears that the actual entity beans selected are returned when a query is executed, JBoss really only returns the primary keys of the matching entities, and does not load the entity until a method is invoked on it. This is known as the <emphasis>n+1</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
 #, no-c-format
-msgid ""
-"Second, the values of unused fields are loaded needlessly. JBoss loads the "
-"<literal>hangout</literal> and <literal>organization</literal> fields, which "
-"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> 字段) "
+msgid "Second, the values of unused fields are loaded needlessly. JBoss loads the <literal>hangout</literal> and <literal>organization</literal> fields, which 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
+#: The_CMP_Engine.xml:1136
+#: The_CMP_Engine.xml:2018
 #, no-c-format
 msgid "The following table shows the execution of the queries:"
 msgstr "下面的表展示了这些查询的执行情况: "
@@ -5228,270 +3485,396 @@
 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
+#: 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
 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:1147
+#: The_CMP_Engine.xml:1363
+#: The_CMP_Engine.xml:1681
 #: The_CMP_Engine.xml:2038
 #, no-c-format
 msgid "name"
 msgstr "名字 "
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1150 The_CMP_Engine.xml:1366 The_CMP_Engine.xml:1684
+#: The_CMP_Engine.xml:1150
+#: The_CMP_Engine.xml:1366
+#: The_CMP_Engine.xml:1684
 #: The_CMP_Engine.xml:2041
 #, no-c-format
 msgid "nick_name"
 msgstr "nick_name"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1153 The_CMP_Engine.xml:1369 The_CMP_Engine.xml:1687
+#: The_CMP_Engine.xml:1153
+#: The_CMP_Engine.xml:1369
+#: The_CMP_Engine.xml:1687
 #: The_CMP_Engine.xml:2044
 #, no-c-format
 msgid "badness"
 msgstr "badness"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1156 The_CMP_Engine.xml:1372 The_CMP_Engine.xml:1690
+#: The_CMP_Engine.xml:1156
+#: The_CMP_Engine.xml:1372
+#: The_CMP_Engine.xml:1690
 #: The_CMP_Engine.xml:2047
 #, no-c-format
 msgid "hangout"
 msgstr "hangout"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1159 The_CMP_Engine.xml:1375 The_CMP_Engine.xml:1693
+#: The_CMP_Engine.xml:1159
+#: The_CMP_Engine.xml:1375
+#: The_CMP_Engine.xml:1693
 #, no-c-format
 msgid "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
+#: 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
 msgid "<entry>0</entry>"
 msgstr "<entry>0</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1169 The_CMP_Engine.xml:1385 The_CMP_Engine.xml:1703
+#: The_CMP_Engine.xml:1169
+#: The_CMP_Engine.xml:1385
+#: The_CMP_Engine.xml:1703
 #: The_CMP_Engine.xml:2069
 #, no-c-format
 msgid "Yojimbo"
 msgstr "Yojimbo"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1172 The_CMP_Engine.xml:1388 The_CMP_Engine.xml:1706
+#: The_CMP_Engine.xml:1172
+#: The_CMP_Engine.xml:1388
+#: The_CMP_Engine.xml:1706
 #: The_CMP_Engine.xml:2072
 #, no-c-format
 msgid "Bodyguard"
 msgstr "Bodyguard"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1175 The_CMP_Engine.xml:1306 The_CMP_Engine.xml:1318
-#: The_CMP_Engine.xml:1391 The_CMP_Engine.xml:1522 The_CMP_Engine.xml:1534
-#: The_CMP_Engine.xml:1709 The_CMP_Engine.xml:1840 The_CMP_Engine.xml:1852
-#: The_CMP_Engine.xml:2075 The_CMP_Engine.xml:2269 The_CMP_Engine.xml:2281
+#: The_CMP_Engine.xml:1175
+#: The_CMP_Engine.xml:1306
+#: The_CMP_Engine.xml:1318
+#: The_CMP_Engine.xml:1391
+#: The_CMP_Engine.xml:1522
+#: The_CMP_Engine.xml:1534
+#: The_CMP_Engine.xml:1709
+#: The_CMP_Engine.xml:1840
+#: The_CMP_Engine.xml:1852
+#: The_CMP_Engine.xml:2075
+#: The_CMP_Engine.xml:2269
+#: The_CMP_Engine.xml:2281
 #: The_CMP_Engine.xml:2284
 #, no-c-format
 msgid "<entry>7</entry>"
 msgstr "<entry>7</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1181 The_CMP_Engine.xml:1201 The_CMP_Engine.xml:1221
-#: 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
+#: The_CMP_Engine.xml:1181
+#: The_CMP_Engine.xml:1201
+#: The_CMP_Engine.xml:1221
+#: 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
 msgid "Yakuza"
 msgstr "Yakuza"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1186 The_CMP_Engine.xml:1198 The_CMP_Engine.xml:1402
-#: 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
+#: The_CMP_Engine.xml:1186
+#: The_CMP_Engine.xml:1198
+#: The_CMP_Engine.xml:1402
+#: 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
 msgid "<entry>1</entry>"
 msgstr "<entry>1</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1189 The_CMP_Engine.xml:1405 The_CMP_Engine.xml:1723
+#: The_CMP_Engine.xml:1189
+#: The_CMP_Engine.xml:1405
+#: The_CMP_Engine.xml:1723
 #: The_CMP_Engine.xml:2098
 #, no-c-format
 msgid "Takeshi"
 msgstr "Takeshi"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1192 The_CMP_Engine.xml:1408 The_CMP_Engine.xml:1726
+#: The_CMP_Engine.xml:1192
+#: The_CMP_Engine.xml:1408
+#: The_CMP_Engine.xml:1726
 #: The_CMP_Engine.xml:2101
 #, no-c-format
 msgid "Master"
 msgstr "Master"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1195 The_CMP_Engine.xml:1411 The_CMP_Engine.xml:1729
+#: The_CMP_Engine.xml:1195
+#: The_CMP_Engine.xml:1411
+#: The_CMP_Engine.xml:1729
 #: The_CMP_Engine.xml:2104
 #, no-c-format
 msgid "<entry>10</entry>"
 msgstr "<entry>10</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1206 The_CMP_Engine.xml:1218 The_CMP_Engine.xml:1295
-#: The_CMP_Engine.xml:1422 The_CMP_Engine.xml:1434 The_CMP_Engine.xml:1511
-#: The_CMP_Engine.xml:1740 The_CMP_Engine.xml:1752 The_CMP_Engine.xml:1829
-#: The_CMP_Engine.xml:2124 The_CMP_Engine.xml:2136 The_CMP_Engine.xml:2139
+#: The_CMP_Engine.xml:1206
+#: The_CMP_Engine.xml:1218
+#: The_CMP_Engine.xml:1295
+#: The_CMP_Engine.xml:1422
+#: The_CMP_Engine.xml:1434
+#: The_CMP_Engine.xml:1511
+#: The_CMP_Engine.xml:1740
+#: The_CMP_Engine.xml:1752
+#: The_CMP_Engine.xml:1829
+#: The_CMP_Engine.xml:2124
+#: The_CMP_Engine.xml:2136
+#: The_CMP_Engine.xml:2139
 #: The_CMP_Engine.xml:2249
 #, no-c-format
 msgid "<entry>2</entry>"
 msgstr "<entry>2</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1209 The_CMP_Engine.xml:1425 The_CMP_Engine.xml:1743
+#: The_CMP_Engine.xml:1209
+#: The_CMP_Engine.xml:1425
+#: The_CMP_Engine.xml:1743
 #: The_CMP_Engine.xml:2127
 #, no-c-format
 msgid "Yuriko"
 msgstr "Yuriko"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1212 The_CMP_Engine.xml:1428 The_CMP_Engine.xml:1746
+#: The_CMP_Engine.xml:1212
+#: The_CMP_Engine.xml:1428
+#: The_CMP_Engine.xml:1746
 #: The_CMP_Engine.xml:2130
 #, no-c-format
 msgid "Four finger"
 msgstr "Four finger"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1215 The_CMP_Engine.xml:1246 The_CMP_Engine.xml:1258
-#: The_CMP_Engine.xml:1275 The_CMP_Engine.xml:1431 The_CMP_Engine.xml:1462
-#: The_CMP_Engine.xml:1474 The_CMP_Engine.xml:1491 The_CMP_Engine.xml:1749
-#: The_CMP_Engine.xml:1780 The_CMP_Engine.xml:1792 The_CMP_Engine.xml:1809
-#: 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
+#: The_CMP_Engine.xml:1215
+#: The_CMP_Engine.xml:1246
+#: The_CMP_Engine.xml:1258
+#: The_CMP_Engine.xml:1275
+#: The_CMP_Engine.xml:1431
+#: The_CMP_Engine.xml:1462
+#: The_CMP_Engine.xml:1474
+#: The_CMP_Engine.xml:1491
+#: The_CMP_Engine.xml:1749
+#: The_CMP_Engine.xml:1780
+#: The_CMP_Engine.xml:1792
+#: The_CMP_Engine.xml:1809
+#: 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
 msgid "<entry>4</entry>"
 msgstr "<entry>4</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1226 The_CMP_Engine.xml:1238 The_CMP_Engine.xml:1442
-#: 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
+#: The_CMP_Engine.xml:1226
+#: The_CMP_Engine.xml:1238
+#: The_CMP_Engine.xml:1442
+#: 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
 msgid "<entry>3</entry>"
 msgstr "<entry>3</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1229 The_CMP_Engine.xml:1445 The_CMP_Engine.xml:1763
+#: The_CMP_Engine.xml:1229
+#: The_CMP_Engine.xml:1445
+#: The_CMP_Engine.xml:1763
 #: The_CMP_Engine.xml:2156
 #, no-c-format
 msgid "Chow"
 msgstr "Chow"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1232 The_CMP_Engine.xml:1448 The_CMP_Engine.xml:1766
+#: The_CMP_Engine.xml:1232
+#: The_CMP_Engine.xml:1448
+#: The_CMP_Engine.xml:1766
 #: The_CMP_Engine.xml:2159
 #, no-c-format
 msgid "Killer"
 msgstr "Killer"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1235 The_CMP_Engine.xml:1451 The_CMP_Engine.xml:1769
+#: The_CMP_Engine.xml:1235
+#: The_CMP_Engine.xml:1451
+#: The_CMP_Engine.xml:1769
 #: The_CMP_Engine.xml:2162
 #, no-c-format
 msgid "<entry>9</entry>"
 msgstr "<entry>9</entry>"
 
 #. Tag: entry
-#: 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
+#: 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
 msgid "Triads"
 msgstr "Triads"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1249 The_CMP_Engine.xml:1465 The_CMP_Engine.xml:1783
+#: The_CMP_Engine.xml:1249
+#: The_CMP_Engine.xml:1465
+#: The_CMP_Engine.xml:1783
 #: The_CMP_Engine.xml:2185
 #, no-c-format
 msgid "Shogi"
 msgstr "Shogi"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1252 The_CMP_Engine.xml:1468 The_CMP_Engine.xml:1786
+#: The_CMP_Engine.xml:1252
+#: The_CMP_Engine.xml:1468
+#: The_CMP_Engine.xml:1786
 #: The_CMP_Engine.xml:2188
 #, no-c-format
 msgid "Lightning"
 msgstr "Lightning"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1255 The_CMP_Engine.xml:1471 The_CMP_Engine.xml:1789
+#: The_CMP_Engine.xml:1255
+#: The_CMP_Engine.xml:1471
+#: The_CMP_Engine.xml:1789
 #: The_CMP_Engine.xml:2191
 #, no-c-format
 msgid "<entry>8</entry>"
 msgstr "<entry>8</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1266 The_CMP_Engine.xml:1278 The_CMP_Engine.xml:1482
-#: 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
+#: The_CMP_Engine.xml:1266
+#: The_CMP_Engine.xml:1278
+#: The_CMP_Engine.xml:1482
+#: 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
 msgid "<entry>5</entry>"
 msgstr "<entry>5</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1269 The_CMP_Engine.xml:1485 The_CMP_Engine.xml:1803
+#: The_CMP_Engine.xml:1269
+#: The_CMP_Engine.xml:1485
+#: The_CMP_Engine.xml:1803
 #: The_CMP_Engine.xml:2214
 #, no-c-format
 msgid "Valentino"
 msgstr "Valentino"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1272 The_CMP_Engine.xml:1488 The_CMP_Engine.xml:1806
+#: The_CMP_Engine.xml:1272
+#: The_CMP_Engine.xml:1488
+#: The_CMP_Engine.xml:1806
 #: The_CMP_Engine.xml:2217
 #, no-c-format
 msgid "Pizza-Face"
 msgstr "Pizza-Face"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1281 The_CMP_Engine.xml:1301 The_CMP_Engine.xml:1321
-#: 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
+#: The_CMP_Engine.xml:1281
+#: The_CMP_Engine.xml:1301
+#: The_CMP_Engine.xml:1321
+#: 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
 msgid "Mafia"
 msgstr "Mafia"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1286 The_CMP_Engine.xml:1298 The_CMP_Engine.xml:1315
-#: The_CMP_Engine.xml:1502 The_CMP_Engine.xml:1514 The_CMP_Engine.xml:1531
-#: The_CMP_Engine.xml:1820 The_CMP_Engine.xml:1832 The_CMP_Engine.xml:1849
-#: The_CMP_Engine.xml:2240 The_CMP_Engine.xml:2252 The_CMP_Engine.xml:2255
+#: The_CMP_Engine.xml:1286
+#: The_CMP_Engine.xml:1298
+#: The_CMP_Engine.xml:1315
+#: The_CMP_Engine.xml:1502
+#: The_CMP_Engine.xml:1514
+#: The_CMP_Engine.xml:1531
+#: The_CMP_Engine.xml:1820
+#: The_CMP_Engine.xml:1832
+#: The_CMP_Engine.xml:1849
+#: The_CMP_Engine.xml:2240
+#: The_CMP_Engine.xml:2252
+#: The_CMP_Engine.xml:2255
 #: The_CMP_Engine.xml:2278
 #, no-c-format
 msgid "<entry>6</entry>"
 msgstr "<entry>6</entry>"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1289 The_CMP_Engine.xml:1505 The_CMP_Engine.xml:1823
+#: The_CMP_Engine.xml:1289
+#: The_CMP_Engine.xml:1505
+#: The_CMP_Engine.xml:1823
 #: The_CMP_Engine.xml:2243
 #, no-c-format
 msgid "Toni"
 msgstr "Toni"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1292 The_CMP_Engine.xml:1508 The_CMP_Engine.xml:1826
+#: The_CMP_Engine.xml:1292
+#: The_CMP_Engine.xml:1508
+#: The_CMP_Engine.xml:1826
 #: The_CMP_Engine.xml:2246
 #, no-c-format
 msgid "Toothless"
 msgstr "Toothless"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1309 The_CMP_Engine.xml:1525 The_CMP_Engine.xml:1843
+#: The_CMP_Engine.xml:1309
+#: The_CMP_Engine.xml:1525
+#: The_CMP_Engine.xml:1843
 #: The_CMP_Engine.xml:2272
 #, no-c-format
 msgid "Corleone"
 msgstr "Corleone"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:1312 The_CMP_Engine.xml:1528 The_CMP_Engine.xml:1846
+#: The_CMP_Engine.xml:1312
+#: The_CMP_Engine.xml:1528
+#: The_CMP_Engine.xml:1846
 #: The_CMP_Engine.xml:2275
 #, no-c-format
 msgid "Godfather"
@@ -5506,17 +3889,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1332
 #, no-c-format
-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 "
-"names of CMP fields and CMR Fields that have a foreign key (e.g., "
-"<literal>Gangster</literal> in the Organization-Gangster example) that will "
-"be loaded in a single operation. An example configuration is shown below:"
-msgstr ""
-"对加载系统的配置和优化从 entity 里命名的加载组(load group)声明开始。加载组"
-"包含具有外键并将在单一操作里加载的 CMP 字段和 CMR 字段的名字(如 "
-"Organization-Gangster 示例里的 <literal>Gangster</literal>)。下面是一个配置"
-"示例: "
+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 names of CMP fields and CMR Fields that have a foreign key (e.g., <literal>Gangster</literal> in the Organization-Gangster example) that will be loaded in a single operation. An example configuration is shown below:"
+msgstr "对加载系统的配置和优化从 entity 里命名的加载组(load group)声明开始。加载组包含具有外键并将在单一操作里加载的 CMP 字段和 CMR 字段的名字(如 Organization-Gangster 示例里的 <literal>Gangster</literal>)。下面是一个配置示例: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1335
@@ -5535,8 +3909,7 @@
 "                    &lt;field-name&gt;badness&lt;/field-name&gt;\n"
 "                &lt;/load-group&gt;\n"
 "                &lt;load-group&gt;\n"
-"                    &lt;load-group-name&gt;contact info&lt;/load-group-"
-"name&gt;\n"
+"                    &lt;load-group-name&gt;contact info&lt;/load-group-name&gt;\n"
 "                    &lt;field-name&gt;nickName&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;contactInfo&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;hangout&lt;/field-name&gt;\n"
@@ -5559,8 +3932,7 @@
 "                    &lt;field-name&gt;badness&lt;/field-name&gt;\n"
 "                &lt;/load-group&gt;\n"
 "                &lt;load-group&gt;\n"
-"                    &lt;load-group-name&gt;contact info&lt;/load-group-"
-"name&gt;\n"
+"                    &lt;load-group-name&gt;contact info&lt;/load-group-name&gt;\n"
 "                    &lt;field-name&gt;nickName&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;contactInfo&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;hangout&lt;/field-name&gt;\n"
@@ -5573,19 +3945,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1336
 #, no-c-format
-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 "
-"mutually exclusive. For example, both of the load groups contain the "
-"<literal>nickName</literal> field. In addition to the declared load groups, "
-"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 字段。 "
+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 mutually exclusive. For example, both of the load groups contain the <literal>nickName</literal> field. In addition to the declared load groups, 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
@@ -5596,25 +3957,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1343
 #, no-c-format
-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 "
-"several rows; hence the term read-ahead. JBoss implements two main "
-"strategies (<literal>on-find</literal> and <literal>on-load</literal>) to "
-"optimize the loading problem identified in the previous section. The extra "
-"data loaded during read-ahead is not immediately associated with an entity "
-"object in memory, as entities are not materialized in JBoss until actually "
-"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 ""
-"JBoss 里的优化加载被称为预读(read-ahead)。这指的是在读取被加载的 entity 的"
-"某一行时,同时还读取下面的几行,所以被称为预读(read-ahead)。JBoss 实现两个"
-"主要的策略(<literal>on-find</literal> 和 <literal>on-load</literal>)来优化"
-"前面章节所提及的加载问题。在预读期间加载的额外数据不会马上和内存里的 entity "
-"对象相关联,因为 JBoss 里的 entity 知道实际被访问时才会实例化。相反,它会存储"
-"在预加载的缓存里,而知道事务结束时才会载入到 entity 里。下面的章节描述了预读"
-"策略。 "
+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 several rows; hence the term read-ahead. JBoss implements two main strategies (<literal>on-find</literal> and <literal>on-load</literal>) to optimize the loading problem identified in the previous section. The extra data loaded during read-ahead is not immediately associated with an entity object in memory, as entities are not materialized in JBoss until actually 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 "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
@@ -5625,13 +3969,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1348
 #, no-c-format
-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 将执行下面的查询。 "
+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 将执行下面的查询。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1351
@@ -5648,16 +3987,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1352
 #, no-c-format
-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. "
-"This strategy is effective for queries that return a small amount of data, "
-"but it becomes very inefficient when trying to load a large result set into "
-"memory. The following table shows the execution of this query:"
-msgstr ""
-"所有需要的数据都存放在预加载的缓存里,所以在迭代查询结果时不需要执行额外的查"
-"询。这种策略对于返回少量数据的查询来说时有效的,但是如果把大量的查询结果放入"
-"内存就非常低效了。下面的表展示了这个查询的执行: "
+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. This strategy is effective for queries that return a small amount of data, but it becomes very inefficient when trying to load a large result set into memory. The following table shows the execution of this query:"
+msgstr "所有需要的数据都存放在预加载的缓存里,所以在迭代查询结果时不需要执行额外的查询。这种策略对于返回少量数据的查询来说时有效的,但是如果把大量的查询结果放入内存就非常低效了。下面的表展示了这个查询的执行: "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1356
@@ -5668,19 +3999,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1544
 #, no-c-format
-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 "
-"<literal>read-ahead</literal> strategy is not declared in the "
-"<literal>query</literal> element, the strategy declared in the "
-"<literal>entity</literal> element or <literal>defaults</literal> element is "
-"used. The <literal>on-find</literal> configuration follows:"
-msgstr ""
-"<literal>read-ahead</literal> 策略和查询的 <literal>load-group</literal> 在 "
-"<literal>query</literal> 元素里进行定义。如果 <literal>read-ahead</literal> "
-"策略不在 <literal>query</literal> 里声明,<literal>entity</literal> 元素或 "
-"<literal>defaults</literal> 元素里声明的策略将被使用。下面是 <literal>on-"
-"find</literal> 的配置: "
+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 <literal>read-ahead</literal> strategy is not declared in the <literal>query</literal> element, the strategy declared in the <literal>entity</literal> element or <literal>defaults</literal> element is used. The <literal>on-find</literal> configuration follows:"
+msgstr "<literal>read-ahead</literal> 策略和查询的 <literal>load-group</literal> 在 <literal>query</literal> 元素里进行定义。如果 <literal>read-ahead</literal> 策略不在 <literal>query</literal> 里声明,<literal>entity</literal> 元素或 <literal>defaults</literal> 元素里声明的策略将被使用。下面是 <literal>on-find</literal> 的配置: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1547
@@ -5739,19 +4059,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1548
 #, no-c-format
-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 "
-"only a fixed number of results are rendered on a page. Since the preloaded "
-"data is only valid for the length of the transaction, and a transaction is "
-"limited to a single web HTTP hit, most of the preloaded data is not used. "
-"The <literal>on-load</literal> strategy discussed in the next section does "
-"not suffer from this problem."
-msgstr ""
-"<literal>on-find</literal> 策略存在的一个问题时它必须为每个选择的 entity 载入"
-"额外的数据。在 web 程序里,页面上通常会显示固定数量的结果。既然预加载的数据只"
-"在事务期间有效,而事务仅仅限于单个的 web HTTP 会话,那么大多数的预加载数据都"
-"不会被用到。下节讨论的 <literal>on-load</literal> 策略就不会有这个问题。 "
+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 only a fixed number of results are rendered on a page. Since the preloaded data is only valid for the length of the transaction, and a transaction is limited to a single web HTTP hit, most of the preloaded data is not used. The <literal>on-load</literal> strategy discussed in the next section does not suffer from this problem."
+msgstr "<literal>on-find</literal> 策略存在的一个问题时它必须为每个选择的 entity 载入额外的数据。在 web 程序里,页面上通常会显示固定数量的结果。既然预加载的数据只在事务期间有效,而事务仅仅限于单个的 web HTTP 会话,那么大多数的预加载数据都不会被用到。下节讨论的 <literal>on-load</literal> 策略就不会有这个问题。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1552
@@ -5762,23 +4071,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1553
 #, no-c-format
-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 "
-"fields from the base instance but also related instances which can be "
-"reached from the base instance by CMR navigation. There are no limitation "
-"for the depth of CMR navigations. There are also no limitations for "
-"cardinality of CMR fields used in navigation and relationship type mapping, "
-"i.e. both foreign key and relation-table mapping styles are supported. "
-"Let&#39;s look at some examples. Entity and relationship declarations can be "
-"found below."
-msgstr ""
-"Left join read ahead 是一个加强的 <literal>on-find</literal><literal>read-"
-"ahead</literal> 策略。它允许你预加载 SQL 查询,不仅包括基础实例的字段,也包括"
-"可以通过 CMR 导航从基础实例引用的相关实例。CMR 导航的深度没有限制。在导航和关"
-"系类型映射里使用的 CMR 字段的表间关系(cardinality)也没有限制,也就是说,外"
-"键和关系表映射风格都被支持。让我们来看看一些例子。下面是 Entity 和关系的声"
-"明。 "
+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 fields from the base instance but also related instances which can be reached from the base instance by CMR navigation. There are no limitation for the depth of CMR navigations. There are also no limitations for cardinality of CMR fields used in navigation and relationship type mapping, i.e. both foreign key and relation-table mapping styles are supported. Let&#39;s look at some examples. Entity and relationship declarations can be found below."
+msgstr "Left join read ahead 是一个加强的 <literal>on-find</literal><literal>read-ahead</literal> 策略。它允许你预加载 SQL 查询,不仅包括基础实例的字段,也包括可以通过 CMR 导航从基础实例引用的相关实例。CMR 导航的深度没有限制。在导航和关系类型映射里使用的 CMR 字段的表间关系(cardinality)也没有限制,也就是说,外键和关系表映射风格都被支持。让我们来看看一些例子。下面是 Entity 和关系的声明。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1559
@@ -5789,12 +4083,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1560
 #, no-c-format
-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 查询将类似于: "
+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 查询将类似于: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1563
@@ -5805,13 +4095,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1564
 #, no-c-format
-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>。 "
+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>。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1567
@@ -5824,8 +4109,7 @@
 "            &lt;method-param&gt;java.lang.Long&lt;/method-param&gt;\n"
 "        &lt;/method-params&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM D AS o WHERE o.id = ?"
-"1]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM D AS o WHERE o.id = ?1]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
@@ -5842,8 +4126,7 @@
 "            &lt;method-param&gt;java.lang.Long&lt;/method-param&gt;\n"
 "        &lt;/method-params&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM D AS o WHERE o.id = ?"
-"1]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM D AS o WHERE o.id = ?1]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
@@ -5856,9 +4139,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1568
 #, no-c-format
-msgid ""
-"The <literal>left-join</literal> declares the relations to be eager loaded. "
-"The generated SQL would look like this:"
+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 将类似于: "
 
 #. Tag: programlisting
@@ -5884,14 +4165,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1572
 #, no-c-format
-msgid ""
-"For the <literal>D</literal> with the specific id we preload all its related "
-"<literal>B</literal>&#39;s and <literal>C</literal>&#39;s and can access "
-"those instance loading them from the read ahead cache, not from the database."
-msgstr ""
-"对于带有特定 ID 的 <literal>D</literal>,我们预加载所有相关的 <literal>B</"
-"literal> 和 <literal>C</literal>,然后我们可以访问那些从预读缓存而不是数据库"
-"里加载的实例。 "
+msgid "For the <literal>D</literal> with the specific id we preload all its related <literal>B</literal>&#39;s and <literal>C</literal>&#39;s and can access those instance loading them from the read ahead cache, not from the database."
+msgstr "对于带有特定 ID 的 <literal>D</literal>,我们预加载所有相关的 <literal>B</literal> 和 <literal>C</literal>,然后我们可以访问那些从预读缓存而不是数据库里加载的实例。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1578
@@ -5902,13 +4177,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1579
 #, no-c-format
-msgid ""
-"In the same way, we could optimize the <literal>findAll</literal> method on "
-"<literal>D</literal> selects all the <literal>D</literal>&#39;s. A normal "
-"findAll query would look like this:"
-msgstr ""
-"以相同的方式,我们可以优化 <literal>D</literal> 的 <literal>findAll</"
-"literal> 方法,选择所有的  <literal>D</literal>。普通的 findAll 查询类似于: "
+msgid "In the same way, we could optimize the <literal>findAll</literal> method on <literal>D</literal> selects all the <literal>D</literal>&#39;s. A normal findAll query would look like this:"
+msgstr "以相同的方式,我们可以优化 <literal>D</literal> 的 <literal>findAll</literal> 方法,选择所有的  <literal>D</literal>。普通的 findAll 查询类似于: "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1582
@@ -5919,12 +4189,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1583
 #, no-c-format
-msgid ""
-"To preload the relations, we simply need to add the <literal>left-join</"
-"literal> elements to the query."
-msgstr ""
-"为了预加载关系,我们只需简单地把 <literal>left-join</literal> 元素添加到这个"
-"查询里。 "
+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
@@ -5934,8 +4200,7 @@
 "    &lt;query-method&gt;\n"
 "        &lt;method-name&gt;findAll&lt;/method-name&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT DISTINCT OBJECT(o) FROM D AS o ORDER "
-"BY o.id DESC]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT DISTINCT OBJECT(o) FROM D AS o ORDER BY o.id DESC]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
@@ -5949,8 +4214,7 @@
 "    &lt;query-method&gt;\n"
 "        &lt;method-name&gt;findAll&lt;/method-name&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT DISTINCT OBJECT(o) FROM D AS o ORDER "
-"BY o.id DESC]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT DISTINCT OBJECT(o) FROM D AS o ORDER BY o.id DESC]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
@@ -5989,13 +4253,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1591
 #, 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> 对象。 "
+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> 对象。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:1597
@@ -6006,46 +4265,26 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1598
 #, no-c-format
-msgid ""
-"Now let&#39;s look at a more complex configuration. Here we want to preload "
-"instance <literal>A</literal> along with several relations."
-msgstr ""
-"现在,让我们来看一个更为复杂的配置。在这里我们想预加载实例 <literal>A</"
-"literal> 以及几个关系。 "
+msgid "Now let&#39;s look at a more complex configuration. Here we want to preload instance <literal>A</literal> along with several relations."
+msgstr "现在,让我们来看一个更为复杂的配置。在这里我们想预加载实例 <literal>A</literal> 以及几个关系。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1603
 #, no-c-format
-msgid ""
-"its parent (self-relation) reached from <literal>A</literal> with CMR field "
-"<literal>parent</literal>"
-msgstr ""
-"通过 CMR 字段 <literal>parent</literal> 从 <literal>A</literal> 连接的父关系"
-"(自有关系)。 "
+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
 #, 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 "
-"<literal>B</literal> with CMR field <literal>c</literal>"
-msgstr ""
-"用 CMR 字段 <literal>b</literal> 从 <literal>A</literal> 到达的 <literal>B</"
-"literal>,以及相关的用 CMR 字段 <literal>c</literal> 到达的 <literal>C</"
-"literal>。 "
+msgid "the <literal>B</literal> reached from <literal>A</literal> with CMR field <literal>b</literal>, and the related <literal>C</literal> reached from <literal>B</literal> with CMR field <literal>c</literal>"
+msgstr "用 CMR 字段 <literal>b</literal> 从 <literal>A</literal> 到达的 <literal>B</literal>,以及相关的用 CMR 字段 <literal>c</literal> 到达的 <literal>C</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1613
 #, no-c-format
-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> "
-"reached from B with CMR field c."
-msgstr ""
-"从 <literal>A</literal> 到达的 <literal>B</literal>,但这次使用 CMR 字段 "
-"<literal>b2</literal> 且将其关联至从 B 用 CMR 字段 c 到达的 <literal>C</"
-"literal>。 "
+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> reached from B with CMR field c."
+msgstr "从 <literal>A</literal> 到达的 <literal>B</literal>,但这次使用 CMR 字段 <literal>b2</literal> 且将其关联至从 B 用 CMR 字段 c 到达的 <literal>C</literal>。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1618
@@ -6073,8 +4312,7 @@
 "    &lt;query-method&gt;\n"
 "        &lt;method-name&gt;findAll&lt;/method-name&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o ORDER BY o.id "
-"DESC]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o ORDER BY o.id DESC]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
@@ -6093,8 +4331,7 @@
 "    &lt;query-method&gt;\n"
 "        &lt;method-name&gt;findAll&lt;/method-name&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o ORDER BY o.id "
-"DESC]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o ORDER BY o.id DESC]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
@@ -6150,12 +4387,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1630
 #, no-c-format
-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 而不需要"
-"加载其他的数据库。 "
+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
@@ -6166,15 +4399,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1637
 #, no-c-format
-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-"
-"parent in one query. To do this, we would used nested <literal>left-join</"
-"literal> declaration."
-msgstr ""
-"这是另外一个自有关系(self-relation)的例子。假设我们想编写一个方法,它在查询"
-"里预加载一个实例、其 parent、 grand-parent 和 grand-grand-parent。为了实现这"
-"一点,我们将使用嵌套的 <literal>left-join</literal> 声明。 "
+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-parent in one query. To do this, we would used nested <literal>left-join</literal> declaration."
+msgstr "这是另外一个自有关系(self-relation)的例子。假设我们想编写一个方法,它在查询里预加载一个实例、其 parent、 grand-parent 和 grand-grand-parent。为了实现这一点,我们将使用嵌套的 <literal>left-join</literal> 声明。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1640
@@ -6187,17 +4413,14 @@
 "            &lt;method-param&gt;java.lang.Long&lt;/method-param&gt;\n"
 "        &lt;/method-params&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o WHERE o.id = ?"
-"1]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o WHERE o.id = ?1]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
 "        &lt;eager-load-group&gt;*&lt;/eager-load-group&gt;\n"
 "        &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic\"&gt;\n"
-"            &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic"
-"\"&gt;\n"
-"                &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic"
-"\"/&gt;\n"
+"            &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic\"&gt;\n"
+"                &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic\"/&gt;\n"
 "            &lt;/left-join&gt;\n"
 "        &lt;/left-join&gt;\n"
 "    &lt;/read-ahead&gt;\n"
@@ -6210,17 +4433,14 @@
 "            &lt;method-param&gt;java.lang.Long&lt;/method-param&gt;\n"
 "        &lt;/method-params&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o WHERE o.id = ?"
-"1]]&gt;&lt;/jboss-ql&gt;\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[SELECT OBJECT(o) FROM A AS o WHERE o.id = ?1]]&gt;&lt;/jboss-ql&gt;\n"
 "    &lt;read-ahead&gt;\n"
 "        &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "        &lt;page-size&gt;4&lt;/page-size&gt;\n"
 "        &lt;eager-load-group&gt;*&lt;/eager-load-group&gt;\n"
 "        &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic\"&gt;\n"
-"            &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic"
-"\"&gt;\n"
-"                &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic"
-"\"/&gt;\n"
+"            &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic\"&gt;\n"
+"                &lt;left-join cmr-field=\"parent\" eager-load-group=\"basic\"/&gt;\n"
 "            &lt;/left-join&gt;\n"
 "        &lt;/left-join&gt;\n"
 "    &lt;/read-ahead&gt;\n"
@@ -6230,28 +4450,24 @@
 #: The_CMP_Engine.xml:1644
 #, no-c-format
 msgid ""
-"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B_FK, t0_o.B2_FK, t0_o."
-"PARENT,\n"
+"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B_FK, t0_o.B2_FK, t0_o.PARENT,\n"
 "       t1_o_parent.id, t1_o_parent.name,\n"
 "       t2_o_parent_parent.id, t2_o_parent_parent.name,\n"
 "       t3_o_parent_parent_parent.id, t3_o_parent_parent_parent.name\n"
 "  FROM A t0_o\n"
 "       LEFT OUTER JOIN A t1_o_parent ON t0_o.PARENT=t1_o_parent.id\n"
-"       LEFT OUTER JOIN A t2_o_parent_parent ON t1_o_parent."
-"PARENT=t2_o_parent_parent.id\n"
+"       LEFT OUTER JOIN A t2_o_parent_parent ON t1_o_parent.PARENT=t2_o_parent_parent.id\n"
 "       LEFT OUTER JOIN A t3_o_parent_parent_parent \n"
 "            ON t2_o_parent_parent.PARENT=t3_o_parent_parent_parent.id\n"
 " WHERE (t0_o.id = ?) FOR UPDATE"
 msgstr ""
-"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B_FK, t0_o.B2_FK, t0_o."
-"PARENT,\n"
+"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B_FK, t0_o.B2_FK, t0_o.PARENT,\n"
 "       t1_o_parent.id, t1_o_parent.name,\n"
 "       t2_o_parent_parent.id, t2_o_parent_parent.name,\n"
 "       t3_o_parent_parent_parent.id, t3_o_parent_parent_parent.name\n"
 "  FROM A t0_o\n"
 "       LEFT OUTER JOIN A t1_o_parent ON t0_o.PARENT=t1_o_parent.id\n"
-"       LEFT OUTER JOIN A t2_o_parent_parent ON t1_o_parent."
-"PARENT=t2_o_parent_parent.id\n"
+"       LEFT OUTER JOIN A t2_o_parent_parent ON t1_o_parent.PARENT=t2_o_parent_parent.id\n"
 "       LEFT OUTER JOIN A t3_o_parent_parent_parent \n"
 "            ON t2_o_parent_parent.PARENT=t3_o_parent_parent_parent.id\n"
 " WHERE (t0_o.id = ?) FOR UPDATE"
@@ -6265,12 +4481,8 @@
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1648
 #, no-c-format
-msgid ""
-"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B2_FK, t0_o.PARENT FOR "
-"UPDATE"
-msgstr ""
-"SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B2_FK, t0_o.PARENT FOR "
-"UPDATE"
+msgid "SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B2_FK, t0_o.PARENT FOR UPDATE"
+msgstr "SELECT t0_o.id, t0_o.name, t0_o.secondName, t0_o.B2_FK, t0_o.PARENT FOR UPDATE"
 
 #. Tag: title
 #: The_CMP_Engine.xml:1654
@@ -6281,33 +4493,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1655
 #, no-c-format
-msgid ""
-"The <literal>on-load</literal> strategy block-loads additional data for "
-"several entities when an entity is loaded, starting with the requested "
-"entity and the next several entities in the order they were selected. This "
-"strategy is based on the theory that the results of a find or select will be "
-"accessed in forward order. When a query is executed, JBoss stores the order "
-"of the entities found in the list cache. Later, when one of the entities is "
-"loaded, JBoss uses this list to determine the block of entities to load. The "
-"number of lists stored in the cache is specified with the <literal>list-"
-"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> 策略不加载的有问题的数据。 "
+msgid "The <literal>on-load</literal> strategy block-loads additional data for several entities when an entity is loaded, starting with the requested entity and the next several entities in the order they were selected. This strategy is based on the theory that the results of a find or select will be accessed in forward order. When a query is executed, JBoss stores the order of the entities found in the list cache. Later, when one of the entities is loaded, JBoss uses this list to determine the block of entities to load. The number of lists stored in the cache is specified with the <literal>list-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
 #, 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> 配置的例子。 "
+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> 配置的例子。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:1661
@@ -6384,15 +4577,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1666
 #, no-c-format
-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 "
-"following two queries to load the <literal>name</literal>, "
-"<literal>nickName</literal> and <literal>badness</literal> fields for the "
-"entities:"
-msgstr ""
-"然而,在我们迭代结果集时数据的加载会有所不同。对于页面大小为 4 的结果集,JBoss 将只需要执行下面的两个查询来加载 <literal>name<"
-"/literal>、<literal>nickName</literal> 和 <literal>badness</literal> 字段。 "
+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 following two queries to load the <literal>name</literal>, <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
@@ -6433,20 +4619,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1866
 #, no-c-format
-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 "
-"specifically does not read-ahead any data or remember the order of the found "
-"entities. This results in the queries and performance shown at the beginning "
-"of this chapter. The none strategy is declared with a read-ahead element. If "
-"the <literal>read-ahead</literal> element contains a <literal>page-size</"
-"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 策略的例子。 "
+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 specifically does not read-ahead any data or remember the order of the found entities. This results in the queries and performance shown at the beginning of this chapter. The none strategy is declared with a read-ahead element. If the <literal>read-ahead</literal> element contains a <literal>page-size</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,15 +4681,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1878
 #, no-c-format
-msgid ""
-"In the previous section several steps use the phrase \"when the entity is "
-"loaded.\" This was intentionally left vague because the commit option "
-"specified for the entity and the current state of the transaction determine "
-"when an entity is loaded. The following section describes the commit options "
-"and the loading processes."
-msgstr ""
-"在前一节里,有几个步骤使用了短语 \"when the entity is loaded\"。这种模糊是故意留下的,因为为这个 entity "
-"指定的提交选项和事务的当前状态决定了 entity 的加载时机。下面的内容将描述提交选项和加载过程。 "
+msgid "In the previous section several steps use the phrase \"when the entity is loaded.\" This was intentionally left vague because the commit option specified for the entity and the current state of the transaction determine 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
@@ -6526,77 +4693,38 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1883
 #, no-c-format
-msgid ""
-"Central to the loading process are the commit options, which control when "
-"the data for an entity expires. JBoss supports four commit options "
-"<literal>A</literal>, <literal>B</literal>, <literal>C</literal> and "
-"<literal>D</literal>. The first three are described in the Enterprise "
-"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 所特有的。下面是对每个提交选项的详细描述: "
+msgid "Central to the loading process are the commit options, which control when the data for an entity expires. JBoss supports four commit options <literal>A</literal>, <literal>B</literal>, <literal>C</literal> and <literal>D</literal>. The first three are described in the Enterprise 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
 #, no-c-format
-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 "
-"between transactions, which can result is substantial performance gains. As "
-"a result of this assumption, no data managed by JBoss can be changed outside "
-"of JBoss. For example, changing data in another program or with the use of "
-"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 内部)都将导致不一致的数据库状态。 "
+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 between transactions, which can result is substantial performance gains. As a result of this assumption, no data managed by JBoss can be changed outside of JBoss. For example, changing data in another program or with the use of 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
 #, no-c-format
-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 "
-"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 的加载。它是缺省的提交选项。 "
+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 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
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">C</emphasis>: JBoss discards all entity context "
-"information at the end of the transaction."
+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 的上下文的信息。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1903
 #, no-c-format
-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> 相似,但其数据只在指定的时间内保持有效。 "
+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> 相似,但其数据只在指定的时间内保持有效。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1908
 #, no-c-format
-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\"/>. "
-"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>: "
+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\"/>. 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
@@ -6611,8 +4739,7 @@
 "&lt;jboss&gt;\n"
 "    &lt;container-configurations&gt;\n"
 "        &lt;container-configuration&gt;\n"
-"            &lt;container-name&gt;Standard CMP 2.x EntityBean&lt;/container-"
-"name&gt;\n"
+"            &lt;container-name&gt;Standard CMP 2.x EntityBean&lt;/container-name&gt;\n"
 "            &lt;commit-option&gt;A&lt;/commit-option&gt;\n"
 "        &lt;/container-configuration&gt;\n"
 "    &lt;/container-configurations&gt;\n"
@@ -6621,8 +4748,7 @@
 "&lt;jboss&gt;\n"
 "    &lt;container-configurations&gt;\n"
 "        &lt;container-configuration&gt;\n"
-"            &lt;container-name&gt;Standard CMP 2.x EntityBean&lt;/container-"
-"name&gt;\n"
+"            &lt;container-name&gt;Standard CMP 2.x EntityBean&lt;/container-name&gt;\n"
 "            &lt;commit-option&gt;A&lt;/commit-option&gt;\n"
 "        &lt;/container-configuration&gt;\n"
 "    &lt;/container-configurations&gt;\n"
@@ -6637,21 +4763,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1918
 #, no-c-format
-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> "
-"of the last query that selected this entity. If the entity has not been "
-"selected in a query, or the last query used the <literal>none</literal> read-"
-"ahead strategy, JBoss will use the default <literal>eager-load-group</"
-"literal> declared for the entity. In the following example configuration, "
-"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>。 "
+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> of the last query that selected this entity. If the entity has not been selected in a query, or the last query used the <literal>none</literal> read-ahead strategy, JBoss will use the default <literal>eager-load-group</literal> declared for the entity. In the following example configuration, 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
@@ -6700,43 +4813,30 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1922
 #, no-c-format
-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:"
+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 加载过程被初始化。下面是对这个加载过程的详细描述: "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1927
 #, no-c-format
-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 "
-"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 的上下文将保持有效。 "
+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 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
 #, no-c-format
-msgid ""
-"Any residual data in the entity context is flushed. This assures that old "
-"data does not bleed into the new load."
+msgid "Any residual data in the entity context is flushed. This assures that old data does not bleed into the new load."
 msgstr "Entity 上下文里的任何驻留数据都将被清除。这确保了旧的数据不会混在新的加载过程里。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1937
 #, no-c-format
-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."
+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 "主键值被注入回主键字段里。主键对象实际上独立于这些字段,它需要在第二步的清除后重新进行加载。 "
 
 #. Tag: para
-#: The_CMP_Engine.xml:1942 The_CMP_Engine.xml:1975
+#: 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 "预加载缓存里这个 entity 的任何数据都将加载到这些字段里。 "
@@ -6744,31 +4844,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1947
 #, no-c-format
-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 "
-"entity, but can be overridden if the entity was located using a query or CMR "
-"field with an <literal>on-find</literal> or <literal>on-load</literal> read "
-"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。 "
+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 entity, but can be overridden if the entity was located using a query or CMR field with an <literal>on-find</literal> or <literal>on-load</literal> read 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
 #, no-c-format
-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 "
-"described in <xref linkend=\"Read_ahead-on_load\"/>. The data for the "
-"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 的数据保存在预加载缓存中。 "
+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 described in <xref linkend=\"Read_ahead-on_load\"/>. The data for the 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
@@ -6785,17 +4868,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1966
 #, no-c-format
-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 "
-"bean is made, JBoss loads the field and all the fields of any <literal>lazy-"
-"load-group</literal> the field belong to. JBoss performs a set join and then "
-"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 操作,然后删除任何已经加载的字段。下面是一个配置示例。 "
+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 bean is made, JBoss loads the field and all the fields of any <literal>lazy-load-group</literal> the field belong to. JBoss performs a set join and then 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
@@ -6814,8 +4888,7 @@
 "                    &lt;field-name&gt;badness&lt;/field-name&gt;\n"
 "                &lt;/load-group&gt;\n"
 "                &lt;load-group&gt;\n"
-"                    &lt;load-group-name&gt;contact info&lt;/load-group-"
-"name&gt;\n"
+"                    &lt;load-group-name&gt;contact info&lt;/load-group-name&gt;\n"
 "                    &lt;field-name&gt;nickName&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;contactInfo&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;hangout&lt;/field-name&gt;\n"
@@ -6843,8 +4916,7 @@
 "                    &lt;field-name&gt;badness&lt;/field-name&gt;\n"
 "                &lt;/load-group&gt;\n"
 "                &lt;load-group&gt;\n"
-"                    &lt;load-group-name&gt;contact info&lt;/load-group-"
-"name&gt;\n"
+"                    &lt;load-group-name&gt;contact info&lt;/load-group-name&gt;\n"
 "                    &lt;field-name&gt;nickName&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;contactInfo&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;hangout&lt;/field-name&gt;\n"
@@ -6862,48 +4934,26 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1970
 #, no-c-format
-msgid ""
-"When the bean provider calls <literal>getName()</literal> with this "
-"configuration, JBoss loads <literal>name</literal>, <literal>nickName</"
-"literal> and <literal>badness</literal>, assuming they are not already "
-"loaded. When the bean provider calls <literal>getNickName()</literal>, the "
-"<literal>name</literal>, <literal>nickName</literal>, <literal>badness</"
-"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 加载过程的详细描述: "
+msgid "When the bean provider calls <literal>getName()</literal> with this configuration, JBoss loads <literal>name</literal>, <literal>nickName</literal> and <literal>badness</literal>, assuming they are not already loaded. When the bean provider calls <literal>getNickName()</literal>, the <literal>name</literal>, <literal>nickName</literal>, <literal>badness</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
 #, no-c-format
-msgid ""
-"If the field value was loaded by the preload cache the lazy load process is "
-"finished."
+msgid "If the field value was loaded by the preload cache the lazy load process is finished."
 msgstr "如果字段值通过预加载缓存加载,那么 lazy 加载过程就结束了。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1985
 #, no-c-format
-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."
+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 操作,并删除已经加载的任何字段。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:1990
 #, no-c-format
-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 "
-"is stored in the context and the data for the other entities is stored in "
-"the preload cache."
-msgstr ""
-"我们执行一个查询来选择所需的列。和基本的加载过程一样,JBoss 可以加载一个 entity 块。当前 entity 的数据保存在上下文里,而其他 "
-"entity 的数据则存储在预加载缓存里。 "
+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 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
@@ -6914,25 +4964,13 @@
 #. Tag: para
 #: The_CMP_Engine.xml:1997
 #, no-c-format
-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 "
-"loaded, meaning the value of the currently sought entity and the values of "
-"the CMR field for the next several entities are loaded. As a query, the "
-"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> 进行预加载。 "
+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 loaded, meaning the value of the currently sought entity and the values of the CMR field for the next several entities are loaded. As a query, the 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
 #, no-c-format
-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:"
+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 表将被生成。下面是示例代码: "
 
 #. Tag: title
@@ -7006,15 +5044,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2005
 #, no-c-format
-msgid ""
-"For this example, the configuration of the gangster&#39;s "
-"<literal>findAll_onfind</literal> query is unchanged from the <literal>on-"
-"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> 关系的配置: "
+msgid "For this example, the configuration of the gangster&#39;s <literal>findAll_onfind</literal> query is unchanged from the <literal>on-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
@@ -7032,8 +5063,7 @@
 "            &lt;ejb-name&gt;LocationEJB&lt;/ejb-name&gt;\n"
 "            &lt;load-groups&gt;\n"
 "                &lt;load-group&gt;\n"
-"                    &lt;load-group-name&gt;quick info&lt;/load-group-"
-"name&gt;\n"
+"                    &lt;load-group-name&gt;quick info&lt;/load-group-name&gt;\n"
 "                    &lt;field-name&gt;city&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;state&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;zipCode&lt;/field-name&gt;\n"
@@ -7044,8 +5074,7 @@
 "    &lt;/enterprise-beans&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Gangster-Hangout&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Gangster-Hangout&lt;/ejb-relation-name&gt;\n"
 "            &lt;foreign-key-mapping/&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
 "                &lt;ejb-relationship-role-name&gt;\n"
@@ -7055,8 +5084,7 @@
 "                &lt;read-ahead&gt;\n"
 "                    &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "                    &lt;page-size&gt;4&lt;/page-size&gt;\n"
-"                    &lt;eager-load-group&gt;quick info&lt;/eager-load-"
-"group&gt;\n"
+"                    &lt;eager-load-group&gt;quick info&lt;/eager-load-group&gt;\n"
 "                &lt;/read-ahead&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
@@ -7080,8 +5108,7 @@
 "            &lt;ejb-name&gt;LocationEJB&lt;/ejb-name&gt;\n"
 "            &lt;load-groups&gt;\n"
 "                &lt;load-group&gt;\n"
-"                    &lt;load-group-name&gt;quick info&lt;/load-group-"
-"name&gt;\n"
+"                    &lt;load-group-name&gt;quick info&lt;/load-group-name&gt;\n"
 "                    &lt;field-name&gt;city&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;state&lt;/field-name&gt;\n"
 "                    &lt;field-name&gt;zipCode&lt;/field-name&gt;\n"
@@ -7092,8 +5119,7 @@
 "    &lt;/enterprise-beans&gt;\n"
 "    &lt;relationships&gt;\n"
 "        &lt;ejb-relation&gt;\n"
-"            &lt;ejb-relation-name&gt;Gangster-Hangout&lt;/ejb-relation-"
-"name&gt;\n"
+"            &lt;ejb-relation-name&gt;Gangster-Hangout&lt;/ejb-relation-name&gt;\n"
 "            &lt;foreign-key-mapping/&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
 "                &lt;ejb-relationship-role-name&gt;\n"
@@ -7103,8 +5129,7 @@
 "                &lt;read-ahead&gt;\n"
 "                    &lt;strategy&gt;on-find&lt;/strategy&gt;\n"
 "                    &lt;page-size&gt;4&lt;/page-size&gt;\n"
-"                    &lt;eager-load-group&gt;quick info&lt;/eager-load-"
-"group&gt;\n"
+"                    &lt;eager-load-group&gt;quick info&lt;/eager-load-group&gt;\n"
 "                &lt;/read-ahead&gt;\n"
 "            &lt;/ejb-relationship-role&gt;\n"
 "            &lt;ejb-relationship-role&gt;\n"
@@ -7143,13 +5168,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2014
 #, no-c-format
-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> 字段。 "
+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> 字段。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2017
@@ -7206,15 +5226,21 @@
 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
+#: 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 "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
+#: 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
 msgid "<entry>CA</entry>"
 msgstr "<entry>CA</entry>"
@@ -7226,7 +5252,9 @@
 msgstr "94108"
 
 #. Tag: entry
-#: The_CMP_Engine.xml:2119 The_CMP_Engine.xml:2148 The_CMP_Engine.xml:2177
+#: 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"
@@ -7295,16 +5323,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2306
 #, no-c-format
-msgid ""
-"By default, when a multi-object finder or select method is executed the JDBC "
-"result set is read to the end immediately. The client receives a collection "
-"of <literal>EJBLocalObject</literal> or CMP field values which it can then "
-"iterate through. For big result sets this approach is not efficient. In some "
-"cases it is better to delay reading the next row in the result set until the "
-"client tries to read the corresponding value from the collection. You can "
-"get this behavior for a query using the <literal>lazy-resultset-loading</"
-"literal> element."
-msgstr ""
+msgid "By default, when a multi-object finder or select method is executed the JDBC result set is read to the end immediately. The client receives a collection of <literal>EJBLocalObject</literal> or CMP field values which it can then iterate through. For big result sets this approach is not efficient. In some cases it is better to delay reading the next row in the result set until the client tries to read the corresponding value from the collection. You can get this behavior for a query using the <literal>lazy-resultset-loading</literal> element."
+msgstr "在缺省情况下,当一个多对象 finder 或者 select 方法被执行时,JDBC 结果集将马上输出到终端。客户接收到 <literal>EJBLocalObject</literal> 或 CMP 字段值的集合并进行迭代。对于大的结果集,这个方法效率不高。在某些情况下延迟对下一条记录的读取(也就是直至客户试图读取对应的值时才读取)会更好。你可以用 <literal>lazy-resultset-loading</literal> 元素设置这种行为。"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2309
@@ -7314,37 +5334,23 @@
 "    &lt;query-method&gt;\n"
 "        &lt;method-name&gt;findAll&lt;/method-name&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[select object(o) from A o]]&gt;&lt;/jboss-"
-"ql&gt;\n"
-"    <emphasis role=\"bold\">&lt;lazy-resultset-loading&gt;true&lt;/lazy-"
-"resultset-loading&gt;</emphasis>\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[select object(o) from A o]]&gt;&lt;/jboss-ql&gt;\n"
+"    <emphasis role=\"bold\">&lt;lazy-resultset-loading&gt;true&lt;/lazy-resultset-loading&gt;</emphasis>\n"
 "&lt;/query&gt;"
 msgstr ""
 "&lt;query&gt;\n"
 "    &lt;query-method&gt;\n"
 "        &lt;method-name&gt;findAll&lt;/method-name&gt;\n"
 "    &lt;/query-method&gt;\n"
-"    &lt;jboss-ql&gt;&lt;![CDATA[select object(o) from A o]]&gt;&lt;/jboss-"
-"ql&gt;\n"
-"    <emphasis role=\"bold\">&lt;lazy-resultset-loading&gt;true&lt;/lazy-"
-"resultset-loading&gt;</emphasis>\n"
+"    &lt;jboss-ql&gt;&lt;![CDATA[select object(o) from A o]]&gt;&lt;/jboss-ql&gt;\n"
+"    <emphasis role=\"bold\">&lt;lazy-resultset-loading&gt;true&lt;/lazy-resultset-loading&gt;</emphasis>\n"
 "&lt;/query&gt;"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2310
 #, no-c-format
-msgid ""
-"The are some issues you should be aware of when using lazy result set "
-"loading. Special care should be taken when working with a "
-"<literal>Collection</literal> associated with a lazily loaded result set. "
-"The first call to <literal>iterator()</literal> returns a special "
-"<literal>Iterator</literal> that reads from the <literal>ResultSet</"
-"literal>. Until this <literal>Iterator</literal> has been exhausted, "
-"subsequent calls to <literal>iterator()</literal> or calls to the "
-"<literal>add()</literal> method will result in an exception. The "
-"<literal>remove()</literal> and <literal>size()</literal> methods work as "
-"would be expected."
-msgstr ""
+msgid "The are some issues you should be aware of when using lazy result set loading. Special care should be taken when working with a <literal>Collection</literal> associated with a lazily loaded result set. The first call to <literal>iterator()</literal> returns a special <literal>Iterator</literal> that reads from the <literal>ResultSet</literal>. Until this <literal>Iterator</literal> has been exhausted, subsequent calls to <literal>iterator()</literal> or calls to the <literal>add()</literal> method will result in an exception. The <literal>remove()</literal> and <literal>size()</literal> methods work as would be expected."
+msgstr "使用 lazy 结果集加载时你应该注意一些情况。当使用和 lazy 加载结果集相关联的 <literal>Collection</literal> 时,你需要格外小心。对 <literal>iterator()</literal> 的第一次调用返回一个特殊的 <literal>Iterator</literal>,它从 <literal>ResultSet</literal> 读取结果。在这个 <literal>Iterator</literal> 执行完毕后,随后对 <literal>iterator()</literal> 的或 <literal>add()</literal> 方法的调用将导致异常抛出。<literal>remove()</literal> 和 <literal>size()</literal> 方法则如所预期的一样执行。"
 
 #. Tag: title
 #: The_CMP_Engine.xml:2318
@@ -7355,23 +5361,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2319
 #, no-c-format
-msgid ""
-"All of the examples presented in this chapter have been defined to run in a "
-"transaction. Transaction granularity is a dominating factor in optimized "
-"loading because transactions define the lifetime of preloaded data. If the "
-"transaction completes, commits, or rolls back, the data in the preload cache "
-"is lost. This can result in a severe negative performance impact."
-msgstr ""
+msgid "All of the examples presented in this chapter have been defined to run in a transaction. Transaction granularity is a dominating factor in optimized loading because transactions define the lifetime of preloaded data. If the transaction completes, commits, or rolls back, the data in the preload cache is lost. This can result in a severe negative performance impact."
+msgstr "本章里所有的例子都是在事务里运行的。事务的颗粒度是优化负载平衡的决定性因素,因为事务定义了预加载数据的生命周期。如果事务完成、提交或回滚,预加载缓存里的数据将会丢失。这会导致严重的性能问题。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2322
 #, no-c-format
-msgid ""
-"The performance impact of running without a transaction will be demonstrated "
-"with an example that uses an <literal>on-find</literal> optimized query that "
-"selects the first four gangsters (to keep the result set small), and it is "
-"executed without a wrapper transaction. The example code follows:"
-msgstr ""
+msgid "The performance impact of running without a transaction will be demonstrated with an example that uses an <literal>on-find</literal> optimized query that selects the first four gangsters (to keep the result set small), and it is executed without a wrapper transaction. The example code follows:"
+msgstr "我们将用一个例子来演示没有事务时对运行性能的影响,它使用 <literal>on-find</literal> 优化查询,选择"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2325
@@ -7430,7 +5427,6 @@
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2329
 #, 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"
@@ -7445,12 +5441,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2330
 #, no-c-format
-msgid ""
-"Normally this would be the only query executed, but since this code is not "
-"running in a transaction, all of the preloaded data is thrown away as soon "
-"as finder returns. Then when the CMP field is accessed JBoss executes the "
-"following four queries (one for each loop):"
-msgstr ""
+msgid "Normally this would be the only query executed, but since this code is not running in a transaction, all of the preloaded data is thrown away as soon as finder returns. Then when the CMP field is accessed JBoss executes the following four queries (one for each loop):"
+msgstr "通常,这将是唯一执行的查询,但既然这段代码不是在事务里运行的,只要 finder 返回,所有的预加载数据都会被丢弃。当 CMP 字段被访问时,JBoss 将执行下列 4 个查询(每个循环对应一个):"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2333
@@ -7485,11 +5477,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2334
 #, no-c-format
-msgid ""
-"It&#39;s actually worse than this. JBoss executes each of these queries "
-"three times; once for each CMP field that is accessed. This is because the "
-"preloaded values are discarded between the CMP field accessor calls."
-msgstr ""
+msgid "It&#39;s actually worse than this. JBoss executes each of these queries three times; once for each CMP field that is accessed. This is because the preloaded values are discarded between the CMP field accessor calls."
+msgstr "这实际上会更差。JBoss 把这些查询每个都执行三次;每次都是用被访问的 CMP字段。这是因为预加载的值在两次 CMP 字段访问之间会被丢弃。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2337
@@ -7501,32 +5490,19 @@
 #: The_CMP_Engine.xml:2341
 #, no-c-format
 msgid "No Transaction on-find optimized query execution"
-msgstr ""
+msgstr "无事务的 on-find 优化查询的执行"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2348
 #, no-c-format
-#, fuzzy
-msgid ""
-"This performance is much worse than read ahead none because of the amount of "
-"data loaded from the database. The number of rows loaded is determined by "
-"the following equation:"
+msgid "This performance is much worse than read ahead none because of the amount of data loaded from the database. The number of rows loaded is determined by the following equation:"
 msgstr "none ç­–ç•¥:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2356
 #, no-c-format
-msgid ""
-"This all happens because the transaction in the example is bounded by a "
-"single call on the entity. This brings up the important question \"How do I "
-"run my code in a transaction?\" The answer depends on where the code runs. "
-"If it runs in an EJB (session, entity, or message driven), the method must "
-"be marked with the <literal>Required</literal> or <literal>RequiresNew</"
-"literal><literal>trans-attribute</literal> in the <literal>assembly-"
-"descriptor</literal>. If the code is not running in an EJB, a user "
-"transaction is necessary. The following code wraps a call to the declared "
-"method with a user transaction:"
-msgstr ""
+msgid "This all happens because the transaction in the example is bounded by a single call on the entity. This brings up the important question \"How do I run my code in a transaction?\" The answer depends on where the code runs. If it runs in an EJB (session, entity, or message driven), the method must be marked with the <literal>Required</literal> or <literal>RequiresNew</literal><literal>trans-attribute</literal> in the <literal>assembly-descriptor</literal>. If the code is not running in an EJB, a user transaction is necessary. The following code wraps a call to the declared method with a user transaction:"
+msgstr "这是因为本例里的事务由实体上的单个调用绑定。这带来一个重要的疑问“怎样在事务里运行我的代码?”其答案取决于代码在哪里运行。如果它在 EJB(Session、Entity、Message Driven)里运行,这方法将用  <literal>assembly-descriptor</literal> 里的 <literal>Required</literal> or <literal>RequiresNew</literal><literal>trans-attribute</literal> 进行标记。如果代码没有在 EJB 里运行,用户事务就是必需的。下面的代码用用户事务包裹了对声明方法的调用:"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2359
@@ -7605,36 +5581,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2364
 #, no-c-format
-msgid ""
-"JBoss has supports for optimistic locking of entity beans. Optimistic "
-"locking allows multiple instances of the same entity bean to be active "
-"simultaneously. Consistency is enforced based on the optimistic locking "
-"policy choice. The optimistic locking policy choice defines the set of "
-"fields that are used in the commit time write of modified data to the "
-"database. The optimistic consistency check asserts that the values of the "
-"chosen set of fields has the same values in the database as existed when the "
-"current transaction was started. This is done using a <literal>select for "
-"UPDATE WHERE ...</literal> statement that contains the value assertions."
-msgstr ""
-"JBoss 支持 entity bean 的乐观锁定。乐观锁定允许相同的 entity bean 的多个实例"
-"同时处于活动状态。对于乐观锁定策略而言,一致性是强制的。乐观锁定策略选择定义"
-"了用在提交阶段把有改动的数据写入数据库时使用的字段。乐观一致性检查判断选定字"
-"段的值是否和在当前事务开始时就存在于数据库里的值相同。这是通过包含值判断的 "
-"<literal>select for UPDATE WHERE ...</literal> 语句来完成的。 "
+msgid "JBoss has supports for optimistic locking of entity beans. Optimistic locking allows multiple instances of the same entity bean to be active simultaneously. Consistency is enforced based on the optimistic locking policy choice. The optimistic locking policy choice defines the set of fields that are used in the commit time write of modified data to the database. The optimistic consistency check asserts that the values of the chosen set of fields has the same values in the database as existed when the current transaction was started. This is done using a <literal>select for UPDATE WHERE ...</literal> statement that contains the value assertions."
+msgstr "JBoss 支持 entity bean 的乐观锁定。乐观锁定允许相同的 entity bean 的多个实例同时处于活动状态。对于乐观锁定策略而言,一致性是强制的。乐观锁定策略选择定义了用在提交阶段把有改动的数据写入数据库时使用的字段。乐观一致性检查判断选定字段的值是否和在当前事务开始时就存在于数据库里的值相同。这是通过包含值判断的 <literal>select for UPDATE WHERE ...</literal> 语句来完成的。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2367
 #, no-c-format
-msgid ""
-"You specify the optimistic locking policy choice using an "
-"<literal>optimistic-locking</literal> element in the <literal>jbosscmp-jdbc."
-"xml</literal> descriptor. The content model of the <literal>optimistic-"
-"locking</literal> element is shown below and the description of the elements "
-"follows."
-msgstr ""
-"你可以在 <literal>jbosscmp-jdbc.xml</literal> 描述符里通过 "
-"<literal>optimistic-locking</literal> 元素指定乐观锁定策略选择。下面是 "
-"<literal>optimistic-locking</literal> 元素的内容模型及其描述。 "
+msgid "You specify the optimistic locking policy choice using an <literal>optimistic-locking</literal> element in the <literal>jbosscmp-jdbc.xml</literal> descriptor. The content model of the <literal>optimistic-locking</literal> element is shown below and the description of the elements follows."
+msgstr "你可以在 <literal>jbosscmp-jdbc.xml</literal> 描述符里通过 <literal>optimistic-locking</literal> 元素指定乐观锁定策略选择。下面是 <literal>optimistic-locking</literal> 元素的内容模型及其描述。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:2371
@@ -7645,112 +5599,44 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2380
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">group-name</emphasis>: This element specifies that "
-"optimistic locking is based on the fields of a <literal>load-group</"
-"literal>. This value of this element must match one of the entity&#39;s "
-"<literal>load-group-name</literal>. The fields in this group will be used "
-"for optimistic locking."
-msgstr ""
-"<emphasis role=\"bold\">group-name</emphasis>:这个元素指定优化锁定基于 "
-"<literal>load-group</literal> 的字段。这个元素的值必须匹配 entity 的 "
-"<literal>load-group-name</literal> 中的一个。这个组里的字段将用于优化锁定。 "
+msgid "<emphasis role=\"bold\">group-name</emphasis>: This element specifies that optimistic locking is based on the fields of a <literal>load-group</literal>. This value of this element must match one of the entity&#39;s <literal>load-group-name</literal>. The fields in this group will be used for optimistic locking."
+msgstr "<emphasis role=\"bold\">group-name</emphasis>:这个元素指定优化锁定基于 <literal>load-group</literal> 的字段。这个元素的值必须匹配 entity 的 <literal>load-group-name</literal> 中的一个。这个组里的字段将用于优化锁定。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2385
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">modified-strategy</emphasis>: This element specifies "
-"that optimistic locking is based on the modified fields. This strategy "
-"implies that the fields that were modified during transaction will be used "
-"for optimistic locking."
-msgstr ""
-"<emphasis role=\"bold\">modified-strategy</emphasis>:这个元素指定优化锁定基"
-"于被修改的字段。这个策略暗示这在事务中被修改的字段将被用于乐观锁定。 "
+msgid "<emphasis role=\"bold\">modified-strategy</emphasis>: This element specifies that optimistic locking is based on the modified fields. This strategy implies that the fields that were modified during transaction will be used for optimistic locking."
+msgstr "<emphasis role=\"bold\">modified-strategy</emphasis>:这个元素指定优化锁定基于被修改的字段。这个策略暗示这在事务中被修改的字段将被用于乐观锁定。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2390
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-strategy</emphasis>: This element specifies "
-"that optimistic locking is based on the fields read. This strategy implies "
-"that the fields that were read/changed in the transaction will be used for "
-"optimistic locking."
-msgstr ""
-"<emphasis role=\"bold\">read-strategy</emphasis>:这个元素指定用户锁定基于字"
-"段的读取。这个策略表示在事务中被读/修改的字段将被用于乐观锁定。 "
+msgid "<emphasis role=\"bold\">read-strategy</emphasis>: This element specifies that optimistic locking is based on the fields read. This strategy implies that the fields that were read/changed in the transaction will be used for optimistic locking."
+msgstr "<emphasis role=\"bold\">read-strategy</emphasis>:这个元素指定用户锁定基于字段的读取。这个策略表示在事务中被读/修改的字段将被用于乐观锁定。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2395
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">version-column</emphasis>: This element specifies "
-"that optimistic locking is based on a version column strategy. Specifying "
-"this element will add an additional version field of type <literal>java.lang."
-"Long</literal> to the entity bean for optimistic locking. Each update of the "
-"entity will increase the value of this field. The <literal>field-name</"
-"literal> element allows for the specification of the name of the CMP field "
-"while the <literal>column-name</literal> element allows for the "
-"specification of the corresponding table column."
-msgstr ""
-"<emphasis role=\"bold\">version-column</emphasis>:这个元素指定优化锁定基于 "
-"version 列的策略。指定这个元素将在 entity bean 里添加一个额外的 version 字"
-"段,其类型为 <literal>java.lang.Long</literal>。每次对 entity 的更新都使这个"
-"字段的值增加。<literal>field-name</literal> 元素允许指定 CMP 字段的名字,而 "
-"<literal>column-name</literal> 元素则允许指定对应的表的列的名称。 "
+msgid "<emphasis role=\"bold\">version-column</emphasis>: This element specifies that optimistic locking is based on a version column strategy. Specifying this element will add an additional version field of type <literal>java.lang.Long</literal> to the entity bean for optimistic locking. Each update of the entity will increase the value of this field. The <literal>field-name</literal> element allows for the specification of the name of the CMP field while the <literal>column-name</literal> element allows for the specification of the corresponding table column."
+msgstr "<emphasis role=\"bold\">version-column</emphasis>:这个元素指定优化锁定基于 version 列的策略。指定这个元素将在 entity bean 里添加一个额外的 version 字段,其类型为 <literal>java.lang.Long</literal>。每次对 entity 的更新都使这个字段的值增加。<literal>field-name</literal> 元素允许指定 CMP 字段的名字,而 <literal>column-name</literal> 元素则允许指定对应的表的列的名称。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2400
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">timestamp-column</emphasis>: This element specifies "
-"that optimistic locking is based on a timestamp column strategy. Specifying "
-"this element will add an additional version field of type <literal>java.util."
-"Date</literal> to the entity bean for optimistic locking. Each update of the "
-"entity will set the value of this field to the current time. The "
-"<literal>field-name</literal> element allows for the specification of the "
-"name of the CMP field while the <literal>column-name</literal> element "
-"allows for the specification of the corresponding table column."
-msgstr ""
-"<emphasis role=\"bold\">timestamp-column</emphasis>:这个元素指定优化锁定基"
-"于 timestamp 列的策略。指定这个元素将在 entity bean 里添加一个额外的 version "
-"字段,其类型为 <literal>java.lang.Date</literal>。每次对 entity 的更新都使这"
-"个字段的值增加。<literal>field-name</literal> 元素允许指定 CMP 字段的名字,"
-"而 <literal>column-name</literal> 元素则允许指定对应的表的列的名称。 "
+msgid "<emphasis role=\"bold\">timestamp-column</emphasis>: This element specifies that optimistic locking is based on a timestamp column strategy. Specifying this element will add an additional version field of type <literal>java.util.Date</literal> to the entity bean for optimistic locking. Each update of the entity will set the value of this field to the current time. The <literal>field-name</literal> element allows for the specification of the name of the CMP field while the <literal>column-name</literal> element allows for the specification of the corresponding table column."
+msgstr "<emphasis role=\"bold\">timestamp-column</emphasis>:这个元素指定优化锁定基于 timestamp 列的策略。指定这个元素将在 entity bean 里添加一个额外的 version 字段,其类型为 <literal>java.lang.Date</literal>。每次对 entity 的更新都使这个字段的值增加。<literal>field-name</literal> 元素允许指定 CMP 字段的名字,而 <literal>column-name</literal> 元素则允许指定对应的表的列的名称。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2405
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">key-generator-factory</emphasis>: This element "
-"specifies that optimistic locking is based on key generation. The value of "
-"the element is the JNDI name of a <literal>org.jboss.ejb.plugins."
-"keygenerator.KeyGeneratorFactory</literal> implementation. Specifying this "
-"element will add an additional version field to the entity bean for "
-"optimistic locking. The type of the field must be specified via the "
-"<literal>field-type</literal> element. Each update of the entity will update "
-"the key field by obtaining a new value from the key generator. The "
-"<literal>field-name</literal> element allows for the specification of the "
-"name of the CMP field while the <literal>column-name</literal> element "
-"allows for the specification of the corresponding table column."
-msgstr ""
-"<emphasis role=\"bold\">key-generator-factory</emphasis>:这个元素指定用户锁"
-"定基于键的生成。这个元素的值是 <literal>org.jboss.ejb.plugins.keygenerator."
-"KeyGeneratorFactory</literal> 实现的 JNDI 名字。指定这个元素将在 entity bean "
-"里添加一个额外的 version 字段。这个字段的类型必须通过 <literal>field-type</"
-"literal> 元素来指定。每次对 entity 的更新都使这个字段的值增加。"
-"<literal>field-name</literal> 元素允许指定 CMP 字段的名字,而 "
-"<literal>column-name</literal> 元素则允许指定对应的表的列的名称。 "
+msgid "<emphasis role=\"bold\">key-generator-factory</emphasis>: This element specifies that optimistic locking is based on key generation. The value of the element is the JNDI name of a <literal>org.jboss.ejb.plugins.keygenerator.KeyGeneratorFactory</literal> implementation. Specifying this element will add an additional version field to the entity bean for optimistic locking. The type of the field must be specified via the <literal>field-type</literal> element. Each update of the entity will update the key field by obtaining a new value from the key generator. The <literal>field-name</literal> element allows for the specification of the name of the CMP field while the <literal>column-name</literal> element allows for the specification of the corresponding table column."
+msgstr "<emphasis role=\"bold\">key-generator-factory</emphasis>:这个元素指定用户锁定基于键的生成。这个元素的值是 <literal>org.jboss.ejb.plugins.keygenerator.KeyGeneratorFactory</literal> 实现的 JNDI 名字。指定这个元素将在 entity bean 里添加一个额外的 version 字段。这个字段的类型必须通过 <literal>field-type</literal> 元素来指定。每次对 entity 的更新都使这个字段的值增加。<literal>field-name</literal> 元素允许指定 CMP 字段的名字,而 <literal>column-name</literal> 元素则允许指定对应的表的列的名称。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2410
 #, no-c-format
-msgid ""
-"A sample <literal>jbosscmp-jdbc.xml</literal> descriptor illustrating all of "
-"the optimistic locking strategies is given below."
-msgstr ""
-"下面的 <literal>jbosscmp-jdbc.xml</literal> 描述符示例演示了所有的用户锁定策"
-"略。 "
+msgid "A sample <literal>jbosscmp-jdbc.xml</literal> descriptor illustrating all of the optimistic locking strategies is given below."
+msgstr "下面的 <literal>jbosscmp-jdbc.xml</literal> 描述符示例演示了所有的用户锁定策略。 "
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2413
@@ -7889,8 +5775,7 @@
 "                &lt;field-name&gt;stringField&lt;/field-name&gt;\n"
 "            &lt;/cmp-field&gt;\n"
 "            &lt;optimistic-locking&gt;\n"
-"                &lt;key-generator-factory&gt;UUIDKeyGeneratorFactory&lt;/key-"
-"generator-factory&gt;\n"
+"                &lt;key-generator-factory&gt;UUIDKeyGeneratorFactory&lt;/key-generator-factory&gt;\n"
 "                &lt;field-type&gt;java.lang.String&lt;/field-type&gt;\n"
 "                &lt;field-name&gt;uuidField&lt;/field-name&gt;\n"
 "                &lt;column-name&gt;ol_uuid&lt;/column-name&gt;\n"
@@ -8034,8 +5919,7 @@
 "                &lt;field-name&gt;stringField&lt;/field-name&gt;\n"
 "            &lt;/cmp-field&gt;\n"
 "            &lt;optimistic-locking&gt;\n"
-"                &lt;key-generator-factory&gt;UUIDKeyGeneratorFactory&lt;/key-"
-"generator-factory&gt;\n"
+"                &lt;key-generator-factory&gt;UUIDKeyGeneratorFactory&lt;/key-generator-factory&gt;\n"
 "                &lt;field-type&gt;java.lang.String&lt;/field-type&gt;\n"
 "                &lt;field-name&gt;uuidField&lt;/field-name&gt;\n"
 "                &lt;column-name&gt;ol_uuid&lt;/column-name&gt;\n"
@@ -8055,25 +5939,8 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2418
 #, no-c-format
-msgid ""
-"Support for primary key generation outside of the entity bean is available "
-"through custom implementations of the entity creation command objects used "
-"to insert entities into a persistent store. The list of available commands "
-"is specified in entity-commands element of the <literal>jbosscmp-jdbc.xml</"
-"literal> descriptor. The default <literal>entity-command</literal> may be "
-"specified in the <literal>jbosscmp-jdbc.xml</literal> in defaults element. "
-"Each entity element can override the <literal>entity-command</literal> in "
-"defaults by specifying its own <literal>entity-command</literal>. The "
-"content model of the <literal>entity-commands</literal> and child elements "
-"is given below."
-msgstr ""
-"支持 entity bean 外的主键生成可通过自定义 entity 的 creation 命令来实现,这个"
-"命令被用来把 entity 插入到持久性存储里。<literal>jbosscmp-jdbc.xml</literal> "
-"描述符里的 entity-commands 元素指定了可用的命令。缺省的 <literal>entity-"
-"command</literal> 可以在 <literal>jbosscmp-jdbc.xml</literal> 的 defaults 元"
-"素里指定。每个 entity 元素都可以通过指定自己的 <literal>entity-command</"
-"literal> 覆盖缺省的 <literal>entity-command</literal>。下面是 "
-"<literal>entity-commands</literal> 及其子元素的内容模型。 "
+msgid "Support for primary key generation outside of the entity bean is available through custom implementations of the entity creation command objects used to insert entities into a persistent store. The list of available commands is specified in entity-commands element of the <literal>jbosscmp-jdbc.xml</literal> descriptor. The default <literal>entity-command</literal> may be specified in the <literal>jbosscmp-jdbc.xml</literal> in defaults element. Each entity element can override the <literal>entity-command</literal> in defaults by specifying its own <literal>entity-command</literal>. The content model of the <literal>entity-commands</literal> and child elements is given below."
+msgstr "支持 entity bean 外的主键生成可通过自定义 entity 的 creation 命令来实现,这个命令被用来把 entity 插入到持久性存储里。<literal>jbosscmp-jdbc.xml</literal> 描述符里的 entity-commands 元素指定了可用的命令。缺省的 <literal>entity-command</literal> 可以在 <literal>jbosscmp-jdbc.xml</literal> 的 defaults 元素里指定。每个 entity 元素都可以通过指定自己的 <literal>entity-command</literal> 覆盖缺省的 <literal>entity-command</literal>。下面是 <literal>entity-commands</literal> 及其子元素的内容模型。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:2422
@@ -8084,50 +5951,14 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2429
 #, no-c-format
-msgid ""
-"Each <literal>entity-command</literal> element specifies an entity "
-"generation implementation. The <literal>name</literal> attribute specifies a "
-"name that allows the command defined in an <literal>entity-commands</"
-"literal> section to be referenced in the defaults and entity elements. The "
-"<literal>class</literal> attribute specifies the implementation of the "
-"<literal>org.jboss.ejb.plugins.cmp.jdbc</literal>. "
-"<literal>JDBCCreateEntityCommand</literal> that supports the key generation. "
-"Database vendor specific commands typically subclass the <literal>org.jboss."
-"ejb.plugins.cmp.jdbc</literal>. <literal>JDBCIdentityColumnCreateCommand</"
-"literal> if the database generates the primary key as a side effect of doing "
-"an insert, or the <literal>org.jboss.ejb.plugins.cmp.jdbc."
-"JDBCInsertPKCreateCommand</literal> if the command must insert the generated "
-"key."
-msgstr ""
-"每个 <literal>entity-command</literal> 元素都指定了一个 entity 生成实现。"
-"<literal>name</literal> 属性指定的名称可以允许在 defaults 和 entity 元素里引"
-"用 <literal>entity-commands</literal> 部分定义的命令。<literal>class</"
-"literal> 属性指定支持键生成的  <literal>org.jboss.ejb.plugins.cmp.jdbc</"
-"literal>.<literal>JDBCCreateEntityCommand</literal> 的实现。如果数据库把生成"
-"主键当作插入的附属动作的话,数据库供应商专有的命令通常作为 <literal>org."
-"jboss.ejb.plugins.cmp.jdbc</literal>."
-"<literal>JDBCIdentityColumnCreateCommand</literal> 的子类,而如果命令必须插入"
-"生成的键时,它会作为 <literal>org.jboss.ejb.plugins.cmp.jdbc."
-"JDBCInsertPKCreateCommand</literal> 的子类。 "
+msgid "Each <literal>entity-command</literal> element specifies an entity generation implementation. The <literal>name</literal> attribute specifies a name that allows the command defined in an <literal>entity-commands</literal> section to be referenced in the defaults and entity elements. The <literal>class</literal> attribute specifies the implementation of the <literal>org.jboss.ejb.plugins.cmp.jdbc</literal>. <literal>JDBCCreateEntityCommand</literal> that supports the key generation. Database vendor specific commands typically subclass the <literal>org.jboss.ejb.plugins.cmp.jdbc</literal>. <literal>JDBCIdentityColumnCreateCommand</literal> if the database generates the primary key as a side effect of doing an insert, or the <literal>org.jboss.ejb.plugins.cmp.jdbc.JDBCInsertPKCreateCommand</literal> if the command must insert the generated key."
+msgstr "每个 <literal>entity-command</literal> 元素都指定了一个 entity 生成实现。<literal>name</literal> 属性指定的名称可以允许在 defaults 和 entity 元素里引用 <literal>entity-commands</literal> 部分定义的命令。<literal>class</literal> 属性指定支持键生成的  <literal>org.jboss.ejb.plugins.cmp.jdbc</literal>.<literal>JDBCCreateEntityCommand</literal> 的实现。如果数据库把生成主键当作插入的附属动作的话,数据库供应商专有的命令通常作为 <literal>org.jboss.ejb.plugins.cmp.jdbc</literal>.<literal>JDBCIdentityColumnCreateCommand</literal> 的子类,而如果命令必须插入生成的键时,它会作为 <literal>org.jboss.ejb.plugins.cmp.jdbc.JDBCInsertPKCreateCommand</literal> 的子类。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2432
 #, no-c-format
-msgid ""
-"The optional <literal>attribute</literal> element(s) allows for the "
-"specification of arbitrary name/value property pairs that will be available "
-"to the entity command implementation class. The <literal>attribute</literal> "
-"element has a required <literal>name</literal> attribute that specifies the "
-"name property, and the <literal>attribute</literal> element content is the "
-"value of the property. The attribute values are accessible through the "
-"<literal>org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityCommandMetaData."
-"getAttribute</literal>(String) method."
-msgstr ""
-"可选的 <literal>attribute</literal> 元素允许指定任意的 name/value 属性对来为 "
-"entity 命令实现所用。<literal>attribute</literal> 元素具有一个必需的指定名称"
-"的 <literal>name</literal> 属性且 <literal>attribute</literal> 元素的内容是这"
-"个属性的值。这个属性值可通过<literal>org.jboss.ejb.plugins.cmp.jdbc.metadata."
-"JDBCEntityCommandMetaData.getAttribute</literal>(String) 方法来访问。 "
+msgid "The optional <literal>attribute</literal> element(s) allows for the specification of arbitrary name/value property pairs that will be available to the entity command implementation class. The <literal>attribute</literal> element has a required <literal>name</literal> attribute that specifies the name property, and the <literal>attribute</literal> element content is the value of the property. The attribute values are accessible through the <literal>org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityCommandMetaData.getAttribute</literal>(String) method."
+msgstr "可选的 <literal>attribute</literal> 元素允许指定任意的 name/value 属性对来为 entity 命令实现所用。<literal>attribute</literal> 元素具有一个必需的指定名称的 <literal>name</literal> 属性且 <literal>attribute</literal> 元素的内容是这个属性的值。这个属性值可通过<literal>org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityCommandMetaData.getAttribute</literal>(String) 方法来访问。 "
 
 #. Tag: title
 #: The_CMP_Engine.xml:2436
@@ -8138,173 +5969,85 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2437
 #, no-c-format
-msgid ""
-"The following are the current <literal>entity-command</literal> definitions "
-"found in the <literal>standardjbosscmp-jdbc.xml</literal> descriptor:"
+msgid "The following are the current <literal>entity-command</literal> definitions found in the <literal>standardjbosscmp-jdbc.xml</literal> descriptor:"
 msgstr "下面是 <literal>standardjbosscmp-jdbc.xml</literal> 描述符里找到的当前 <literal>entity-command</literal> 定义:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2442
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">default</emphasis>: (<literal>org.jboss.ejb.plugins."
-"cmp.jdbc.JDBCCreateEntityCommand</literal>) The "
-"<literal>JDBCCreateEntityCommand</literal> is the default entity creation as "
-"it is the <literal>entity-command</literal> referenced in the "
-"<literal>standardjbosscmp-jdbc.xml</literal> defaults element. This entity-"
-"command executes an <literal>INSERT INTO</literal> query using the assigned "
-"primary key value."
+msgid "<emphasis role=\"bold\">default</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand</literal>) The <literal>JDBCCreateEntityCommand</literal> is the default entity creation as it is the <literal>entity-command</literal> referenced in the <literal>standardjbosscmp-jdbc.xml</literal> defaults element. This entity-command executes an <literal>INSERT INTO</literal> query using the assigned primary key value."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2447
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">no-select-before-insert</emphasis>: (<literal>org."
-"jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand</literal>) This is a "
-"variation on <literal>default</literal> that skips select before insert by "
-"specifying an attribute <literal>name=\"SQLExceptionProcessor\"</literal> "
-"that points to the <literal>jboss.jdbc:service=SQLExceptionProcessor</"
-"literal> service. The <literal>SQLExceptionProcessor</literal> service "
-"provides a <literal>boolean isDuplicateKey(SQLException e)</literal> "
-"operation that allows a for determination of any unique constraint violation."
+msgid "<emphasis role=\"bold\">no-select-before-insert</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand</literal>) This is a variation on <literal>default</literal> that skips select before insert by specifying an attribute <literal>name=\"SQLExceptionProcessor\"</literal> that points to the <literal>jboss.jdbc:service=SQLExceptionProcessor</literal> service. The <literal>SQLExceptionProcessor</literal> service provides a <literal>boolean isDuplicateKey(SQLException e)</literal> operation that allows a for determination of any unique constraint violation."
 msgstr "<emphasis role=\"bold\"></emphasis><literal></literal><literal></literal><literal> 名字</literal><literal></literal><literal></literal><literal></literal>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2452
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">pk-sql</emphasis> (<literal>org.jboss.ejb.plugins."
-"cmp.jdbc.keygen.JDBCPkSqlCreateCommand</literal>) The "
-"<literal>JDBCPkSqlCreateCommand</literal> executes an <literal>INSERT INTO</"
-"literal> query statement provided by the <literal>pk-sql</literal> attribute "
-"to obtain the next primary key value. Its primary target usage are databases "
-"with sequence support."
+msgid "<emphasis role=\"bold\">pk-sql</emphasis> (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCPkSqlCreateCommand</literal>) The <literal>JDBCPkSqlCreateCommand</literal> executes an <literal>INSERT INTO</literal> query statement provided by the <literal>pk-sql</literal> attribute to obtain the next primary key value. Its primary target usage are databases with sequence support."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2457
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mysql-get-generated-keys</emphasis>: (<literal>org."
-"jboss.ejb.plugins.cmp.jdbc.keygen.JDBCMySQLCreateCommand</literal>) The "
-"<literal>JDBCMySQLCreateCommand</literal> executes an <literal>INSERT INTO</"
-"literal> query using the <literal>getGeneratedKeys</literal> method from "
-"MySQL native <literal>java.sql.Statement</literal> interface implementation "
-"to fetch the generated key."
+msgid "<emphasis role=\"bold\">mysql-get-generated-keys</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCMySQLCreateCommand</literal>) The <literal>JDBCMySQLCreateCommand</literal> executes an <literal>INSERT INTO</literal> query using the <literal>getGeneratedKeys</literal> method from MySQL native <literal>java.sql.Statement</literal> interface implementation to fetch the generated key."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2462
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">oracle-sequence</emphasis>: (<literal>org.jboss.ejb."
-"plugins.cmp.jdbc.keygen.JDBCOracleCreateCommand</literal>) The "
-"<literal>JDBCOracleCreateCommand</literal> is a create command for use with "
-"Oracle that uses a sequence in conjunction with a <literal>RETURNING</"
-"literal> clause to generate keys in a single statement. It has a required "
-"<literal>sequence</literal> element that specifies the name of the sequence "
-"column."
+msgid "<emphasis role=\"bold\">oracle-sequence</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCOracleCreateCommand</literal>) The <literal>JDBCOracleCreateCommand</literal> is a create command for use with Oracle that uses a sequence in conjunction with a <literal>RETURNING</literal> clause to generate keys in a single statement. It has a required <literal>sequence</literal> element that specifies the name of the sequence column."
 msgstr "<emphasis role=\"bold\"></emphasis><literal></literal><literal></literal><literal></literal><literal></literal> 名字."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2467
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">hsqldb-fetch-key</emphasis>: (<literal>org.jboss.ejb."
-"plugins.cmp.jdbc.keygen.JDBCHsqldbCreateCommand</literal>) The "
-"<literal>JDBCHsqldbCreateCommand</literal> executes an <literal>INSERT INTO</"
-"literal> query after executing a <literal>CALL IDENTITY()</literal> "
-"statement to fetch the generated key."
+msgid "<emphasis role=\"bold\">hsqldb-fetch-key</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCHsqldbCreateCommand</literal>) The <literal>JDBCHsqldbCreateCommand</literal> executes an <literal>INSERT INTO</literal> query after executing a <literal>CALL IDENTITY()</literal> statement to fetch the generated key."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2472
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">sybase-fetch-key</emphasis>: (<literal>org.jboss.ejb."
-"plugins.cmp.jdbc.keygen.JDBCSybaseCreateCommand</literal>) The "
-"<literal>JDBCSybaseCreateCommand</literal> executes an <literal>INSERT</"
-"literal> INTO query after executing a <literal>SELECT @@IDENTITY</literal> "
-"statement to fetch the generated key."
+msgid "<emphasis role=\"bold\">sybase-fetch-key</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCSybaseCreateCommand</literal>) The <literal>JDBCSybaseCreateCommand</literal> executes an <literal>INSERT</literal> INTO query after executing a <literal>SELECT @@IDENTITY</literal> statement to fetch the generated key."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2477
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mssql-fetch-key</emphasis>: (<literal>org.jboss.ejb."
-"plugins.cmp.jdbc.keygen.JDBCSQLServerCreateCommand</literal>) The "
-"<literal>JDBCSQLServerCreateCommand</literal> for Microsoft SQL Server that "
-"uses the value from an <literal>IDENTITY</literal> columns. By default uses "
-"<literal>SELECT SCOPE_IDENTITY()</literal> to reduce the impact of triggers; "
-"can be overridden with <literal>pk-sql</literal> attribute e.g. for V7."
+msgid "<emphasis role=\"bold\">mssql-fetch-key</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCSQLServerCreateCommand</literal>) The <literal>JDBCSQLServerCreateCommand</literal> for Microsoft SQL Server that uses the value from an <literal>IDENTITY</literal> columns. By default uses <literal>SELECT SCOPE_IDENTITY()</literal> to reduce the impact of triggers; can be overridden with <literal>pk-sql</literal> attribute e.g. for V7."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2482
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">informix-serial</emphasis>: (<literal>org.jboss.ejb."
-"plugins.cmp.jdbc.keygen.JDBCInformixCreateCommand</literal>) The "
-"<literal>JDBCInformixCreateCommand</literal> executes an <literal>INSERT</"
-"literal> INTO query after using the <literal>getSerial</literal> method from "
-"Informix native <literal>java.sql.Statement</literal> interface "
-"implementation to fetch the generated key."
+msgid "<emphasis role=\"bold\">informix-serial</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCInformixCreateCommand</literal>) The <literal>JDBCInformixCreateCommand</literal> executes an <literal>INSERT</literal> INTO query after using the <literal>getSerial</literal> method from Informix native <literal>java.sql.Statement</literal> interface implementation to fetch the generated key."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2487
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">postgresql-fetch-seq</emphasis>: (<literal>org.jboss."
-"ejb.plugins.cmp.jdbc.keygen.JDBCPostgreSQLCreateCommand</literal>) The "
-"<literal>JDBCPostgreSQLCreateCommand</literal> for PostgreSQL that fetches "
-"the current value of the sequence. The optional <literal>sequence</literal> "
-"attribute can be used to change the name of the sequence, with the default "
-"being <literal>table_pkColumn_seq</literal>."
+msgid "<emphasis role=\"bold\">postgresql-fetch-seq</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCPostgreSQLCreateCommand</literal>) The <literal>JDBCPostgreSQLCreateCommand</literal> for PostgreSQL that fetches the current value of the sequence. The optional <literal>sequence</literal> attribute can be used to change the name of the sequence, with the default being <literal>table_pkColumn_seq</literal>."
 msgstr "<emphasis role=\"bold\"></emphasis><literal></literal><literal></literal><literal></literal> 名字<literal></literal>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2492
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">key-generator</emphasis>: (<literal>org.jboss.ejb."
-"plugins.cmp.jdbc.keygen.JDBCKeyGeneratorCreateCommand</literal>) The "
-"<literal>JDBCKeyGeneratorCreateCommand</literal> executes an <literal>INSERT "
-"INTO</literal> query after obtaining a value for the primary key from the "
-"key generator referenced by the <literal>key-generator-factory</literal>. "
-"The <literal>key-generator-factory</literal> attribute must provide the name "
-"of a JNDI binding of the <literal>org.jboss.ejb.plugins.keygenerator."
-"KeyGeneratorFactory</literal> implementation."
+msgid "<emphasis role=\"bold\">key-generator</emphasis>: (<literal>org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCKeyGeneratorCreateCommand</literal>) The <literal>JDBCKeyGeneratorCreateCommand</literal> executes an <literal>INSERT INTO</literal> query after obtaining a value for the primary key from the key generator referenced by the <literal>key-generator-factory</literal>. The <literal>key-generator-factory</literal> attribute must provide the name of a JNDI binding of the <literal>org.jboss.ejb.plugins.keygenerator.KeyGeneratorFactory</literal> implementation."
 msgstr "<emphasis role=\"bold\"></emphasis><literal></literal><literal></literal><literal></literal><literal></literal><literal></literal> 名字<literal></literal>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2497
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">get-generated-keys</emphasis>: (org.jboss.ejb."
-"plugins.cmp.jdbc.jdbc3.JDBCGetGeneratedKeysCreateCommand) The "
-"<literal>JDBCGetGeneratedKeysCreateCommand</literal> executes an "
-"<literal>INSERT INTO</literal> query using a statement built using the JDBC3 "
-"<literal>prepareStatement(String, Statement.RETURN_GENERATED_KEYS)</literal> "
-"that has the capability to retrieve the auto-generated key. The generated "
-"key is obtained by calling the <literal>PreparedStatement.getGeneratedKeys</"
-"literal> method. Since this requires JDBC3 support it is only available in "
-"JDK1.4.1+ with a supporting JDBC driver."
+msgid "<emphasis role=\"bold\">get-generated-keys</emphasis>: (org.jboss.ejb.plugins.cmp.jdbc.jdbc3.JDBCGetGeneratedKeysCreateCommand) The <literal>JDBCGetGeneratedKeysCreateCommand</literal> executes an <literal>INSERT INTO</literal> query using a statement built using the JDBC3 <literal>prepareStatement(String, Statement.RETURN_GENERATED_KEYS)</literal> that has the capability to retrieve the auto-generated key. The generated key is obtained by calling the <literal>PreparedStatement.getGeneratedKeys</literal> method. Since this requires JDBC3 support it is only available in JDK1.4.1+ with a supporting JDBC driver."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2502
 #, no-c-format
-msgid ""
-"An example configuration using the <literal>hsqldb-fetch-key</"
-"literal><literal>entity-command</literal> with the generated key mapped to a "
-"known primary key <literal>cmp-field</literal> is shown below."
+msgid "An example configuration using the <literal>hsqldb-fetch-key</literal><literal>entity-command</literal> with the generated key mapped to a known primary key <literal>cmp-field</literal> is shown below."
 msgstr ""
 
 #. Tag: programlisting
@@ -8352,9 +6095,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2506
 #, no-c-format
-msgid ""
-"An alternate example using an unknown primary key without an explicit "
-"<literal>cmp-field</literal> is shown below."
+msgid "An alternate example using an unknown primary key without an explicit <literal>cmp-field</literal> is shown below."
 msgstr ""
 
 #. Tag: programlisting
@@ -8368,8 +6109,7 @@
 "            &lt;pk-constraint&gt;false&lt;/pk-constraint&gt;\n"
 "            &lt;table-name&gt;location&lt;/table-name&gt;\n"
 "            &lt;unknown-pk&gt;\n"
-"                &lt;unknown-pk-class&gt;java.lang.Integer&lt;/unknown-pk-"
-"class&gt;\n"
+"                &lt;unknown-pk-class&gt;java.lang.Integer&lt;/unknown-pk-class&gt;\n"
 "                &lt;field-name&gt;locationID&lt;/field-name&gt;\n"
 "                &lt;column-name&gt;id&lt;/column-name&gt;\n"
 "                &lt;jdbc-type&gt;INTEGER&lt;/jdbc-type&gt;\n"
@@ -8389,8 +6129,7 @@
 "            &lt;pk-constraint&gt;false&lt;/pk-constraint&gt;\n"
 "            &lt;table-name&gt;location&lt;/table-name&gt;\n"
 "            &lt;unknown-pk&gt;\n"
-"                &lt;unknown-pk-class&gt;java.lang.Integer&lt;/unknown-pk-"
-"class&gt;\n"
+"                &lt;unknown-pk-class&gt;java.lang.Integer&lt;/unknown-pk-class&gt;\n"
 "                &lt;field-name&gt;locationID&lt;/field-name&gt;\n"
 "                &lt;column-name&gt;id&lt;/column-name&gt;\n"
 "                &lt;jdbc-type&gt;INTEGER&lt;/jdbc-type&gt;\n"
@@ -8412,14 +6151,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2516
 #, no-c-format
-#, fuzzy
-msgid ""
-"JBoss global defaults are defined in the <literal>standardjbosscmp-jdbc.xml</"
-"literal> file of the <literal>server/&lt;server-name&gt;/conf/</literal> "
-"directory. Each application can override the global defaults in the "
-"<literal>jbosscmp-jdbc.xml</literal> file. The default options are contained "
-"in a defaults element of the configuration file, and the content model is "
-"shown below."
+msgid "JBoss global defaults are defined in the <literal>standardjbosscmp-jdbc.xml</literal> file of the <literal>server/&lt;server-name&gt;/conf/</literal> directory. Each application can override the global defaults in the <literal>jbosscmp-jdbc.xml</literal> file. The default options are contained in a defaults element of the configuration file, and the content model is shown below."
 msgstr "<literal></literal><literal>&lt; 名字&gt;</literal><literal></literal>."
 
 #. Tag: title
@@ -8449,8 +6181,7 @@
 "        &lt;pk-constraint&gt;true&lt;/pk-constraint&gt;\n"
 "        &lt;fk-constraint&gt;false&lt;/fk-constraint&gt;\n"
 "        &lt;row-locking&gt;false&lt;/row-locking&gt;\n"
-"        &lt;preferred-relation-mapping&gt;foreign-key&lt;/preferred-relation-"
-"mapping&gt;\n"
+"        &lt;preferred-relation-mapping&gt;foreign-key&lt;/preferred-relation-mapping&gt;\n"
 "        &lt;read-ahead&gt;\n"
 "            &lt;strategy&gt;on-load&lt;/strategy&gt;\n"
 "            &lt;page-size&gt;1000&lt;/page-size&gt;\n"
@@ -8471,8 +6202,7 @@
 "        &lt;pk-constraint&gt;true&lt;/pk-constraint&gt;\n"
 "        &lt;fk-constraint&gt;false&lt;/fk-constraint&gt;\n"
 "        &lt;row-locking&gt;false&lt;/row-locking&gt;\n"
-"        &lt;preferred-relation-mapping&gt;foreign-key&lt;/preferred-relation-"
-"mapping&gt;\n"
+"        &lt;preferred-relation-mapping&gt;foreign-key&lt;/preferred-relation-mapping&gt;\n"
 "        &lt;read-ahead&gt;\n"
 "            &lt;strategy&gt;on-load&lt;/strategy&gt;\n"
 "            &lt;page-size&gt;1000&lt;/page-size&gt;\n"
@@ -8491,208 +6221,103 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2533
 #, no-c-format
-msgid ""
-"Each option can apply to entities, relationships, or both, and can be "
-"overridden in the specific entity or relationship. A detailed description of "
-"each option follows:"
+msgid "Each option can apply to entities, relationships, or both, and can be overridden in the specific entity or relationship. A detailed description of each option follows:"
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2538
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">datasource</emphasis>: This optional element is the "
-"<literal>jndi-name</literal> used to look up the datasource. All database "
-"connections used by an entity or <literal>relation-table</literal> are "
-"obtained from the datasource. Having different datasources for entities is "
-"not recommended, as it vastly constrains the domain over which finders and "
-"ejbSelects can query."
+msgid "<emphasis role=\"bold\">datasource</emphasis>: This optional element is the <literal>jndi-name</literal> used to look up the datasource. All database connections used by an entity or <literal>relation-table</literal> are obtained from the datasource. Having different datasources for entities is not recommended, as it vastly constrains the domain over which finders and ejbSelects can query."
 msgstr "<emphasis role=\"bold\"></emphasis><literal> 名字</literal><literal></literal>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2543
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">datasource-mapping</emphasis>: This optional element "
-"specifies the name of the <literal>type-mapping</literal>, which determines "
-"how Java types are mapped to SQL types, and how EJB-QL functions are mapped "
-"to database specific functions. Type mappings are discussed in <xref linkend="
-"\"Datasource_Customization-Mapping\"/>."
+msgid "<emphasis role=\"bold\">datasource-mapping</emphasis>: This optional element specifies the name of the <literal>type-mapping</literal>, which determines how Java types are mapped to SQL types, and how EJB-QL functions are mapped to database specific functions. Type mappings are discussed in <xref linkend=\"Datasource_Customization-Mapping\"/>."
 msgstr "<emphasis role=\"bold\"></emphasis> 名字<literal></literal><xref linkend=\"Datasource_Customization-Mapping\"/>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2548
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">create-table</emphasis>: This optional element when "
-"true, specifies that JBoss should attempt to create a table for the entity. "
-"When the application is deployed, JBoss checks if a table already exists "
-"before creating the table. If a table is found, it is logged, and the table "
-"is not created. This option is very useful during the early stages of "
-"development when the table structure changes often. The default is false."
+msgid "<emphasis role=\"bold\">create-table</emphasis>: This optional element when true, specifies that JBoss should attempt to create a table for the entity. When the application is deployed, JBoss checks if a table already exists before creating the table. If a table is found, it is logged, and the table is not created. This option is very useful during the early stages of development when the table structure changes often. The default is false."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2575
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">remove-table</emphasis>: This optional element when "
-"true, JBoss will attempt to drop the table for each entity and each relation "
-"table mapped relationship. When the application is undeployed, JBoss will "
-"attempt to drop the table. This option is very useful during the early "
-"stages of development when the table structure changes often. The default is "
-"false."
+msgid "<emphasis role=\"bold\">remove-table</emphasis>: This optional element when true, JBoss will attempt to drop the table for each entity and each relation table mapped relationship. When the application is undeployed, JBoss will attempt to drop the table. This option is very useful during the early stages of development when the table structure changes often. The default is false."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2580
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-only</emphasis>: This optional element when "
-"true specifies that the bean provider will not be allowed to change the "
-"value of any fields. A field that is read-only will not be stored in, or "
-"inserted into, the database. If a primary key field is read-only, the create "
-"method will throw a <literal>CreateException</literal>. If a set accessor is "
-"called on a <literal>read-only</literal> field, it throws an "
-"<literal>EJBException</literal>. Read only fields are useful for fields that "
-"are filled in by database triggers, such as last update. The <literal>read-"
-"only</literal> option can be overridden on a per field basis. The default is "
-"false."
+msgid "<emphasis role=\"bold\">read-only</emphasis>: This optional element when true specifies that the bean provider will not be allowed to change the value of any fields. A field that is read-only will not be stored in, or inserted into, the database. If a primary key field is read-only, the create method will throw a <literal>CreateException</literal>. If a set accessor is called on a <literal>read-only</literal> field, it throws an <literal>EJBException</literal>. Read only fields are useful for fields that are filled in by database triggers, such as last update. The <literal>read-only</literal> option can be overridden on a per field basis. The default is false."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2585
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">read-time-out</emphasis>: This optional element is "
-"the amount of time in milliseconds that a read on a read only field is "
-"valid. A value of 0 means that the value is always reloaded at the start of "
-"a transaction, and a value of -1 means that the value never times out. This "
-"option can also be overridden on a per CMP field basis. If <literal>read-"
-"only</literal> is false, this value is ignored. The default is -1."
+msgid "<emphasis role=\"bold\">read-time-out</emphasis>: This optional element is the amount of time in milliseconds that a read on a read only field is valid. A value of 0 means that the value is always reloaded at the start of a transaction, and a value of -1 means that the value never times out. This option can also be overridden on a per CMP field basis. If <literal>read-only</literal> is false, this value is ignored. The default is -1."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2590
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">row-locking</emphasis>: This optional element if "
-"true specifies that JBoss will lock all rows loaded in a transaction. Most "
-"databases implement this by using the <literal>SELECT FOR UPDATE</literal> "
-"syntax when loading the entity, but the actual syntax is determined by the "
-"<literal>row-locking-template</literal> in the <literal>datasource-mapping</"
-"literal> used by this entity. The default is false."
+msgid "<emphasis role=\"bold\">row-locking</emphasis>: This optional element if true specifies that JBoss will lock all rows loaded in a transaction. Most databases implement this by using the <literal>SELECT FOR UPDATE</literal> syntax when loading the entity, but the actual syntax is determined by the <literal>row-locking-template</literal> in the <literal>datasource-mapping</literal> used by this entity. The default is false."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2595
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">pk-constraint</emphasis>: This optional element if "
-"true specifies that JBoss will add a primary key constraint when creating "
-"tables. The default is true."
-msgstr ""
-"<emphasis role=\"bold\">cookies</emphasis>:这个标记表示是否用 cookies 记录会"
-"话。它的缺省值是 true。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">pk-constraint</emphasis>: This optional element if true specifies that JBoss will add a primary key constraint when creating tables. The default is true."
+msgstr "<emphasis role=\"bold\">pk-constraint</emphasis>:这个可选元素为 true 表示 JBoss 将在创建表时添加主键。它的缺省值是 true。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2600
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">preferred-relation-mapping</emphasis>: This optional "
-"element specifies the preferred mapping style for relationships. The "
-"<literal>preferred-relation-mapping</literal> element must be either "
-"<literal>foreign-key</literal> or <literal>relation-table</literal>."
-msgstr ""
-"<emphasis role=\"bold\">persistPeriod</emphasis>:如果"
-"<literal>perisitPolicy</literal>属性是<literal>NoMoreOftenThan</literal> 或"
-"者 <literal>OnTimer</literal>,<literal>persistPeriod</literal>属性指定更新的"
-"频率(毫秒)。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">preferred-relation-mapping</emphasis>: This optional element specifies the preferred mapping style for relationships. The <literal>preferred-relation-mapping</literal> element must be either <literal>foreign-key</literal> or <literal>relation-table</literal>."
+msgstr "<emphasis role=\"bold\">preferred-relation-mapping</emphasis>:这个可选元素指定关系的首选映射风格。<literal>preferred-relation-mapping</literal> 元素必须是 <literal>foreign-key</literal> 或 <literal>relation-table</literal>。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2605
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">read-ahead</emphasis>: This optional element "
-"controls caching of query results and CMR fields for the entity. This option "
-"is discussed in <xref linkend=\"Optimized_Loading-Read_ahead\"/>."
-msgstr ""
-"<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集(参"
-"看 <xref linkend=\"jbosscache-jgroups\"/>)指定 JGroup 配置选项的元素"
-"(element)。"
+msgid "<emphasis role=\"bold\">read-ahead</emphasis>: This optional element controls caching of query results and CMR fields for the entity. This option is discussed in <xref linkend=\"Optimized_Loading-Read_ahead\"/>."
+msgstr "<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集(参看 <xref linkend=\"jbosscache-jgroups\"/>)指定 JGroup 配置选项的元素(element)。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2610
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">list-cache-max</emphasis>: This optional element "
-"specifies the number of <literal>read-lists</literal> that can be tracked by "
-"this entity. This option is discussed in <xref linkend=\"Read_ahead-on_load"
-"\"/>. The default is 1000."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>:这个元素指定操作的易读的描"
-"述。"
+msgid "<emphasis role=\"bold\">list-cache-max</emphasis>: This optional element specifies the number of <literal>read-lists</literal> that can be tracked by this entity. This option is discussed in <xref linkend=\"Read_ahead-on_load\"/>. The default is 1000."
+msgstr "<emphasis role=\"bold\">description</emphasis>:这个元素指定操作的易读的描述。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2620
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">fetch-size</emphasis>: This optional element "
-"specifies the number of entities to read in one round-trip to the underlying "
-"datastore. The default is 0."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>:这个元素指定操作的易读的描"
-"述。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">fetch-size</emphasis>: This optional element specifies the number of entities to read in one round-trip to the underlying datastore. The default is 0."
+msgstr "<emphasis role=\"bold\">description</emphasis>:这个可选元素指定对底层数据库一次读取的实体数目。它的缺省值为 0。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2625
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">unknown-pk</emphasis>: This optional element allows "
-"one to define the default mapping of an unknown primary key type of "
-"<literal>java.lang.Object</literal> maps to the persistent store."
+msgid "<emphasis role=\"bold\">unknown-pk</emphasis>: This optional element allows one to define the default mapping of an unknown primary key type of <literal>java.lang.Object</literal> maps to the persistent store."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2630
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">entity-command</emphasis>: This optional element "
-"allows one to define the default command for entity creation. This is "
-"described in detail in <xref linkend=\"The_CMP_Engine-"
-"Entity_Commands_and_Primary_Key_Generation\"/>."
-msgstr ""
-"<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集(参"
-"看 <xref linkend=\"jbosscache-jgroups\"/>)指定 JGroup 配置选项的元素"
-"(element)。"
+msgid "<emphasis role=\"bold\">entity-command</emphasis>: This optional element allows one to define the default command for entity creation. This is described in detail in <xref linkend=\"The_CMP_Engine-Entity_Commands_and_Primary_Key_Generation\"/>."
+msgstr "<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集(参看 <xref linkend=\"jbosscache-jgroups\"/>)指定 JGroup 配置选项的元素(element)。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2635
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">ql-compiler</emphasis>: This optional elements "
-"allows a replacement query compiler to be specified. Alternate query "
-"compilers were discussed in <xref linkend=\"Queries-"
-"EJBQL_2.1_and_SQL92_queries\"/>."
-msgstr ""
-"<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集(参"
-"看 <xref linkend=\"jbosscache-jgroups\"/>)指定 JGroup 配置选项的元素"
-"(element)。"
+msgid "<emphasis role=\"bold\">ql-compiler</emphasis>: This optional elements allows a replacement query compiler to be specified. Alternate query compilers were discussed in <xref linkend=\"Queries-EJBQL_2.1_and_SQL92_queries\"/>."
+msgstr "<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集(参看 <xref linkend=\"jbosscache-jgroups\"/>)指定 JGroup 配置选项的元素(element)。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2640
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">throw-runtime-exceptions</emphasis>: This attribute, "
-"if set to true, indicates that an error in connecting to the database should "
-"be seen in the application as runtime <literal>EJBException</literal> rather "
-"than as a checked exception."
+msgid "<emphasis role=\"bold\">throw-runtime-exceptions</emphasis>: This attribute, if set to true, indicates that an error in connecting to the database should be seen in the application as runtime <literal>EJBException</literal> rather than as a checked exception."
 msgstr ""
 
 #. Tag: title
@@ -8704,15 +6329,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2651
 #, no-c-format
-msgid ""
-"JBoss includes predefined type-mappings for many databases including: "
-"Cloudscape, DB2, DB2/400, Hypersonic SQL, InformixDB, InterBase, MS "
-"SQLSERVER, MS SQLSERVER2000, mySQL, Oracle7, Oracle8, Oracle9i, PointBase, "
-"PostgreSQL, PostgreSQL 7.2, SapDB, SOLID, and Sybase. If you do not like the "
-"supplied mapping, or a mapping is not supplied for your database, you will "
-"have to define a new mapping. If you find an error in one of the supplied "
-"mappings, or if you create a new mapping for a new database, please consider "
-"posting a patch at the JBoss project page on SourceForge."
+msgid "JBoss includes predefined type-mappings for many databases including: Cloudscape, DB2, DB2/400, Hypersonic SQL, InformixDB, InterBase, MS SQLSERVER, MS SQLSERVER2000, mySQL, Oracle7, Oracle8, Oracle9i, PointBase, PostgreSQL, PostgreSQL 7.2, SapDB, SOLID, and Sybase. If you do not like the supplied mapping, or a mapping is not supplied for your database, you will have to define a new mapping. If you find an error in one of the supplied mappings, or if you create a new mapping for a new database, please consider posting a patch at the JBoss project page on SourceForge."
 msgstr ""
 
 #. Tag: title
@@ -8724,11 +6341,7 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2656
 #, no-c-format
-msgid ""
-"Customization of a database is done through the <literal>type-mapping</"
-"literal> section of the <literal>jbosscmp-jdbc.xml</literal> descriptor. The "
-"content model for the type-mapping element is given in <xref linkend="
-"\"Type_Mapping-The_jbosscmp_jdbc_type_mapping_element_content_model.\"/>."
+msgid "Customization of a database is done through the <literal>type-mapping</literal> section of the <literal>jbosscmp-jdbc.xml</literal> descriptor. The content model for the type-mapping element is given in <xref linkend=\"Type_Mapping-The_jbosscmp_jdbc_type_mapping_element_content_model.\"/>."
 msgstr ""
 
 #. Tag: title
@@ -8739,35 +6352,25 @@
 
 #. Tag: para
 #: The_CMP_Engine.xml:2669
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The elements are:"
 msgstr "子元素是:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2674
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">name</emphasis>: This required element provides the "
-"name identifying the database customization. It is used to refer to the "
-"mapping by the <literal>datasource-mapping</literal> elements found in "
-"defaults and entity."
+msgid "<emphasis role=\"bold\">name</emphasis>: This required element provides the name identifying the database customization. It is used to refer to the mapping by the <literal>datasource-mapping</literal> elements found in defaults and entity."
 msgstr "<emphasis role=\"bold\"> 名字</emphasis> 名字<literal></literal>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2679
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">row-locking-template</emphasis>: This required "
-"element gives the <literal>PreparedStatement</literal> template used to "
-"create a row lock on the selected rows. The template must support three "
-"arguments:"
+msgid "<emphasis role=\"bold\">row-locking-template</emphasis>: This required element gives the <literal>PreparedStatement</literal> template used to create a row lock on the selected rows. The template must support three arguments:"
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2684
 #, no-c-format
-#, fuzzy
 msgid "the select clause"
 msgstr "select 子句"
 
@@ -8775,95 +6378,71 @@
 #: The_CMP_Engine.xml:2689
 #, no-c-format
 msgid "the from clause. The order of the tables is currently not guaranteed"
-msgstr ""
+msgstr "from 子句。目前不能保证表的顺序"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2694
 #, no-c-format
-#, fuzzy
 msgid "the where clause"
 msgstr "where 子句"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2699
 #, no-c-format
-msgid ""
-"If row locking is not supported in select statement this element should be "
-"empty. The most common form of row locking is select for update as in: "
-"<literal>SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE</literal>."
-msgstr ""
+msgid "If row locking is not supported in select statement this element should be empty. The most common form of row locking is select for update as in: <literal>SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE</literal>."
+msgstr "如果 select 语句里不支持行锁定,这个元素应该为空。行锁定最常见的形式是:<literal>SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE</literal>。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2704
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">pk-constraint-template</emphasis>: This required "
-"element gives the <literal>PreparedStatement</literal> template used to "
-"create a primary key constraint in the create table statement. The template "
-"must support two arguments"
+msgid "<emphasis role=\"bold\">pk-constraint-template</emphasis>: This required element gives the <literal>PreparedStatement</literal> template used to create a primary key constraint in the create table statement. The template must support two arguments"
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2709
 #, no-c-format
-#, fuzzy
-msgid ""
-"Primary key constraint name; which is always <literal>pk_{table-name}</"
-"literal>"
+msgid "Primary key constraint name; which is always <literal>pk_{table-name}</literal>"
 msgstr "名字<literal> 名字</literal>"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2714
 #, no-c-format
 msgid "Comma separated list of primary key column names"
-msgstr ""
+msgstr "以逗号隔开的主键字段名列表"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2719
 #, no-c-format
-msgid ""
-"If a primary key constraint clause is not supported in a create table "
-"statement this element should be empty. The most common form of a primary "
-"key constraint is: <literal>CONSTRAINT ?1 PRIMARY KEY (?2)</literal>"
-msgstr ""
+msgid "If a primary key constraint clause is not supported in a create table statement this element should be empty. The most common form of a primary key constraint is: <literal>CONSTRAINT ?1 PRIMARY KEY (?2)</literal>"
+msgstr "如果 create table 语句里不支持主键约束子句,那么这个元素应该为空。主键约束最常见的形式是:<literal>CONSTRAINT ?1 PRIMARY KEY (?2)</literal>"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2724
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">fk-constraint-template</emphasis>: This is the "
-"template used to create a foreign key constraint in separate statement. The "
-"template must support five arguments:"
-msgstr ""
-"<emphasis role=\"bold\">SessionIdAlphabet</emphasis>:这是一个用来创建会话 "
-"ID 的字符集。它必须由刚好 65 个唯一的字符组成."
+#, no-c-format
+msgid "<emphasis role=\"bold\">fk-constraint-template</emphasis>: This is the template used to create a foreign key constraint in separate statement. The template must support five arguments:"
+msgstr "<emphasis role=\"bold\">fk-constraint-template</emphasis>:这是用来在单独语句里创建外键约束的模板。这个模板必须支持 5 个参数:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2729
 #, no-c-format
-#, fuzzy
 msgid "Table name"
 msgstr "名字"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2734
 #, no-c-format
-#, fuzzy
-msgid ""
-"Foreign key constraint name; which is always <literal>fk_{table-name}_{cmr-"
-"field-name}</literal>"
+msgid "Foreign key constraint name; which is always <literal>fk_{table-name}_{cmr-field-name}</literal>"
 msgstr "名字<literal> 名字 名字</literal>"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2739
 #, no-c-format
 msgid "Comma separated list of foreign key column names"
-msgstr ""
+msgstr "以逗号隔开的外键字段名的列表"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2744
 #, no-c-format
-#, fuzzy
 msgid "References table name"
 msgstr "名字"
 
@@ -8871,167 +6450,112 @@
 #: The_CMP_Engine.xml:2749
 #, no-c-format
 msgid "Comma separated list of the referenced primary key column names"
-msgstr ""
+msgstr "以逗号隔开的被引用主键字段名的列表"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2754
 #, no-c-format
-msgid ""
-"If the datasource does not support foreign key constraints this element "
-"should be empty. The most common form of a foreign key constraint is: "
-"<literal>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)"
-"</literal>."
-msgstr ""
+msgid "If the datasource does not support foreign key constraints this element should be empty. The most common form of a foreign key constraint is: <literal>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</literal>."
+msgstr "如果数据源不支持外键约束,这个元素应该为空。外键约束最常见的形式是:<literal>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</literal>。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2759
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">auto-increment-template</emphasis>: This declares "
-"the SQL template for specifying auto increment columns."
-msgstr "<emphasis role=\"bold\">parameter</emphasis>:这个元素描述了操作的签名。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">auto-increment-template</emphasis>: This declares the SQL template for specifying auto increment columns."
+msgstr "<emphasis role=\"bold\">auto-increment-template</emphasis>:这声明了 SQL 模板来指定自动增量(auto increment)的字段。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2764
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">add-column-template</emphasis>: When <literal>alter-"
-"table</literal> is true, this SQL template specifies the syntax for adding a "
-"column to an existing table. The default value is <literal>ALTER TABLE ?1 "
-"ADD ?2 ?3</literal>. The parameters are:"
+msgid "<emphasis role=\"bold\">add-column-template</emphasis>: When <literal>alter-table</literal> is true, this SQL template specifies the syntax for adding a column to an existing table. The default value is <literal>ALTER TABLE ?1 ADD ?2 ?3</literal>. The parameters are:"
 msgstr ""
 
 #. Tag: para
-#: The_CMP_Engine.xml:2769 The_CMP_Engine.xml:2791 The_CMP_Engine.xml:2813
+#: The_CMP_Engine.xml:2769
+#: The_CMP_Engine.xml:2791
+#: The_CMP_Engine.xml:2813
 #, no-c-format
-#, fuzzy
 msgid "the table name"
 msgstr "名字"
 
 #. Tag: para
-#: The_CMP_Engine.xml:2774 The_CMP_Engine.xml:2796 The_CMP_Engine.xml:2818
+#: The_CMP_Engine.xml:2774
+#: The_CMP_Engine.xml:2796
+#: The_CMP_Engine.xml:2818
 #, no-c-format
-#, fuzzy
 msgid "the column name"
 msgstr "SQL 字段类型"
 
 #. Tag: para
-#: The_CMP_Engine.xml:2779 The_CMP_Engine.xml:2801
+#: The_CMP_Engine.xml:2779
+#: The_CMP_Engine.xml:2801
 #, no-c-format
-#, fuzzy
 msgid "the column type"
 msgstr "SQL 字段类型"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2786
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">alter-column-template</emphasis>: When "
-"<literal>alter-table</literal> is true, this SQL template specifies the "
-"syntax for dropping a column to from an existing table. The default value is "
-"<literal>ALTER TABLE ?1 ALTER ?2 TYPE ?3</literal>. The parameters are:"
+msgid "<emphasis role=\"bold\">alter-column-template</emphasis>: When <literal>alter-table</literal> is true, this SQL template specifies the syntax for dropping a column to from an existing table. The default value is <literal>ALTER TABLE ?1 ALTER ?2 TYPE ?3</literal>. The parameters are:"
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2808
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">drop-column-template</emphasis>: When <literal>alter-"
-"table</literal> is true, this SQL template specifies the syntax for dropping "
-"a column to from an existing table. The default value is <literal>ALTER "
-"TABLE ?1 DROP ?2</literal>. The parameters are:"
+msgid "<emphasis role=\"bold\">drop-column-template</emphasis>: When <literal>alter-table</literal> is true, this SQL template specifies the syntax for dropping a column to from an existing table. The default value is <literal>ALTER TABLE ?1 DROP ?2</literal>. The parameters are:"
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2825
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">alias-header-prefix</emphasis>: This required "
-"element gives the prefix used in creating the alias header. An alias header "
-"is prepended to a generated table alias by the EJB-QL compiler to prevent "
-"name collisions. The alias header is constructed as follows: alias-header-"
-"prefix + int_counter + alias-header-suffix. An example alias header would be "
-"<literal>t0_</literal> for an alias-header-prefix of \"<literal>t</literal>"
-"\" and an alias-header-suffix of \"<literal>_</literal>\"."
+msgid "<emphasis role=\"bold\">alias-header-prefix</emphasis>: This required element gives the prefix used in creating the alias header. An alias header is prepended to a generated table alias by the EJB-QL compiler to prevent name collisions. The alias header is constructed as follows: alias-header-prefix + int_counter + alias-header-suffix. An example alias header would be <literal>t0_</literal> for an alias-header-prefix of \"<literal>t</literal>\" and an alias-header-suffix of \"<literal>_</literal>\"."
 msgstr "<emphasis role=\"bold\"></emphasis> 名字<literal></literal><literal></literal><literal></literal>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2830
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">alias-header-suffix</emphasis>: This required "
-"element gives the suffix portion of the generated alias header."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>:这个元素指定通知的易读的描"
-"述。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">alias-header-suffix</emphasis>: This required element gives the suffix portion of the generated alias header."
+msgstr "<emphasis role=\"bold\">alias-header-suffix</emphasis>:这个必需字段指定生成的别名头部信息的后缀。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2835
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">alias-max-length</emphasis>: This required element "
-"gives the maximum allowed length for the generated alias header."
-msgstr "<emphasis role=\"bold\">name</emphasis>:这个元素包含通知类的类全名。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">alias-max-length</emphasis>: This required element gives the maximum allowed length for the generated alias header."
+msgstr "<emphasis role=\"bold\">alias-max-length</emphasis>:这个必需元素给出生成的别名头部信息所允许的最大长度。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2840
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">subquery-supported</emphasis>: This required element "
-"specifies if this <literal>type-mapping</literal> subqueries as either true "
-"or false. Some EJB-QL operators are mapped to exists subqueries. If "
-"<literal>subquery-supported</literal> is false, the EJB-QL compiler will use "
-"a left join and is null."
+msgid "<emphasis role=\"bold\">subquery-supported</emphasis>: This required element specifies if this <literal>type-mapping</literal> subqueries as either true or false. Some EJB-QL operators are mapped to exists subqueries. If <literal>subquery-supported</literal> is false, the EJB-QL compiler will use a left join and is null."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2845
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">true-mapping</emphasis>: This required element "
-"defines <emphasis>true</emphasis> identity in EJB-QL queries. Examples "
-"include <literal>TRUE</literal>, <literal>1</literal>, and <literal>(1=1)</"
-"literal>."
-msgstr ""
-"<emphasis role=\"strong\">例如:</emphasis>建议的取值为 <literal>4</"
-"literal>,<literal>8</literal>,和 <literal>16</literal>"
+#, no-c-format
+msgid "<emphasis role=\"bold\">true-mapping</emphasis>: This required element defines <emphasis>true</emphasis> identity in EJB-QL queries. Examples include <literal>TRUE</literal>, <literal>1</literal>, and <literal>(1=1)</literal>."
+msgstr "<emphasis role=\"bold\">true-mapping</emphasis>:这个必需元素定义 EJB-QL 查询里的 <emphasis>true</emphasis> 标识符。如 <literal>TRUE</literal>、<literal>1</literal> 和 <literal>(1=1)</literal>。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2850
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">false-mapping</emphasis>: This required element "
-"defines <emphasis>false</emphasis> identity in EJB-QL queries. Examples "
-"include <literal>FALSE</literal>, <literal>0</literal>, and <literal>(1=0)</"
-"literal>."
-msgstr ""
-"<emphasis role=\"strong\">例如:</emphasis>建议的取值为 <literal>4</"
-"literal>,<literal>8</literal>,和 <literal>16</literal>"
+#, no-c-format
+msgid "<emphasis role=\"bold\">false-mapping</emphasis>: This required element defines <emphasis>false</emphasis> identity in EJB-QL queries. Examples include <literal>FALSE</literal>, <literal>0</literal>, and <literal>(1=0)</literal>."
+msgstr "<emphasis role=\"bold\">false-mapping</emphasis>:这个可选元素定义 EJB-QL 查询里的 <emphasis>false</emphasis> 标识符。如 <literal>FALSE</literal>、<literal>0</literal> 和 <literal>(1=0)</literal>。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2855
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">function-mapping</emphasis>: This optional element "
-"specifies one or more the mappings from an EJB-QL function to an SQL "
-"implementation. See <xref linkend=\"Datasource_Customization-Function_Mapping"
-"\"/> for the details."
+msgid "<emphasis role=\"bold\">function-mapping</emphasis>: This optional element specifies one or more the mappings from an EJB-QL function to an SQL implementation. See <xref linkend=\"Datasource_Customization-Function_Mapping\"/> for the details."
 msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2860
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mapping</emphasis>: This required element specifies "
-"the mappings from a Java type to the corresponding JDBC and SQL type. See "
-"<xref linkend=\"Datasource_Customization-Mapping\"/> for the details."
+msgid "<emphasis role=\"bold\">mapping</emphasis>: This required element specifies the mappings from a Java type to the corresponding JDBC and SQL type. See <xref linkend=\"Datasource_Customization-Mapping\"/> for the details."
 msgstr ""
 
 #. Tag: title
 #: The_CMP_Engine.xml:2868
 #, no-c-format
-#, fuzzy
 msgid "Function Mapping"
 msgstr "集合类(Collections)映射"
 
@@ -9039,159 +6563,95 @@
 #: The_CMP_Engine.xml:2869
 #, no-c-format
 msgid "The function-mapping element model is show below."
-msgstr ""
+msgstr "下面是 function-mapping 元素的内容模型。"
 
 #. Tag: title
 #: The_CMP_Engine.xml:2873
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The jbosscmp-jdbc function-mapping element content model"
-msgstr "The descriptors element content model"
+msgstr "jbosscmp-jdbc 的 function-mapping 元素的内容模型"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2880
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The allowed child elements are:"
-msgstr "子元素是:"
+msgstr "所允许的子元素是:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2885
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">function-name</emphasis>: This required element "
-"gives the EJB-QL function name, e.g., <literal>concat</literal>, "
-"<literal>substring</literal>."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderPreload</emphasis> 包含了需要预先加载的用"
-"逗号隔开的节点列表(如:<literal>/aop</literal>,<literal>/productcatalogue</"
-"literal>)"
+#, no-c-format
+msgid "<emphasis role=\"bold\">function-name</emphasis>: This required element gives the EJB-QL function name, e.g., <literal>concat</literal>, <literal>substring</literal>."
+msgstr "<emphasis role=\"bold\">function-name</emphasis>:这个必需元素给出 EJB-QL 函数的名称,如 <literal>concat</literal>、<literal>substring</literal>。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2890
 #, no-c-format
-msgid ""
-"<emphasis role=\"bold\">function-sql</emphasis>: This required element gives "
-"the SQL for the function as appropriate for the underlying database. "
-"Examples for a <literal>concat</literal> function include: <literal>(?1 || ?"
-"2)</literal>, <literal>concat(?1, ?2)</literal>, <literal>(?1 + ?2)</"
-"literal>."
+msgid "<emphasis role=\"bold\">function-sql</emphasis>: This required element gives the SQL for the function as appropriate for the underlying database. Examples for a <literal>concat</literal> function include: <literal>(?1 || ?2)</literal>, <literal>concat(?1, ?2)</literal>, <literal>(?1 + ?2)</literal>."
 msgstr ""
 
 #. Tag: title
 #: The_CMP_Engine.xml:2898
 #, no-c-format
-#, fuzzy
 msgid "Mapping"
 msgstr "映射"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2899
 #, no-c-format
-#, fuzzy
-msgid ""
-"A <literal>type-mapping</literal> is simply a set of mappings between Java "
-"class types and database types. A set of type mappings is defined by a set "
-"of <literal>mapping</literal> elements, the content model for which is shown "
-"in <xref linkend=\"Mapping-The_jbosscmp_jdbc_mapping_element_content_model."
-"\"/>."
-msgstr ""
-"<literal>type-mapping</literal> 是一系列从 Java 类的类型到数据库类型的映射。"
-"这些映射通过 <literal>mapping</literal> 元素进行定义,<xref linkend="
-"\"Mapping-The_jbosscmp_jdbc_mapping_element_content_model.\"/> 展示了它的内容"
-"格式。"
+msgid "A <literal>type-mapping</literal> is simply a set of mappings between Java class types and database types. A set of type mappings is defined by a set of <literal>mapping</literal> elements, the content model for which is shown in <xref linkend=\"Mapping-The_jbosscmp_jdbc_mapping_element_content_model.\"/>."
+msgstr "<literal>type-mapping</literal> 是一系列从 Java 类的类型到数据库类型的映射。这些映射通过 <literal>mapping</literal> 元素进行定义,<xref linkend=\"Mapping-The_jbosscmp_jdbc_mapping_element_content_model.\"/> 展示了它的内容格式。"
 
 #. Tag: title
 #: The_CMP_Engine.xml:2903
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The jbosscmp-jdbc mapping element content model."
-msgstr "jbosscmp-jdbc 文件的 mapping 元素的内容格式。"
+msgstr "jbosscmp-jdbc 文件的 mapping 元素的内容格式。 "
 
 #. Tag: para
 #: The_CMP_Engine.xml:2910
 #, no-c-format
-#, fuzzy
-msgid ""
-"If JBoss cannot find a mapping for a type, it will serialize the object and "
-"use the <literal>java.lang.Object</literal> mapping. The following describes "
-"the three child elements of the mapping element:"
-msgstr ""
-"如果 JBoss 不能找到某个类型的映射,它将序列化这个对象并使用 <literal>java."
-"lang.Object</literal> 映射。下面描述了 mapping 元素的 3 个子元素:"
+msgid "If JBoss cannot find a mapping for a type, it will serialize the object and use the <literal>java.lang.Object</literal> mapping. The following describes the three child elements of the mapping element:"
+msgstr "如果 JBoss 不能找到某个类型的映射,它将序列化这个对象并使用 <literal>java.lang.Object</literal> 映射。下面描述了 mapping 元素的 3 个子元素:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2915
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">java-type</emphasis>: This required element gives "
-"the fully qualified name of the Java class to be mapped. If the class is a "
-"primitive wrapper class such as <literal>java.lang.Short</literal>, the "
-"mapping also applies to the primitive type."
-msgstr ""
-"<emphasis role=\"bold\">java-type</emphasis>:这是一个必需元素,它指定被映射"
-"的 Java 类的全限定名。如果这个类是一个原始 wrapper 类,如 <literal>java.lang."
-"Short</literal>,那么该映射也适用于原始类型。"
+msgid "<emphasis role=\"bold\">java-type</emphasis>: This required element gives the fully qualified name of the Java class to be mapped. If the class is a primitive wrapper class such as <literal>java.lang.Short</literal>, the mapping also applies to the primitive type."
+msgstr "<emphasis role=\"bold\">java-type</emphasis>:这是一个必需元素,它指定被映射的 Java 类的全限定名。如果这个类是一个原始 wrapper 类,如 <literal>java.lang.Short</literal>,那么该映射也适用于原始类型。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2920
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">jdbc-type</emphasis>: This required element gives "
-"the JDBC type that is used when setting parameters in a JDBC "
-"<literal>PreparedStatement</literal> or loading data from a JDBC "
-"<literal>ResultSet</literal>. The valid types are defined in <literal>java."
-"sql.Types</literal>."
-msgstr ""
-"<emphasis role=\"bold\">jdbc-type</emphasis>:这个必需的元素指定在 JDBC "
-"<literal>PreparedStatement</literal> 里设置参数或从 JDBC <literal>ResultSet</"
-"literal> 载入数据时使用的 JDBC 类型。有效的类型在 <literal>java.sql.Types</"
-"literal> 里进行定义。"
+msgid "<emphasis role=\"bold\">jdbc-type</emphasis>: This required element gives the JDBC type that is used when setting parameters in a JDBC <literal>PreparedStatement</literal> or loading data from a JDBC <literal>ResultSet</literal>. The valid types are defined in <literal>java.sql.Types</literal>."
+msgstr "<emphasis role=\"bold\">jdbc-type</emphasis>:这个必需的元素指定在 JDBC <literal>PreparedStatement</literal> 里设置参数或从 JDBC <literal>ResultSet</literal> 载入数据时使用的 JDBC 类型。有效的类型在 <literal>java.sql.Types</literal> 里进行定义。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2925
 #, no-c-format
-#, fuzzy
-msgid ""
-"<emphasis role=\"bold\">sql-type</emphasis>: This required element gives the "
-"SQL type that is used in create table statements. Valid types are only "
-"limited by your database vendor."
-msgstr ""
-"<emphasis role=\"bold\">sql-type</emphasis>:这个必需的元素指定了在 create "
-"table 语句里使用的 SQL 类型。有效的类型取决于不同的数据库供应商。"
+msgid "<emphasis role=\"bold\">sql-type</emphasis>: This required element gives the SQL type that is used in create table statements. Valid types are only limited by your database vendor."
+msgstr "<emphasis role=\"bold\">sql-type</emphasis>:这个必需的元素指定了在 create table 语句里使用的 SQL 类型。有效的类型取决于不同的数据库供应商。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2930
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">param-setter</emphasis>: This optional element "
-"specifies the fully qualified name of the <literal>JDBCParameterSetter</"
-"literal> implementation for this mapping."
-msgstr ""
-"<emphasis role=\"bold\">param-setter</emphasis>:这个可选元素指定这个映射的 "
-"<literal>JDBCParameterSetter</literal> 实现的全限定名。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">param-setter</emphasis>: This optional element specifies the fully qualified name of the <literal>JDBCParameterSetter</literal> implementation for this mapping."
+msgstr "<emphasis role=\"bold\">param-setter</emphasis>:这个可选元素指定该映射的 <literal>JDBCParameterSetter</literal> 实现的全限定名。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2935
 #, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">result-reader</emphasis>: This option element "
-"specifies the fully qualified name of the <literal>JDBCResultSetReader</"
-"literal> implementation for this mapping."
-msgstr ""
-"<emphasis role=\"bold\">result-reader</emphasis>:这个可选元素指定该映射的 "
-"<literal>JDBCResultSetReader</literal> 实现的全限定名。"
+msgid "<emphasis role=\"bold\">result-reader</emphasis>: This option element specifies the fully qualified name of the <literal>JDBCResultSetReader</literal> implementation for this mapping."
+msgstr "<emphasis role=\"bold\">result-reader</emphasis>:这个可选元素指定该映射的 <literal>JDBCResultSetReader</literal> 实现的全限定名。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2940
 #, no-c-format
-#, fuzzy
 msgid "An example mapping element for a short in Oracle9i is shown below."
 msgstr "下面是一个关于 Oracle9i 的 Short 类型的 mapping 元素定义。"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2943
 #, no-c-format
-#, fuzzy
 msgid ""
 "&lt;jbosscmp-jdbc&gt;\n"
 "    &lt;type-mappings&gt;\n"
@@ -9224,27 +6684,18 @@
 #. Tag: title
 #: The_CMP_Engine.xml:2947
 #, no-c-format
-#, fuzzy
 msgid "User Type Mappings"
 msgstr "用户类型映射"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2948
 #, no-c-format
-#, fuzzy
-msgid ""
-"User type mappings allow one to map from JDBC column types to custom CMP "
-"fields types by specifying an instance of <literal>org.jboss.ejb.plugins.cmp."
-"jdbc.Mapper</literal> interface, the definition of which is shown below."
-msgstr ""
-"用户类型映射允许你通过一个 <literal>org.jboss.ejb.plugins.cmp.jdbc.Mapper</"
-"literal> 接口的实例把 JDBC 列的类型映射到自定义的 CMP 字段类型,下面给出了它"
-"的定义。"
+msgid "User type mappings allow one to map from JDBC column types to custom CMP fields types by specifying an instance of <literal>org.jboss.ejb.plugins.cmp.jdbc.Mapper</literal> interface, the definition of which is shown below."
+msgstr "用户类型映射允许你通过一个 <literal>org.jboss.ejb.plugins.cmp.jdbc.Mapper</literal> 接口的实例把 JDBC 列的类型映射到自定义的 CMP 字段类型,下面给出了它的定义。"
 
 #. Tag: programlisting
 #: The_CMP_Engine.xml:2951
 #, no-c-format
-#, fuzzy
 msgid ""
 "public interface Mapper\n"
 "{\n"
@@ -9283,55 +6734,30 @@
 #. Tag: para
 #: The_CMP_Engine.xml:2952
 #, no-c-format
-#, fuzzy
-msgid ""
-"A prototypical use case is the mapping of an integer type to its type-safe "
-"Java enumeration instance. The content model of the <literal>user-type-"
-"mappings</literal> element consists of one or more <literal>user-type-"
-"mapping</literal> elements, the content model of which is shown in <xref "
-"linkend=\"User_Type_Mappings-The_user_type_mapping_content_model_\"/>."
-msgstr ""
-"从整型映射到类型安全的 Java enumeration 实例是一个原型用例。<literal>user-"
-"type-mappings</literal> 元素的内容由一个或多个 <literal>user-type-mapping</"
-"literal> 元素组成, <xref linkend=\"User_Type_Mappings-"
-"The_user_type_mapping_content_model_\"/> 展示了其内容格式。"
+msgid "A prototypical use case is the mapping of an integer type to its type-safe Java enumeration instance. The content model of the <literal>user-type-mappings</literal> element consists of one or more <literal>user-type-mapping</literal> elements, the content model of which is shown in <xref linkend=\"User_Type_Mappings-The_user_type_mapping_content_model_\"/>."
+msgstr "从整型映射到类型安全的 Java enumeration 实例是一个原型用例。<literal>user-type-mappings</literal> 元素的内容由一个或多个 <literal>user-type-mapping</literal> 元素组成, <xref linkend=\"User_Type_Mappings-The_user_type_mapping_content_model_\"/> 展示了其内容格式。"
 
 #. Tag: title
 #: The_CMP_Engine.xml:2957
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The user-type-mapping content model &gt;"
 msgstr "user-type-mapping 的内容格式 &gt;"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2967
 #, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">java-type</emphasis>: the fully qualified name of "
-"the CMP field type in the mapping."
-msgstr ""
-"<emphasis role=\"bold\">java-type</emphasis>:该映射里的 CMP 字段类型的全限定"
-"名。"
+msgid "<emphasis role=\"bold\">java-type</emphasis>: the fully qualified name of the CMP field type in the mapping."
+msgstr "<emphasis role=\"bold\">java-type</emphasis>:该映射里的 CMP 字段类型的全限定名。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2972
 #, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mapped-type</emphasis>: the fully qualified name of "
-"the database type in the mapping."
-msgstr ""
-"<emphasis role=\"bold\">mapped-type</emphasis>:该映射里的数据库类型的全限定"
-"名。"
+msgid "<emphasis role=\"bold\">mapped-type</emphasis>: the fully qualified name of the database type in the mapping."
+msgstr "<emphasis role=\"bold\">mapped-type</emphasis>:该映射里的数据库类型的全限定名。"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2977
 #, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">mapper</emphasis>: the fully qualified name of the "
-"<literal>Mapper</literal> interface implementation that handles the "
-"conversion between the <literal>java-type</literal> and <literal>mapped-"
-"type</literal>."
-msgstr ""
-"<emphasis role=\"bold\">mapper</emphasis>:处理 <literal>java-type</literal> "
-"和 <literal>mapped-type</literal> 之间的转换的 <literal>Mapper</literal> 接口"
-"实现的全限定名。"
+msgid "<emphasis role=\"bold\">mapper</emphasis>: the fully qualified name of the <literal>Mapper</literal> interface implementation that handles the conversion between the <literal>java-type</literal> and <literal>mapped-type</literal>."
+msgstr "<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