[jboss-cvs] JBossAS SVN: r84910 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Mar 1 19:37:05 EST 2009
Author: xhuang at jboss.com
Date: 2009-03-01 19:37:04 -0500 (Sun, 01 Mar 2009)
New Revision: 84910
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Reference_Introduction.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Reference_Introduction.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Reference_Introduction.po 2009-03-02 00:32:59 UTC (rev 84909)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Reference_Introduction.po 2009-03-02 00:37:04 UTC (rev 84910)
@@ -9,8 +9,8 @@
"Project-Id-Version: J2EE_Reference_Introduction\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-02-24 10:56+1000\n"
-"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"PO-Revision-Date: 2009-03-02 10:36+1000\n"
+"Last-Translator: Xi HUANG\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -5637,7 +5637,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1347
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Initialize the unified class loader repository to contain all JARs in the "
"optional patch directory as well as the server configuration file conf "
@@ -5648,25 +5648,23 @@
"class loader. This effectively makes all <literal>UnifiedClassLoader</"
"literal>s available through the thread context class loader."
msgstr ""
-"初始化统一类加载器库(unified class loader repository)来包含在可选的patch目录"
-"和服务器配置文件conf目录下的所有JAR，如：<literal>server/default/conf</"
-"literal>。 对于每个JAR和目录，都将建立一个<literal>org.jboss.mx.loading."
-"UnifiedClassLoader</literal>，并向统一库注册。然后，"
-"<literal>UnifiedClassLoader</literal>中的一个被设置为线程上下文类加载器。这有"
-"效地使所有<literal>UnifiedClassLoader</literal>成为可用的。"
+"初始化统一类加载器库(unified class loader repository)来包含在可选的 patch 目录"
+"和服务器配置文件 conf 目录下的所有 JAR，如：<literal>server/default/conf</"
+"literal>。对于每个 JAR 和目录，都将建立一个 <literal>org.jboss.mx.loading."
+"UnifiedClassLoader</literal>，并向统一库注册。然后，<literal>UnifiedClassLoader</literal> 中的一个被设置为线程上下文类加载器。这有"
+"效地使所有 <literal>UnifiedClassLoader</literal> 成为可用的。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1352
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>org.jboss.system.ServiceController</literal> MBean is created. "
"The <literal>ServiceController</literal> manages the JBoss MBean services "
"life cycle. We will discuss the JBoss MBean services notion in detail in "
"<xref linkend=\"Using_JMX_as_a_Microkernel-JBoss_MBean_Services\"/>."
msgstr ""
-"<literal>org.jboss.system.ServiceController</literal> MBean被建立了。"
-"<literal>ServiceController</literal>管理JBoss MBean服务的生命周期。我们将在"
-"<xref linkend=\"ch2.mbeanservice.sect\"/>详细讨论JBoss MBean服务。"
+"<literal>org.jboss.system.ServiceController</literal> MBean 被建立了。"
+"<literal>ServiceController</literal> 管理 JBoss MBean 服务的生命周期。我们将在 <xref linkend=\"Using_JMX_as_a_Microkernel-JBoss_MBean_Services\"/> 详细讨论 JBoss MBean 服务。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1357
@@ -5745,7 +5743,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1391
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"As we have seen, JBoss relies on JMX to load in the MBean services that make "
"up a given server instance's personality. All of the bundled "
@@ -5753,9 +5751,9 @@
"MBeans. The best way to add services to the JBoss server is to write your "
"own JMX MBeans."
msgstr ""
-"如我们已经看到的，JBoss依赖JMX来加载MBean服务，组成服务器实例的特定功能。所有"
-"标准JBoss发行版本捆绑的功能都是基于MBean的。把服务加入到JBoss服务器的最好方法"
-"就是编写你自己的JMX MBean。"
+"如我们已经看到的，JBoss 依赖 JMX 来加载 MBean 服务，组成服务器实例的特定功能。所有"
+"标准 JBoss 发行版本捆绑的功能都是基于 MBean 的。把服务加入到 JBoss 服务器的最好方法"
+"就是编写你自己的 JMX MBean。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1394
@@ -5809,7 +5807,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1402
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>SARDeployer</literal> handles services archives. A service "
"archive can be either a jar that ends with a <literal>.sar</literal> suffix "
@@ -5820,11 +5818,9 @@
"\"The_SARDeployer_MBean-"
"The_DTD_for_the_MBean_service_descriptor_parsed_by_the_SARDeployer\"/>."
msgstr ""
-"<literal>SARDeployer</literal>处理服务档案文件。服务档案文件可以是以"
-"<literal>.sar</literal>结尾并包含一个<literal>META-INF/jboss-service.xml</"
-"literal>描述符的JAR，也可以是独立的命名模式为<literal>*-service.xml</literal>"
-"的XML描述符。服务描述符的DTD是<literal>jboss-service_4.0.dtd</literal>，如"
-"<xref linkend=\"ch2.sardtd.fig\"/>所示。"
+"<literal>SARDeployer</literal> 处理服务档案文件。服务档案文件可以是以 <literal>.sar</literal> 结尾并包含一个 <literal>META-INF/jboss-service.xml</literal> 描述符的 JAR，也可以是独立的命名模式为 <literal>*-service.xml</literal> 的 XML 描述符。服务描述符的 DTD 是 <literal>jboss-service_4.0.dtd</literal>，如 <xref linkend="
+"\"The_SARDeployer_MBean-"
+"The_DTD_for_the_MBean_service_descriptor_parsed_by_the_SARDeployer\"/> 所示。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1406
@@ -5976,7 +5972,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1455
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">server/mbean/depends</emphasis> and <emphasis role="
"\"bold\">server/mbean/depends-list</emphasis>: these elements specify a "
@@ -5989,12 +5985,12 @@
"<emphasis role=\"bold\">server/mbean/depends</emphasis> 和 <emphasis role="
"\"bold\">server/mbean/depends-list</emphasis>：指定了从使用这些元素的 MBean "
"到 <literal>depends</literal> 或者 <literal>depends-list</literal> 命名的 "
-"MBean 的依赖性。<xref linkend=\"ch2.servicedep.fig\"/>。注意这个依赖值可以是"
+"MBean 的依赖性。<xref linkend=\"JBoss_MBean_Services-Specifying_Service_Dependencies\"/>。注意这个依赖值可以是"
"定义了嵌套 MBean 的另外一个 MBean 元素。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1462
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"MBean attribute values don't need to be hardcoded literal strings. "
"Service files may contain references to system properties using the <literal>"
@@ -6011,7 +6007,7 @@
"<literal>name</literal> didn't exist. If none of the listed properties "
"exist and no default value is given, no substitution will occur."
msgstr ""
-"MBean 属性值不需要直接写(hardcode)成字符串。服务文件可以用 <literal>${name}</"
+"MBean 属性值不需要硬编码(hardcode)成字符串。服务文件可以用 <literal>${name}</"
"literal> 来包含系统属性的引用，<literal>name</literal> 在这里是 Java 系统属性"
"的名字。这个系统属性的值，可以调用 <literal>System.getProperty(\"name\")</"
"literal> 来获得。多个属性可以用逗号隔开来指定，如 <literal>${name1,name2,"
@@ -6024,7 +6020,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1465
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"When the <literal>SARDeployer</literal> is asked to deploy a service "
"performs several steps. <xref linkend=\"The_SARDeployer_MBean-"
@@ -6033,7 +6029,9 @@
"service."
msgstr ""
"当 <literal>SARDeployer</literal> 被要求部署一个服务时，它要执行几个步骤。"
-"<xref linkend=\"ch2.sardepstart.fig\"/> 是一个展示服务的初始启动阶段的序列"
+"<xref linkend=\"The_SARDeployer_MBean-"
+"A_sequence_diagram_highlighting_the_main_activities_performed_by_the_SARDeployer_to_start_a_JBoss_MBean_service"
+"\"/> 是一个展示服务的初始启动阶段的序列"
"图。"
#. Tag: title
@@ -6042,20 +6040,19 @@
msgid ""
"A sequence diagram highlighting the main activities performed by the "
"SARDeployer to start a JBoss MBean service"
-msgstr ""
-"A sequence diagram highlighting the main activities performed by the "
-"SARDeployer to start a JBoss MBean service"
+msgstr "突出显示被 SARDeployer 执行并用于启动 JBoss MBean 服务的主要活动的序列图"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1476
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"In <xref linkend=\"The_SARDeployer_MBean-"
"A_sequence_diagram_highlighting_the_main_activities_performed_by_the_SARDeployer_to_start_a_JBoss_MBean_service"
"\"/> the following is illustrated:"
msgstr ""
-"A sequence diagram highlighting the main activities performed by the "
-"SARDeployer to start a JBoss MBean service"
+"<xref linkend=\"The_SARDeployer_MBean-"
+"A_sequence_diagram_highlighting_the_main_activities_performed_by_the_SARDeployer_to_start_a_JBoss_MBean_service"
+"\"/> 解释了下列步骤："
#. Tag: para
#: J2EE_Reference_Introduction.xml:1481
@@ -6128,7 +6125,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1511
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Method 2.4.1. For each MBean instance created, obtain its JMX "
"<literal>ObjectName</literal> and ask the ServiceController to handle the "
@@ -6137,14 +6134,14 @@
"service's dependencies are satisfied is the service create method "
"invoked."
msgstr ""
-"Method 2.4.1，对于创建的每个MBean实例，获得它的JMX <literal>ObjectName</"
-"literal>并请求ServiceController来处理服务生命周期的create步骤。"
-"<literal>ServiceController</literal>处理MBean服务的相关性(dependencies)。只有"
-"满足了服务的相关性，create方法才会被调用。"
+"Method 2.4.1，对于创建的每个 MBean 实例，获得它的 JMX <literal>ObjectName</"
+"literal> 并请求 ServiceController 来处理服务生命周期的 create 步骤。"
+"<literal>ServiceController</literal> 处理 MBean 服务的相关性(dependencies)。只有"
+"满足了服务的相关性，create 方法才会被调用。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1516
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Methods prefixed with 3.1 correspond to the start of each MBean service "
"defined in the service descriptor. For each MBean instance created, obtain "
@@ -6154,10 +6151,10 @@
"service. Only if the service's dependencies are satisfied is the service "
"start method invoked."
msgstr ""
-"以3.1开头的方法对应服务描述符里定义的每个MBean服务的开始。对于创建的每个MBean"
-"实例，获取它的MX ObjectName并请求<literal>ServiceController</literal>来处理服"
-"务生命周期的start步骤。<literal>ServiceController</literal>处理MBean服务的相"
-"关性。只有满足了服务的相关性，服务的start方法才会被调用。"
+"以 3.1 开头的方法对应服务描述符里定义的每个 MBean 服务的开始。对于创建的每个 MBean"
+"实例，获取它的 JMX ObjectName 并请求 <literal>ServiceController</literal> 来处理服"
+"务生命周期的 start 步骤。<literal>ServiceController</literal> 处理 MBean 服务的相"
+"关性。只有满足了服务的相关性，服务的 start 方法才会被调用。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1524
@@ -6215,16 +6212,13 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1529
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>ServiceController</literal> MBean invokes the methods of the "
"<literal>Service</literal> interface at the appropriate times of the service "
"life cycle. We'll discuss the methods in more detail in the "
"<literal>ServiceController</literal> section."
-msgstr ""
-"<literal>ServiceController</literal> MBean 在服务生命周期的合适时候调用"
-"<literal>Service</literal>接口的方法。我们将在<literal>ServiceController</"
-"literal>部分讨论这个方法的更多细节。"
+msgstr "<literal>ServiceController</literal> MBean 在服务生命周期的合适时候调用 <literal>Service</literal> 接口的方法。我们将在 <literal>ServiceController</literal> 部分讨论这个方法的更多细节。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1535
@@ -6234,7 +6228,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1536
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"JBoss manages dependencies between MBeans via the <literal>org.jboss.system."
"ServiceController</literal> custom MBean. The SARDeployer delegates to the "
@@ -6244,11 +6238,10 @@
"\"/> shows a sequence diagram that highlights interaction between the "
"<literal>SARDeployer</literal> and <literal>ServiceController</literal>."
msgstr ""
-"JBoss通过<literal>org.jboss.system.ServiceController</literal>自定义MBean管理"
-"MBean之间的相关性。当初始化，创建，启动，停止和删除MBean服务时，SARDeployer委"
-"托给ServiceController。<xref linkend=\"ch2.servicecontroller.fig\"/> 是一个着"
-"重说明<literal>SARDeployer</literal> 和 <literal>ServiceController</literal>"
-"之间相互作用的序列图。"
+"JBoss 通过 <literal>org.jboss.system.ServiceController</literal> 自定义 MBean 管理 MBean 之间的相关性。当初始化、创建、启动、停止和删除 MBean 服务时，SARDeployer 委"
+"托给 ServiceController。<<xref linkend=\"The_ServiceController_MBean-"
+"The_interaction_between_the_SARDeployer_and_ServiceController_to_start_a_service"
+"\"/> 是一个着重说明 <literal>SARDeployer</literal> 和 <literal>ServiceController</literal> 之间相互作用的序列图。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1540
@@ -6294,7 +6287,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1555
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"When a service's <literal>create</literal> method is called, all "
"services on which the service depends have also had their create method "
@@ -6306,11 +6299,10 @@
"literal> in favor of just the <literal>start</literal> method because that "
"is the first point at which the service can be fully functional."
msgstr ""
-"当服务的<literal>create</literal>方法被调用时，这个服务依赖的所有服务也会调用"
-"它们自己的create方法。这给予MBean一个机会来检查要求的MBean或服务是否存在。在"
-"这个时候服务不能利用其他MBean服务，因为大部分JBoss MBean服务直到用"
-"<literal>start</literal>方法开始时才具有全部的功能。因此，服务的实现经常不实"
-"现<literal>create</literal>而仅仅实现<literal>start</literal>方法，因为它才是"
+"当服务的 <literal>create</literal> 方法被调用时，这个服务依赖的所有服务也会调用"
+"它们自己的 create 方法。这给予 MBean 一个机会来检查要求的 MBean 或服务是否存在。在"
+"这个时候服务不能利用其他 MBean 服务，因为大部分 JBoss MBean 服务直到用 <literal>start</literal> 方法开始时才具有全部的功能。因此，服务的实现经常不实"
+"现 <literal>create</literal> 而仅仅实现 <literal>start</literal> 方法，因为它才是"
"服务完全可用的第一入口。"
#. Tag: title
@@ -6334,7 +6326,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1565
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"When a service's <literal>start</literal> method is called, all services "
"on which the service depends have also had their <literal>start</literal> "
@@ -6342,9 +6334,9 @@
"signals a service to become fully operational since all services upon which "
"the service depends have been created and started."
msgstr ""
-"当服务的<literal>start</literal>方法被调用时，这个服务依赖的所有服务也会调用"
-"它们自己的<literal>start</literal>方法。既然所依赖的服务都已经被创建和启动"
-"了，<literal>start</literal>方法的调用就标志着这个服务是完全可操作的了。"
+"当服务的 <literal>start</literal> 方法被调用时，这个服务依赖的所有服务也会调用"
+"它们自己的 <literal>start</literal> 方法。既然所依赖的服务都已经被创建和启动"
+"了，<literal>start</literal> 方法的调用就标志着这个服务是完全可操作的了。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1571
@@ -6406,7 +6398,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1591
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"To specify that an MBean service depends on other MBean services you need to "
"declare the dependencies in the mbean element of the service descriptor. "
@@ -6423,14 +6415,11 @@
"following listing shows example service descriptor fragments that illustrate "
"the usage of the dependency related elements."
msgstr ""
-"要指定MBean服务依赖于另外的MBean服务，你需要在服务描述符的mbean元素里声明这种"
-"依赖性。这可以用<literal>depends</literal> 和 <literal>depends-list</literal>"
-"元素来完成。两者的区别和<literal>optional-attribute-name</literal>属性的使用"
-"相关。如果你用单一值属性来跟踪<literal>ObjectName</literal>的依赖性，你应该使"
-"用depends元素。如果你用<literal>java.util.List</literal>兼容的属性来跟踪"
-"<literal>ObjectName</literal>的依赖性，你就应该使用<literal>depends-list</"
-"literal>元素。如果你只想指定依赖性，而不在乎关联的服务<literal>ObjectName</"
-"literal>绑定到你的MBean的属性上，你可以使用任意一个，依哪个更容易而定。下面是"
+"要指定 MBean 服务依赖于另外的 MBean 服务，你需要在服务描述符的 mbean 元素里声明这种"
+"依赖性。这可以用 <literal>depends</literal> 和 <literal>depends-list</literal> 元素来完成。两者的区别和<literal>optional-attribute-name</literal> 属性的使用相关。如果你用单一值属性来跟踪 <literal>ObjectName</literal> 的依赖性，你应该使"
+"用 depends 元素。如果你用 <literal>java.util.List</literal> 兼容的属性来跟踪 <literal>ObjectName</literal> 的依赖性，你就应该使用 <literal>depends-list</"
+"literal> 元素。如果你只想指定依赖性，而不在乎关联的服务 <literal>ObjectName</"
+"literal> 绑定到你的 MBean 的属性上，你可以使用任意一个，依哪个更容易而定。下面是"
"服务描述符示例的片段，它说明了和依赖性相关的元素的使用。"
#. Tag: programlisting
@@ -6515,7 +6504,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1595
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Another difference between the <literal>depends</literal> and "
"<literal>depends-list</literal> elements is that the value of the depends "
@@ -6534,17 +6523,17 @@
"<literal>ManagedConnectionFactoryName</literal> attribute of the "
"<literal>LocalTxConnectionManager</literal> class."
msgstr ""
-"<literal>depends</literal> 和 <literal>depends-list</literal>元素的另外一个区"
-"别就是，depends元素的值可能是完整的MBean服务配置，而不是服务的"
-"<literal>ObjectName</literal>。<xref linkend=\"ch2.dependon.ex\"/>是关于"
-"<literal>hsqldb-service.xml</literal>描述符里的一个示例。在这个例子里，定义了"
-"<literal>org.jboss.resource.connectionmanager.RARDeployment</literal>服务的配"
-"置，这里使用嵌套的 <literal>mbean</literal>元素作为<literal>depends</literal>"
-"元素的值。这表示<literal>org.jboss.resource.connectionmanager."
-"LocalTxConnectionManager</literal> MBean依赖于这个服务。<literal>jboss.jca:"
-"service=LocalTxDS,name=hsqldbDS</literal> <literal>ObjectName</literal>将被绑"
-"定到<literal>LocalTxConnectionManager</literal>类的"
-"<literal>ManagedConnectionFactoryName</literal>属性上。"
+"<literal>depends</literal> 和 <literal>depends-list</literal> 元素的另外一个区"
+"别就是，depends元素的值可能是完整的 MBean 服务配置，而不是服务的"
+"<literal>ObjectName</literal>。<xref linkend="
+"\"Specifying_Service_Dependencies-"
+"An_example_of_using_the_depends_element_to_specify_the_complete_configuration_of_a_depended_on_service."
+"\"/> 是关于 <literal>hsqldb-service.xml</literal> 描述符里的一个示例。在这个例子里，定义了"
+"<literal>org.jboss.resource.connectionmanager.RARDeployment</literal> 服务的配"
+"置，这里使用嵌套的 <literal>mbean</literal> 元素作为 <literal>depends</literal> 元素的值。这表示 <literal>org.jboss.resource.connectionmanager."
+"LocalTxConnectionManager</literal> MBean 依赖于这个服务。<literal>jboss.jca:"
+"service=LocalTxDS,name=hsqldbDS</literal> <literal>ObjectName</literal> 将被绑"
+"定到 <literal>LocalTxConnectionManager</literal> 类的 <literal>ManagedConnectionFactoryName</literal> 属性上。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1598
@@ -6686,7 +6675,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1620
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">URLs</emphasis>: A comma separated list of URL "
"strings for the locations that should be watched for changes. Strings that "
@@ -6702,13 +6691,11 @@
"discrimination between collections and directories that are simply unpacked "
"archives."
msgstr ""
-"<emphasis role=\"bold\">URLs</emphasis>：是一个用逗号隔开的URL字符串的列表，"
-"MBean服务会观察这些位置的变化。不对应有效URL的字符串被视作文件路径。相对文件"
-"路径根据服务器的主URL解析，例如，<literal>JBOSS_DIST/server/default</literal>"
-"是缺省的配置文件集。如果URL代表了一个文件，这个文件会被部署并观察随后的更新或"
-"删除。如果URL以<literal>/</literal>结尾，它代表一个目录，这个目录的内容被视作"
-"可部署的集合而且被观察发生的更新或删除。以<literal>/</literal>结尾来识别一个"
-"目录的要求遵循RFC2518规则，它允许集合和是简单的未封装档案的目录之间的区别。"
+"<emphasis role=\"bold\">URLs</emphasis>：是一个用逗号隔开的 URL 字符串的列表，MBean 服务会观察这些位置的变化。不对应有效 URL 的字符串被视作文件路径。相对文件"
+"路径根据服务器的主URL解析，例如，<literal>JBOSS_DIST/server/default</literal> 是缺省的配置文件集。如果 URL 代表了一个文件，这个文件会被部署并观察随后的更新或"
+"删除。如果 URL 以 <literal>/</literal> 结尾，它代表一个目录，这个目录的内容被视作"
+"可部署的集合而且被观察发生的更新或删除。以 <literal>/</literal> 结尾来识别一个"
+"目录的要求遵循 RFC2518 规则，它允许集合和是简单的未封装档案的目录之间的区别。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1623
@@ -6993,7 +6980,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1720
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Which approach you choose depends on whether or not you want your code to be "
"coupled to JBoss specific code. If you don't, then you would use the "
@@ -7014,17 +7001,17 @@
"literal>, <literal>startService</literal>, <literal>stopService</literal>, "
"and <literal>destroyService</literal> methods as required"
msgstr ""
-"使用哪种方法取决于你是否想要你的代码和JBoss相关的代码相关。如果你不希望这样，"
-"你可以用第一个方法。如果你不介意对JBoss类的依赖，最简单的方法就是从"
-"<literal>org.jboss.system.ServiceMBean</literal>扩展你的MBean接口，并且从绝"
-"对 <literal>org.jboss.system.ServiceMBeanSupport</literal>类扩展你的MBean实"
-"现。这个类实现了<literal>org.jboss.system.ServiceMBean</literal>接口。"
-"<literal>ServiceMBeanSupport</literal>提供了<literal>create</literal>，"
+"使用哪种方法取决于你是否想要你的代码和 JBoss 相关的代码相关。如果你不希望这样，"
+"你可以用第一个方法。如果你不介意对 JBoss 类的依赖，最简单的方法就是从"
+"<literal>org.jboss.system.ServiceMBean</literal> 扩展你的 MBean 接口，并且从绝"
+"对 <literal>org.jboss.system.ServiceMBeanSupport</literal> 类扩展你的 MBean 实"
+"现。这个类实现了 <literal>org.jboss.system.ServiceMBean</literal> 接口。"
+"<literal>ServiceMBeanSupport</literal> 提供了 <literal>create</literal>，"
"<literal>start</literal>，<literal>stop</literal>，和 <literal>destroy</"
-"literal>方法的实现，这可以集成logging和JBoss服务的状态管理跟踪。每个方法把和"
-"子类相关的工作分别委托给<literal>createService</literal>，"
+"literal>方法的实现，这可以集成 logging 和 JBoss 服务的状态管理跟踪。每个方法把和"
+"子类相关的工作分别委托给 <literal>createService</literal>，"
"<literal>startService</literal>，<literal>stopService</literal>，和 "
-"<literal>destroyService</literal>。当建立<literal>ServiceMBeanSupport</"
+"<literal>destroyService</literal>。当建立 <literal>ServiceMBeanSupport</"
"literal>的子类时，你将根据要求来覆盖(override) <literal>createService</"
"literal>，<literal>startService</literal>，<literal>stopService</literal>，"
"和 <literal>destroyService</literal> 中的一个或多个方法。"
@@ -7053,7 +7040,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1728
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Version one of the classes, shown in <xref linkend="
"\"A_Standard_MBean_Example-"
@@ -7063,9 +7050,12 @@
"methods needed to start up correctly without using any JBoss-specific "
"classes."
msgstr ""
-"这个类的第一版本，如<xref linkend=\"ch2.jndimap1.ex\"/>所示，是基于服务接口方"
-"法模式的。这个版本的接口声明了<literal>start</literal> 和 <literal>stop</"
-"literal>方法，这样不需要使用任何JBoss相关的类就可以正确地启动。"
+"这个类的第一版本，如 <xref linkend="
+"\"A_Standard_MBean_Example-"
+"JNDIMapMBean_interface_and_implementation_based_on_the_service_interface_method_pattern"
+"\"/> 所示，是基于服务接口方"
+"法模式的。这个版本的接口声明了 <literal>start</literal> 和 <literal>stop</"
+"literal> 方法，这样不需要使用任何 JBoss 相关的类就可以正确地启动。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1731
@@ -7079,7 +7069,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1732
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"package org.jboss.book.jmx.ex1;\n"
" \n"
@@ -7094,7 +7084,7 @@
" public void stop() throws Exception;\n"
"}"
msgstr ""
-"package org.jboss.chap2.ex1;\n"
+"package org.jboss.book.jmx.ex1;\n"
" \n"
"// The JNDIMap MBean interface\n"
"import javax.naming.NamingException;\n"
@@ -7109,7 +7099,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1733
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"package org.jboss.book.jmx.ex1;\n"
"\n"
@@ -7179,7 +7169,7 @@
" }\n"
"}"
msgstr ""
-"package org.jboss.chap2.ex1;\n"
+"package org.jboss.book.jmx.ex1;\n"
"\n"
"// The JNDIMap MBean implementation\n"
"import java.util.HashMap;\n"
@@ -7232,7 +7222,7 @@
" InitialContext rootCtx = new InitialContext();\n"
" Name fullName = rootCtx.getNameParser(\"\").parse(jndiName);\n"
" System.out.println(\"fullName=\"+fullName);\n"
-" NonSerializableFactory.rebind(fullName，contextMap，true);\n"
+" NonSerializableFactory.rebind(fullName, contextMap, true);\n"
" }\n"
"\n"
" private void unbind(String jndiName)\n"
@@ -7249,7 +7239,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1734
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Version two of the classes, shown in <xref linkend="
"\"A_Standard_MBean_Example-"
@@ -7268,15 +7258,16 @@
"approach mentioned at the start of the <xref linkend="
"\"Using_JMX_as_a_Microkernel-JBoss_MBean_Services\"/>."
msgstr ""
-"这个类的第二个版本，如<xref linkend=\"ch2.jndimap1.ex\"/>所示，使用了JBoss "
-"<literal>ServiceMBean</literal>接口和<literal>ServiceMBeanSupport</literal>"
-"类。在这个版本里，实现类扩展了<literal>ServiceMBeanSupport</literal>类并覆盖"
-"了<literal>startService</literal> 和<literal>stopService</literal>方法。"
-"<literal>JNDIMapMBean</literal>也实现了绝对<literal>getName</literal>方法来为"
-"MBean返回一个描述名。<literal>JNDIMapMBean</literal>接口扩展了<literal>org."
-"jboss.system.ServiceMBean</literal>接口，因为它从<literal>ServiceMBean</"
-"literal>继承了服务生命周期方法，所以为<literal>JndiName</literal>属性只声明了"
-"setter和getter方法。这是在<xref linkend=\"ch2.mbeanservice.sect\"/>开始部分的"
+"这个类的第二个版本，如 <xref linkend="
+"\"A_Standard_MBean_Example-"
+"JNDIMapMBean_interface_and_implementation_based_on_the_service_interface_method_pattern"
+"\"/> 所示，使用了JBoss <literal>ServiceMBean</literal> 接口和 <literal>ServiceMBeanSupport</literal> 类。在这个版本里，实现类扩展了<literal>ServiceMBeanSupport</literal> 类并覆盖"
+"了<literal>startService</literal> 和 <literal>stopService</literal> 方法。"
+"<literal>JNDIMapMBean</literal> 也实现了绝对 <literal>getName</literal> 方法来为"
+"MBean返回一个描述名。<literal>JNDIMapMBean</literal> 接口扩展了 <literal>org."
+"jboss.system.ServiceMBean</literal> 接口，因为它从 <literal>ServiceMBean</"
+"literal> 继承了服务生命周期方法，所以为 <literal>JndiName</literal> 属性只声明了 setter 和 getter 方法。这是在 <xref linkend="
+"\"Using_JMX_as_a_Microkernel-JBoss_MBean_Services\"/> 开始部分的"
"第三种方法。"
#. Tag: title
@@ -7291,7 +7282,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1738
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"package org.jboss.book.jmx.ex2;\n"
"\n"
@@ -7304,7 +7295,7 @@
" public void setJndiName(String jndiName) throws NamingException;\n"
"}"
msgstr ""
-"package org.jboss.chap2.ex2;\n"
+"package org.jboss.book.jmx.ex2;\n"
"\n"
"// The JNDIMap MBean interface\n"
"import javax.naming.NamingException;\n"
@@ -7317,7 +7308,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1739
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"package org.jboss.book.jmx.ex2;\n"
"// The JNDIMap MBean implementation\n"
@@ -7386,7 +7377,7 @@
" }\n"
"}"
msgstr ""
-"package org.jboss.chap2.ex2;\n"
+"package org.jboss.book.jmx.ex2;\n"
"// The JNDIMap MBean implementation\n"
"import java.util.HashMap;\n"
"import javax.naming.InitialContext;\n"
@@ -7438,7 +7429,7 @@
" InitialContext rootCtx = new InitialContext();\n"
" Name fullName = rootCtx.getNameParser(\"\").parse(jndiName);\n"
" log.info(\"fullName=\"+fullName);\n"
-" NonSerializableFactory.rebind(fullName，contextMap，true);\n"
+" NonSerializableFactory.rebind(fullName, contextMap, true);\n"
" }\n"
"\n"
" private void unbind(String jndiName)\n"
@@ -7448,21 +7439,21 @@
" rootCtx.unbind(jndiName);\n"
" NonSerializableFactory.unbind(jndiName);\n"
" } catch(NamingException e) {\n"
-" log.error(\"Failed to unbind map\"，e);\n"
+" log.error(\"Failed to unbind map\", e);\n"
" }\n"
" }\n"
"}"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1740
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The source code for these MBeans along with the service descriptors is "
"located in the <literal>examples/src/main/org/jboss/book/jmx/{ex1,ex2}</"
"literal> directories."
msgstr ""
-"这些MBean的源码以及服务描述符在<literal>examples/src/main/org/jboss/chap2/"
-"{ex1,ex2}</literal>目录下。"
+"这些 MBean 的源码以及服务描述符在 <literal>examples/src/main/org/jboss/book/jmx/{ex1,ex2}</"
+"literal> 目录下。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1743
@@ -7472,7 +7463,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1746
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<!-- The SAR META-INF/jboss-service.xml descriptor -->\n"
"<server>\n"
@@ -7486,8 +7477,8 @@
msgstr ""
"<!-- The SAR META-INF/jboss-service.xml descriptor -->\n"
"<server>\n"
-" <mbean code=\"org.jboss.chap2.ex1.JNDIMap\" \n"
-" name=\"chap2.ex1:service=JNDIMap\">\n"
+" <mbean code=\"org.jboss.book.jmx.ex1.JNDIMap\" \n"
+" name=\"j2eechap2.ex1:service=JNDIMap\">\n"
" <attribute name=\"JndiName\">inmemory/maps/MapTest</"
"attribute>\n"
" <depends>jboss:service=Naming</depends>\n"
@@ -7577,7 +7568,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1782
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Let's start with a simple XMBean variation of the standard MBean version "
"of the JNDIMap that adds the descriptive information about the attributes "
@@ -7587,14 +7578,14 @@
"<literal>src/main/org/jboss/book/jmx/xmbean</literal> directory of the book "
"examples."
msgstr ""
-"让我们从一个简单的JNDIMap的标准XMBean版本的变体开始，然后加入属性，操作和参数"
-"的描述信息。下面的列表显示了<literal>jboss-service.xml</literal>描述符和"
-"<literal>jndimap-xmbean1.xml</literal> XMBean描述符。源码可以在本书示例的"
-"<literal>src/main/org/jboss/chap2/xmbean</literal>目录下找到。"
+"让我们从一个简单的 JNDIMap 的标准 XMBean 版本的变体开始，然后加入属性，操作和参数"
+"的描述信息。下面的列表显示了 <literal>jboss-service.xml</literal> 描述符和"
+"<literal>jndimap-xmbean1.xml</literal> XMBean 描述符。源码可以在本书示例的"
+"<literal>src/main/org/jboss/book/jmx/xmbean</literal> 目录下找到。"
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1785
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<?xml version='1.0' encoding='UTF-8' ?>\n"
"<!DOCTYPE server PUBLIC \n"
@@ -7611,14 +7602,14 @@
" </mbean>\n"
"</server>"
msgstr ""
-"<?xml version='1.0' encoding='UTF-8' ?>\n"
+"<?xml version='1.0' encoding='UTF-8' ?>\n"
"<!DOCTYPE server PUBLIC \n"
" \"-//JBoss//DTD MBean Service 3.2//EN\"\n"
" \"http://www.jboss.org/j2ee/dtd/jboss-service_3_2.dtd"
"\">\n"
"<server>\n"
-" <mbean code=\"org.jboss.chap2.xmbean.JNDIMap\"\n"
-" name=\"chap2.xmbean:service=JNDIMap\" \n"
+" <mbean code=\"org.jboss.book.jmx.xmbean.JNDIMap\"\n"
+" name=\"j2eechap2.xmbean:service=JNDIMap\" \n"
" xmbean-dd=\"META-INF/jndimap-xmbean.xml\">\n"
" <attribute name=\"JndiName\">inmemory/maps/MapTest</"
"attribute>\n"
@@ -7628,7 +7619,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1786
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
"<!DOCTYPE mbean PUBLIC\n"
@@ -7751,7 +7742,7 @@
" <constructor>\n"
" <description>The default constructor</description>\n"
" <name>JNDIMap</name>\n"
-" </constructor> \n"
+" </constructor> \n"
" <!-- Attributes -->\n"
" <attribute access=\"read-write\" getMethod=\"getJndiName\" setMethod="
"\"setJndiName\">\n"
@@ -7768,18 +7759,18 @@
" setMethod=\"setInitialValues\">\n"
" <description>The array of initial values that will be placed "
"into the\n"
-" map associated with the service。The array is a collection of\n"
+" map associated with the service. The array is a collection of\n"
" key,value pairs with elements[0,2,4,...2n] being the keys and\n"
-" elements [1,3,5,...,2n+1] the associated values。The\n"
+" elements [1,3,5,...,2n+1] the associated values. The\n"
" \"[Ljava.lang.String;\" type signature is the VM representation "
"of the\n"
-" java.lang.String[] type。</description>\n"
+" java.lang.String[] type. </description>\n"
" <name>InitialValues</name>\n"
" <type>[Ljava.lang.String;</type>\n"
" <descriptors>\n"
" <default value=\"key0,value0\"/>\n"
" </descriptors>\n"
-" </attribute> \n"
+" </attribute> \n"
" <!-- Operations -->\n"
" <operation>\n"
" <description>The start lifecycle operation</"
@@ -7816,14 +7807,14 @@
" <type>java.lang.Object</type>\n"
" </parameter>\n"
" <return-type>java.lang.Object</return-type>\n"
-" </operation> \n"
+" </operation> \n"
" <!-- Notifications -->\n"
" <notification>\n"
" <description>The notification sent whenever a value is get "
"into the map\n"
" managed by the service</description>\n"
" <name>javax.management.Notification</name>\n"
-" <notification-type>org.jboss.chap2.xmbean.JNDIMap.get</"
+" <notification-type>org.jboss.book.jmx.xmbean.JNDIMap.get</"
"notification-type>\n"
" </notification>\n"
" <notification>\n"
@@ -7831,7 +7822,7 @@
"into the map\n"
" managed by the service</description>\n"
" <name>javax.management.Notification</name>\n"
-" <notification-type>org.jboss.chap2.xmbean.JNDIMap.put</"
+" <notification-type>org.jboss.book.jmx.xmbean.JNDIMap.put</"
"notification-type>\n"
" </notification>\n"
"</mbean>"
@@ -7844,7 +7835,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1790
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples]$ ant -Dchap=jmx -Dex=xmbean1 run-example\n"
"...\n"
@@ -7887,50 +7878,46 @@
" changed from javax.management.Attribute at 82a72a to \n"
" javax.management.Attribute at acdb96]"
msgstr ""
-"[examples]$ ant -Dchap=chap2 -Dex=xmbean2 -Djboss.deploy.conf=rmi-adaptor "
-"run-example\n"
+"[examples]$ ant -Dchap=jmx -Dex=xmbean1 run-example\n"
"...\n"
-"run-examplexmbean2:\n"
+"run-examplexmbean1: \n"
" [java] JNDIMap Class: org.jboss.mx.modelmbean.XMBean\n"
" [java] JNDIMap Operations: \n"
" [java] + void start()\n"
" [java] + void stop()\n"
" [java] + void put(java.lang.Object chap2.xmbean:service=JNDIMap,java."
-"lang.Object cha\n"
-"p2.xmbean:service=JNDIMap)\n"
+"lang.Object \n"
+" chap2.xmbean:service=JNDIMap)\n"
" [java] + java.lang.Object get(java.lang.Object chap2.xmbean:"
"service=JNDIMap)\n"
-" [java] + java.lang.String getJndiName()\n"
-" [java] + void setJndiName(java.lang.String chap2.xmbean:"
-"service=JNDIMap)\n"
-" [java] + [Ljava.lang.String; getInitialValues()\n"
-" [java] + void setInitialValues([Ljava.lang.String; chap2.xmbean:"
-"service=JNDIMap)\n"
-" [java] handleNotification，event: null\n"
-" [java] key=key10，value=value10\n"
-" [java] handleNotification，event: javax.management.Notification"
-"[source=chap2.xmbean:s\n"
-"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.put,sequenceNumber=7,"
-"timeStamp=10986326\n"
-"93716,message=null,userData=null]\n"
-" [java] JNDIMap.put(key1，value1) successful\n"
-" [java] handleNotification，event: javax.management.Notification"
-"[source=chap2.xmbean:s\n"
-"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.get,sequenceNumber=8,"
-"timeStamp=10986326\n"
-"93857,message=null,userData=null]\n"
+" [java] name=chap2.xmbean:service=JNDIMap\n"
+" [java] listener=org.jboss.book.jmx.xmbean.TestXMBean1$Listener at f38cf0\n"
+" [java] key=key0, value=value0\n"
+" [java] handleNotification, event: javax.management.Notification"
+"[source=chap2.xmbean:\n"
+" service=JNDIMap][type=org.jboss.book.jmx.xmbean.JNDIMap.put]"
+"[message=]\n"
+" [java] JNDIMap.put(key1, value1) successful\n"
+" [java] handleNotification, event: javax.management.Notification"
+"[source=chap2.xmbean:\n"
+" service=JNDIMap][type=org.jboss.book.jmx.xmbean.JNDIMap.get]"
+"[message=]\n"
" [java] JNDIMap.get(key0): null\n"
-" [java] handleNotification，event: javax.management.Notification"
-"[source=chap2.xmbean:s\n"
-"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.get,sequenceNumber=9,"
-"timeStamp=10986326\n"
-"93896,message=null,userData=null]\n"
+" [java] handleNotification, event: javax.management.Notification"
+"[source=chap2.xmbean:\n"
+" service=JNDIMap][type=org.jboss.book.jmx.xmbean.JNDIMap.get]"
+"[message=]\n"
" [java] JNDIMap.get(key1): value1\n"
-" [java] handleNotification，event: javax.management.Notification"
-"[source=chap2.xmbean:s\n"
-"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.put,sequenceNumber=10,"
-"timeStamp=1098632\n"
-"693925,message=null,userData=null]"
+" [java] handleNotification, event: javax.management.Notification"
+"[source=chap2.xmbean:\n"
+" service=JNDIMap][type=org.jboss.book.jmx.xmbean.JNDIMap.put]"
+"[message=]\n"
+" [java] handleNotification, event: javax.management."
+"AttributeChangeNotification[source\n"
+" =chap2.xmbean:service=JNDIMap][type=jmx.attribute.change]"
+"[message=InitialValues \n"
+" changed from javax.management.Attribute at 82a72a to \n"
+" javax.management.Attribute at acdb96]"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1791
@@ -7957,7 +7944,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1794
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The other major difference between the Standard and XMBean versions of "
"JNDIMap is the descriptive metadata. Look at the <literal>chap2.xmbean:"
@@ -7966,9 +7953,10 @@
"\"Version_1_The_Annotated_JNDIMap_XMBean-"
"The_Version_1_JNDIMapXMBean_jmx_console_view\"/>."
msgstr ""
-"标准的和XMBean版本的JNDIMap之间的主要区别是描述性元数据。看看JMX控制台的"
-"<literal>chap2.xmbean:service=JNDIMap</literal>，你将看到如<xref linkend="
-"\"ch11.v1.fig\"/>所示的属性部分。"
+"标准的和 XMBean 版本的 NDIMap 之间的主要区别是描述性元数据。看看 JMX 控制台的"
+"<literal>chap2.xmbean:service=JNDIMap</literal>，你将看到如 <xref linkend="
+"\"Version_1_The_Annotated_JNDIMap_XMBean-"
+"The_Version_1_JNDIMapXMBean_jmx_console_view\"/> 所示的属性部分。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1798
@@ -8008,7 +7996,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1815
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
"<!DOCTYPE mbean PUBLIC\n"
@@ -8128,12 +8116,12 @@
" <state-action-on-update value=\"keep-running\"/>\n"
" <persistence-manager value=\"org.jboss.mx.persistence."
"ObjectStreamPersistenceManager\"/>\n"
-" </descriptors> <class>org.jboss.test.jmx.xmbean."
-"JNDIMap</class>\n"
+" </descriptors> <class>org.jboss.test.jmx.xmbean.JNDIMap</"
+"class>\n"
" <constructor>\n"
" <description>The default constructor</description>\n"
" <name>JNDIMap</name>\n"
-" </constructor> \n"
+" </constructor> \n"
" <!-- Attributes -->\n"
" <attribute access=\"read-write\" getMethod=\"getJndiName\" setMethod="
"\"setJndiName\">\n"
@@ -8150,7 +8138,7 @@
" setMethod=\"setInitialValues\">\n"
" <description>The array of initial values that will be placed "
"into the\n"
-" map associated with the service。The array is a collection of\n"
+" map associated with the service. The array is a collection of\n"
" key,value pairs with elements[0,2,4,...2n] being the keys and\n"
" elements [1,3,5,...,2n+1] the associated values</"
"description>\n"
@@ -8159,7 +8147,7 @@
" <descriptors>\n"
" <default value=\"key0,value0\"/>\n"
" </descriptors>\n"
-" </attribute> \n"
+" </attribute> \n"
" <!-- Operations -->\n"
" <operation>\n"
" <description>The start lifecycle operation</"
@@ -8196,14 +8184,14 @@
" <type>java.lang.Object</type>\n"
" </parameter>\n"
" <return-type>java.lang.Object</return-type>\n"
-" </operation> \n"
+" </operation> \n"
" <!-- Notifications -->\n"
" <notification>\n"
" <description>The notification sent whenever a value is get "
"into the map\n"
" managed by the service</description>\n"
" <name>javax.management.Notification</name>\n"
-" <notification-type>org.jboss.chap2.xmbean.JNDIMap.get</"
+" <notification-type>org.jboss.book.jmx.xmbean.JNDIMap.get</"
"notification-type>\n"
" </notification>\n"
" <notification>\n"
@@ -8211,7 +8199,7 @@
"into the map\n"
" managed by the service</description>\n"
" <name>javax.management.Notification</name>\n"
-" <notification-type>org.jboss.chap2.xmbean.JNDIMap.put</"
+" <notification-type>org.jboss.book.jmx.xmbean.JNDIMap.put</"
"notification-type>\n"
" </notification>\n"
"</mbean>"
@@ -8224,7 +8212,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1819
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples]$ ant -Dchap=jmx -Dex=xmbean2 -Djboss.deploy.conf=default run-"
"example\n"
@@ -8271,8 +8259,8 @@
"timeStamp=1098632\n"
"693925,message=null,userData=null]"
msgstr ""
-"[examples]$ ant -Dchap=chap2 -Dex=xmbean2 -Djboss.deploy.conf=rmi-adaptor "
-"run-example\n"
+"[examples]$ ant -Dchap=jmx -Dex=xmbean2 -Djboss.deploy.conf=default run-"
+"example\n"
"...\n"
"run-examplexmbean2:\n"
" [java] JNDIMap Class: org.jboss.mx.modelmbean.XMBean\n"
@@ -8290,27 +8278,27 @@
" [java] + [Ljava.lang.String; getInitialValues()\n"
" [java] + void setInitialValues([Ljava.lang.String; chap2.xmbean:"
"service=JNDIMap)\n"
-" [java] handleNotification，event: null\n"
-" [java] key=key10，value=value10\n"
-" [java] handleNotification，event: javax.management.Notification"
+" [java] handleNotification, event: null\n"
+" [java] key=key10, value=value10\n"
+" [java] handleNotification, event: javax.management.Notification"
"[source=chap2.xmbean:s\n"
"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.put,sequenceNumber=7,"
"timeStamp=10986326\n"
"93716,message=null,userData=null]\n"
-" [java] JNDIMap.put(key1，value1) successful\n"
-" [java] handleNotification，event: javax.management.Notification"
+" [java] JNDIMap.put(key1, value1) successful\n"
+" [java] handleNotification, event: javax.management.Notification"
"[source=chap2.xmbean:s\n"
"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.get,sequenceNumber=8,"
"timeStamp=10986326\n"
"93857,message=null,userData=null]\n"
" [java] JNDIMap.get(key0): null\n"
-" [java] handleNotification，event: javax.management.Notification"
+" [java] handleNotification, event: javax.management.Notification"
"[source=chap2.xmbean:s\n"
"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.get,sequenceNumber=9,"
"timeStamp=10986326\n"
"93896,message=null,userData=null]\n"
" [java] JNDIMap.get(key1): value1\n"
-" [java] handleNotification，event: javax.management.Notification"
+" [java] handleNotification, event: javax.management.Notification"
"[source=chap2.xmbean:s\n"
"ervice=JNDIMap,type=org.jboss.chap2.xmbean.JNDIMap.put,sequenceNumber=10,"
"timeStamp=1098632\n"
@@ -8330,21 +8318,21 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1824
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples] ant -Dchap=jmx -Dex=xmbean2a run-example\n"
"...\n"
" [java] InitialValues.length=2\n"
" [java] key=key10, value=value10"
msgstr ""
-"[examples] ant -Dchap=chap2 -Dex=xmbean2a run-example\n"
+"[examples] ant -Dchap=jmx -Dex=xmbean2a run-example\n"
"...\n"
" [java] InitialValues.length=2\n"
-" [java] key=key10，value=value10"
+" [java] key=key10, value=value10"
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1825
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples] ant -Dchap=jmx -Dex=xmbean2a run-example\n"
"...\n"
@@ -8352,15 +8340,15 @@
" [java] key=key10, value=value10\n"
" [java] key=key2, value=value2"
msgstr ""
-"[examples] ant -Dchap=chap2 -Dex=xmbean2a run-example\n"
+"[examples] ant -Dchap=jmx -Dex=xmbean2a run-example\n"
"...\n"
" [java] InitialValues.length=4\n"
-" [java] key=key10，value=value10\n"
-" [java] key=key2，value=value2"
+" [java] key=key10, value=value10\n"
+" [java] key=key2, value=value2"
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1828
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples] ant -Dchap=jmx -Dex=xmbean2a run-example\n"
"...\n"
@@ -8369,24 +8357,24 @@
" [java] key=key2, value=value2\n"
" [java] key=key3, value=value3"
msgstr ""
-"[examples] ant -Dchap=chap2 -Dex=xmbean2a run-example\n"
+"[examples] ant -Dchap=jmx -Dex=xmbean2a run-example\n"
"...\n"
" [java] InitialValues.length=6\n"
-" [java] key=key10，value=value10\n"
-" [java] key=key2，value=value2\n"
-" [java] key=key3，value=value3"
+" [java] key=key10, value=value10\n"
+" [java] key=key2, value=value2\n"
+" [java] key=key3, value=value3"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1830
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>org.jboss.book.jmx.xmbean.TestXMBeanRestart</literal> used in "
"this example obtains the current <literal>InitialValues</literal> attribute "
"setting, and then adds another key/value pair to it. The client code is "
"shown below."
msgstr ""
-"这个例子里使用的<literal>org.jboss.chap2.xmbean.TestXMBeanRestart</literal>获"
-"取了当前的<literal>InitialValues</literal>属性设置，然后加入了另外一对key/"
+"这个例子里使用的 <literal>org.jboss.book.jmx.xmbean.TestXMBeanRestart</literal> 获"
+"取了当前的 <literal>InitialValues</literal> 属性设置，然后加入了另外一对 key/"
"value。下面是客户端的代码。"
#. Tag: programlisting
@@ -8675,7 +8663,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1852
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"When a component archive is deployed, its nested deployment units are "
"processed in a depth first ordering. Structuring of components into an "
@@ -8687,12 +8675,12 @@
msgstr ""
"当部署一个组件档案时，它的嵌套部署单元由深度优先(depth first)顺序来处理。把组"
"件构造到一个档案层次里是另外一个管理部署顺序的方法。如果包结构没有解析依赖性"
-"的话，你将需要显性地说明你的MBean依赖性。让我们考虑一个组件部署的例子，它由一"
-"个使用EJB的MBean组成。这里是EAR示例的结构。"
+"的话，你将需要显性地说明你的 MBean 依赖性。让我们考虑一个组件部署的例子，它由一"
+"个使用 EJB 的 MBean 组成。这里是一个 EAR 示例的结构。"
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1855
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">output/jmx/jmx-ex3.ear</emphasis>\n"
"+- META-INF/MANIFEST.MF\n"
@@ -8709,24 +8697,24 @@
"| +- org/jboss/book/jmx/ex3/EjbMBeanAdaptor.class\n"
"+- META-INF/application.xml"
msgstr ""
-"<emphasis role=\"bold\">output/chap2/chap2-ex3.ear</emphasis>\n"
+"<emphasis role=\"bold\">output/jmx/jmx-ex3.ear</emphasis>\n"
"+- META-INF/MANIFEST.MF\n"
"+- META-INF/jboss-app.xml\n"
-"+- chap2-ex3.jar (archive) [EJB jar]\n"
+"+- jmx-ex3.jar (archive) [EJB jar]\n"
"| +- META-INF/MANIFEST.MF\n"
"| +- META-INF/ejb-jar.xml\n"
-"| +- org/jboss/chap2/ex3/EchoBean.class\n"
-"| +- org/jboss/chap2/ex3/EchoLocal.class\n"
-"| +- org/jboss/chap2/ex3/EchoLocalHome.class\n"
-"+- chap2-ex3.sar (archive) [MBean sar]\n"
+"| +- org/jboss/book/jmx/ex3/EchoBean.class\n"
+"| +- org/jboss/book/jmx/ex3/EchoLocal.class\n"
+"| +- org/jboss/book/jmx/ex3/EchoLocalHome.class\n"
+"+- jmx-ex3.sar (archive) [MBean sar]\n"
"| +- META-INF/MANIFEST.MF\n"
"| +- META-INF/jboss-service.xml\n"
-"| +- org/jboss/chap2/ex3/EjbMBeanAdaptor.class\n"
+"| +- org/jboss/book/jmx/ex3/EjbMBeanAdaptor.class\n"
"+- META-INF/application.xml"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1856
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The EAR contains a <literal>jmx-ex3.jar</literal> and <literal>jmx-ex3.sar</"
"literal>. The <literal>jmx-ex3.jar</literal> is the EJB archive and the "
@@ -8734,10 +8722,8 @@
"implemented the service as a Dynamic MBean to provide an illustration of "
"their use."
msgstr ""
-"这个EAR包含<literal>chap2-ex3.jar</literal> 和 <literal>chap2-ex3.sar</"
-"literal>。<literal>chap2-ex3.jar</literal>是EJB档案，<literal>chap2-ex3.sar</"
-"literal>是MBean服务档案文件。我们已经把这个服务实现为Dynamic MBean，来提供了"
-"它们的使用说明。"
+"这个 EAR 包含 <literal>jmx-ex3.jar</literal> 和 <literal>jmx-ex3.sar</"
+"literal>。<literal>jmx-ex3.jar</literal> 是 EJB 归档，<literal>jmx-ex3.sar</literal> 是 MBean 服务归档文件。我们已经把这个服务实现为 Dynamic MBean 来提供它们的使用说明。"
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1859
@@ -9490,7 +9476,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1867
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Moving to lines 67-83, this is where the MBean operation metadata is "
"constructed. The <literal>echo(String)</literal>, <literal>create()</"
@@ -9508,15 +9494,14 @@
"with the attribute metadata. This is not something you can do with a static "
"interface."
msgstr ""
-"回到67—83行，这里是MBean操作元数据构造的地方。<literal>echo(String)</"
+"回到 67—83行，这里是 MBean 操作元数据构造的地方。<literal>echo(String)</"
"literal>，<literal>create()</literal>，<literal>start()</literal>，"
-"<literal>stop()</literal> 和<literal>destroy()</literal>操作通过获取相应的"
-"java.lang.reflect.Method对象和加入描述来定义。让我们遍历这段代码，讨论这个接"
-"口实现在什么地方，而且MBean怎么使用EJB。从40-51行开始，创建的两个"
-"<literal>MBeanAttributeInfo</literal>实例定义了MBean的属性。这些属性对应静态"
+"<literal>stop()</literal> 和 <literal>destroy()</literal> 操作通过获取相应的 java.lang.reflect.Method 对象和加入描述来定义。让我们遍历这段代码，讨论这个接"
+"口实现在什么地方，而且 MBean 怎么使用 EJB。从 40-51 行开始，创建的两个"
+" <literal>MBeanAttributeInfo</literal> 实例定义了 MBean 的属性。这些属性对应静态"
"接口的<literal>getHelloPrefix</literal>/<literal>setHelloPrefix</literal> 和 "
"<literal>getEjbJndiName</literal>/<literal>setEjbJndiName</literal>。这里我们"
-"可以看到为什么有人愿意使用Dynamic MBean：因为你可以把属性元数据和描述性文本关"
+"可以看到为什么有人愿意使用 Dynamic MBean：因为你可以把属性元数据和描述性文本关"
"联起来。如果使用静态接口，你就做不到这点。"
#. Tag: para
@@ -9643,7 +9628,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1891
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<server>\n"
" <mbean code=\"org.jboss.book.jmx.ex3.EjbMBeanAdaptor\"\n"
@@ -9658,13 +9643,13 @@
"</server>"
msgstr ""
"<server>\n"
-" <mbean code=\"org.jboss.chap2.ex3.EjbMBeanAdaptor\"\n"
+" <mbean code=\"org.jboss.book.jmx.ex3.EjbMBeanAdaptor\"\n"
" name=\"jboss.book:service=EjbMBeanAdaptor\">\n"
" <attribute name=\"HelloPrefix\">AdaptorPrefix</"
"attribute>\n"
-" <attribute name=\"EjbJndiName\">local/chap2.EchoBean</"
+" <attribute name=\"EjbJndiName\">local/j2ee_chap2.EchoBean</"
"attribute>\n"
-" <depends>jboss.j2ee:service=EJB,jndiName=local/chap2."
+" <depends>jboss.j2ee:service=EJB,jndiName=local/j2ee_chap2."
"EchoBean</depends>\n"
" </mbean>\n"
"</server>"
@@ -9677,9 +9662,9 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1895
-#, fuzzy, no-c-format
+#, no-c-format
msgid "[examples]$ ant -Dchap=jmx -Dex=3 run-example"
-msgstr "[examples]$ ant -Dchap=chap2 -Dex=3 run-example"
+msgstr "[examples]$ ant -Dchap=jmx -Dex=3 run-example"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1896
@@ -9835,7 +9820,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1900
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The stack traces are not exceptions. They are traces coming from the "
"<literal>EjbMBeanAdaptor</literal> code to demonstrate that clients ask for "
@@ -9845,12 +9830,12 @@
msgstr ""
"这里的堆栈跟踪信息不是异常(exceptions)。它们来自 <literal>EjbMBeanAdaptor</"
"literal> 代码的第 150 行，演示了当客户端想探索 MBean 的能力时请求 MBean 接"
-"口。注意 MBean 容器(有 [EjbModule] 的行)是在 example MBean (有 "
-"[EjbMBeanAdaptor] 的行)之前启动的。 "
+"口。注意 MBean 容器(有 [EjbModule] 的行)是在 example MBean（有 "
+"[EjbMBeanAdaptor] 的行）之前启动的。 "
#. Tag: para
#: J2EE_Reference_Introduction.xml:1903
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Now, let's invoke the echo method using the JMX console web application. "
"Go to the JMX Console (<ulink url=\"http://localhost:8080/jmx-console\"></"
@@ -9863,8 +9848,8 @@
"现在，让我们用 JMX 控制台 web 程序来调用 echo 方法。来到 JMX 控制台(<ulink "
"url=\"http://localhost:8080/jmx-console\"></ulink>)并找到 <emphasis>jboss."
"book</emphasis> 域里的 <emphasis>service=EjbMBeanAdaptor</emphasis>。点击这个"
-"链接并往下滚动到 <emphasis>echo</emphasis> 操作部分。你应该看到如 <xref "
-"linkend=\"ch2.ejbadaptor.fig\"/> 所示的视图。"
+"链接并往下滚动到 <emphasis>echo</emphasis> 操作部分。你应该看到如 <xref linkend=\"Deployment_Ordering_and_Dependencies-"
+"The_EjbMBeanAdaptor_MBean_operations_JMX_console_view\"/> 所示的视图。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1907
@@ -9890,7 +9875,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1917
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"10:51:48,671 INFO [EjbMBeanAdaptor] Begin invoke, actionName=echo\n"
"10:51:48,671 INFO [EjbMBeanAdaptor] Lookup EchoLocalHome at local/j2ee_chap2."
@@ -9899,12 +9884,12 @@
"10:51:48,687 INFO [EjbMBeanAdaptor] Result: AdaptorPrefix-echo-arg\n"
"10:51:48,687 INFO [EjbMBeanAdaptor] End invoke, actionName=echo"
msgstr ""
-"10:51:48,671 INFO [EjbMBeanAdaptor] Begin invoke，actionName=echo\n"
-"10:51:48,671 INFO [EjbMBeanAdaptor] Lookup EchoLocalHome at local/chap2."
+"10:51:48,671 INFO [EjbMBeanAdaptor] Begin invoke, actionName=echo\n"
+"10:51:48,671 INFO [EjbMBeanAdaptor] Lookup EchoLocalHome at local/j2ee_chap2."
"EchoBean\n"
-"10:51:48,687 INFO [EchoBean] echo，info=echo info，arg=，arg=-echo-arg\n"
+"10:51:48,687 INFO [EchoBean] echo, info=echo info, arg=, arg=-echo-arg\n"
"10:51:48,687 INFO [EjbMBeanAdaptor] Result: AdaptorPrefix-echo-arg\n"
-"10:51:48,687 INFO [EjbMBeanAdaptor] End invoke，actionName=echo"
+"10:51:48,687 INFO [EjbMBeanAdaptor] End invoke, actionName=echo"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1923
@@ -10139,7 +10124,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1995
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Deployers are the mechanism by which components are brought into a JBoss "
"server. Deployers are also the creators of the majority of UCL instances, "
@@ -10162,7 +10147,8 @@
"顶端的 <literal>DeploymentInfo</literal> 才实际上创建 UCL。所有的子部署者将把"
"它们的 class paths 加入到父 <literal>DeploymentInfo</literal> UCL里。每个部署"
"都有一个独立的 URLClassLoader，它把部署 URL 作为它的路径。这被用来使资源的载"
-"入本地化，如部署描述符。<xref linkend=\"ch2.earclassloader.fig\"/> 说明了部署"
+"入本地化，如部署描述符。<xref linkend=\"Deployers_and_ClassLoaders-"
+"An_illustration_of_the_class_loaders_involved_with_an_EAR_deployment\"/> 说明了部署"
"者，DeploymentInfos 和 类加载器之间的相互作用。"
#. Tag: title
@@ -10173,7 +10159,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2006
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The figure illustrates an EAR deployment with EJB and WAR subdeployments. "
"The EJB deployment references the <literal>lib/util.jar</literal> utility "
@@ -10258,7 +10244,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2021
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Let's begin our discussion of the detached invoker architecture with an "
"overview of the components involved. The main components in the detached "
@@ -10267,7 +10253,9 @@
"The_main_components_in_the_detached_invoker_architecture\"/>."
msgstr ""
"让我们开始讨论脱管调用者架构和它所涉及的组件吧。脱管调用者架构里的主要组件如 "
-"<xref linkend=\"ch2.dinv.fig\"/> 所示。"
+"<xref linkend="
+"\"Remote_Access_to_Services_Detached_Invokers-"
+"The_main_components_in_the_detached_invoker_architecture\"/> 所示。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:2025
@@ -10277,7 +10265,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2032
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"On the client side, there exists a client proxy which exposes the interface"
"(s) of the MBean service. This is the same smart, compile-less dynamic proxy "
@@ -10298,12 +10286,13 @@
"态代理，和我们用在 EJB home 和 remote 接口上的相同。唯一的区别就是开放的接口"
"集和代理内部的客户端拦截器。客户端拦截器由客户代理内部的矩形来表示。拦截器是"
"一种装配线?的模式，它允许方法调用和/或返回值的传输。客户通过某种查找机制获得"
-"一个代理，如 JNDI。虽然 <xref linkend=\"ch2.dinv.fig\"/> 里指出了 RMI，但开放"
-"接口和类型的真正要求是，它们在 JNDI 和传输层上的客户服务器之间是可串形化的。"
+"一个代理，如 JNDI。虽然 <xref linkend=\"Remote_Access_to_Services_Detached_Invokers-"
+"The_main_components_in_the_detached_invoker_architecture\"/> 里指出了 RMI，但开放"
+"接口和类型的真正要求是，它们在 JNDI 和传输层上的客户服务器之间是可序列化的。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:2035
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The choice of the transport layer is determined by the last interceptor in "
"the client proxy, which is referred to as the <emphasis>Invoker Interceptor</"
@@ -10316,12 +10305,12 @@
"is the case the call is passed to a call-by-reference invoker that simply "
"passes the invocation along to the target MBean."
msgstr ""
-"传输层的选择是由客户代理里最后的拦截器决定的，在 <xref linkend=\"ch2.dinv.fig"
-"\"/> 里它被称作 <emphasis>Invoker Interceptor</emphasis>。调用者拦截器"
+"传输层的选择是由客户代理里最后的拦截器决定的，在 <xref linkend=\"Remote_Access_to_Services_Detached_Invokers-"
+"The_main_components_in_the_detached_invoker_architecture\"/> 里它被称作 <emphasis>Invoker Interceptor</emphasis>。调用者拦截器"
"(invoker interceptor)包含了服务端 <emphasis>Detached Invoker</emphasis> "
"MBean 服务的特定传输 stub 的引用。调用者拦截器也处理和目标 MBean 相同的虚拟机"
-"内发生的调用的优化。当调用者拦截器检测到调用被传递到一个引用调用(call-by-"
-"reference)的调用者时，它简单地把这个调用传递到目标 MBean。，"
+"内发生的调用的优化。当调用者拦截器检测到调用被传递到一个引用调用（call-by-"
+"reference）的调用者时，它简单地把这个调用传递到目标 MBean。，"
#. Tag: para
#: J2EE_Reference_Introduction.xml:2038
@@ -10337,7 +10326,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:2041
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"package org.jboss.invocation;\n"
" \n"
@@ -10357,25 +10346,25 @@
"}"
msgstr ""
"package org.jboss.invocation;\n"
-" \n"
+" \n"
"import java.rmi.Remote;\n"
"import org.jboss.proxy.Interceptor;\n"
"import org.jboss.util.id.GUID;\n"
-" \n"
-" \n"
+" \n"
+" \n"
"public interface Invoker\n"
" extends Remote\n"
"{\n"
" GUID ID = new GUID();\n"
"\n"
" String getServerHostName() throws Exception;\n"
-" \n"
+"\n"
" Object invoke(Invocation invocation) throws Exception;\n"
"}"
#. Tag: para
#: J2EE_Reference_Introduction.xml:2042
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The Invoker interface extends <literal>Remote</literal> to be compatible "
"with RMI, but this does not mean that an invoker must expose an RMI service "
@@ -10392,9 +10381,10 @@
"调用者接口把 <literal>Remote</literal> 扩展为和 RMI 兼容，但这不意味着调用者"
"必须开放一个 RMI 服务 stub。脱管调用者服务简单地担任一个传输网关，它接受它特"
"定的传输上的以 <literal>org.jboss.invocation.Invocation</literal> 对象代表的"
-"调用，将这个调用解包(unmarshall)，把这个调用转发到如 <xref linkend=\"ch2."
-"dinv.fig\"/> 里的 <emphasis>Target MBean</emphasis> 代表的目的 MBean 服务，然"
-"后将转发调用的返回值或者是异常结果打包(marshall)给客户端。"
+"调用，将这个调用解包（unmarshall），把这个调用转发到如 <xref linkend="
+"\"Remote_Access_to_Services_Detached_Invokers-"
+"The_main_components_in_the_detached_invoker_architecture\"/> 里的 <emphasis>Target MBean</emphasis> 代表的目的 MBean 服务，然"
+"后将转发调用的返回值或者是异常结果打包（marshall）给客户端。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:2045
@@ -10412,7 +10402,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2048
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The configuration of the client proxy is done by the server side proxy "
"factory MBean service, indicated by the <emphasis>Proxy Factory</emphasis> "
@@ -10420,7 +10410,8 @@
"The_main_components_in_the_detached_invoker_architecture\"/>. The proxy "
"factory performs the following tasks:"
msgstr ""
-"如 <xref linkend=\"ch2.dinv.fig\"/> 里的 <emphasis>Proxy Factory</emphasis> "
+"如 <xref linkend=\"Remote_Access_to_Services_Detached_Invokers-"
+"The_main_components_in_the_detached_invoker_architecture\"/> 里的 <emphasis>Proxy Factory</emphasis> "
"组件所指出的那样，客户代理的配置由服务器端 proxy factory MBean 服务来完成。"
"proxy factory 执行下面的任务："
@@ -10456,7 +10447,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2073
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The last component in <xref linkend="
"\"Remote_Access_to_Services_Detached_Invokers-"
@@ -10465,7 +10456,9 @@
"for invocations to remote clients. The steps required for an MBean service "
"to be accessible through a given interface are:"
msgstr ""
-"<xref linkend=\"ch2.dinv.fig\"/> 里的最后的组件是 <emphasis>Target MBean</"
+"<xref linkend="
+"\"Remote_Access_to_Services_Detached_Invokers-"
+"The_main_components_in_the_detached_invoker_architecture\"/> 里的最后的组件是 <emphasis>Target MBean</"
"emphasis> 服务，它希望为对远程客户的调用开放一个接口。MBean 服务通过给定接口"
"而成为可访问的所需的步骤是："
@@ -10840,7 +10833,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2103
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Let's go through the key details of this service. The "
"<literal>InvokerAdaptorServiceMBean</literal> Standard MBean interface of "
@@ -10862,7 +10855,7 @@
"接口类型的自定义。它得和 <literal>MBeanServer</literal> 类兼容，如方法名和签"
"名。<literal>invoke(Invocation)</literal> 操作是被要求的入口，目标 MBean 服务"
"必须开放它来遵循脱管调用者模式。这个操作被脱管调用者服务调用，这些服务已经被"
-"配置好来提供对 <literal>InvokerAdaptorService</literal> 的访问。"
+"配置好来提供对 <literal>InvokerAdaptorService</literal> 的访问。 "
#. Tag: para
#: J2EE_Reference_Introduction.xml:2106
@@ -10913,7 +10906,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2112
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Lines 77-93 obtain the name of the MBean on which the MBeanServer operation "
"is being performed and lookup the class loader associated with the MBean'"
@@ -10928,7 +10921,7 @@
"MBean 的 SAR 部署关联的类加载器。通过 JBoss JMX 实现的一个特定的类，"
"<literal>org.jboss.mx.server.registry.BasicMBeanRegistry</literal>，可以获得"
"这个信息。这对于建立正确的类加载上下文的 MBean 来说，通常是必需的。因为脱管调"
-"用者协议层可能不能访问用来将和调用关联的类型解包(unmarshall)的类加载器。"
+"用者协议层可能不能访问用来将和调用关联的类型解包（unmarshall）的类加载器。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:2115
@@ -11012,7 +11005,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2133
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Now let's take a look at how the <literal>InvokerAdaptorService</"
"literal> may be used to expose the same <literal>org.jboss.jmx.adaptor.rmi."
@@ -11030,8 +11023,10 @@
"<literal>InvokerAdaptorService</literal> 来开放相同的 <literal>org.jboss.jmx."
"adaptor.rmi.RMIAdaptor</literal> 接口。我们从 <literal>jmx-invoker-adaptor-"
"service.sar</literal> 部署的缺省设置里找到的 proxy factory 和 "
-"<literal>InvokerAdaptorService</literal> 配置开始。<xref linkend=\"ch2."
-"jmxinvokersar.ex\"/> 展示了这个部署的 <literal>jboss-service.xml</literal> 描"
+"<literal>InvokerAdaptorService</literal> 配置开始。<xref linkend="
+"\"A_Detached_Invoker_Example_the_MBeanServer_Invoker_Adaptor_Service-"
+"The_default_jmx_invoker_adaptor_server.sar_jboss_service."
+"xml_deployment_descriptor\"/> 展示了这个部署的 <literal>jboss-service.xml</literal> 描"
"述符。"
#. Tag: title
@@ -11046,7 +11041,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:2137
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<server>\n"
" <!-- The JRMP invoker proxy configuration for the "
@@ -11126,10 +11121,10 @@
" </iterceptors>\n"
" </attribute>\n"
" <depends>jboss:service=invoker,type=jrmp</depends>\n"
-" </mbean> \n"
+" </mbean> \n"
" <!-- This is the service that handles the RMIAdaptor invocations by "
"routing\n"
-" them to the MBeanServer the service is deployed under。-->\n"
+" them to the MBeanServer the service is deployed under. -->\n"
" <mbean code=\"org.jboss.jmx.connector.invoker.InvokerAdaptorService"
"\" \n"
" name=\"jboss.jmx:type=adaptor,name=Invoker\">\n"
@@ -11140,7 +11135,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2138
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The first MBean, <literal>org.jboss.invocation.jrmp.server.JRMPProxyFactory</"
"literal>, is the proxy factory MBean service that creates proxies for the "
@@ -11167,7 +11162,7 @@
"器：<literal>ClientMethodInterceptor</literal>，"
"<literal>InvokerAdaptorClientInterceptor</literal>，"
"<literal>InvokerInterceptor</literal>。<literal>InvokerAdaptorService</"
-"literal> 的配置简单地设置了这个服务所开放的 RMIAdaptor 接口。"
+"literal> 的配置简单地设置了这个服务所开放的 RMIAdaptor 接口。 "
#. Tag: para
#: J2EE_Reference_Introduction.xml:2141
@@ -11478,7 +11473,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:2254
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>org.jboss.invocation.iiop.IIOPInvoker</literal> class is an "
"MBean service that provides the RMI/IIOP implementation of the "
@@ -11496,13 +11491,13 @@
"<literal>org.jboss.invocation.iiop.IIOPInvoker</literal> 类是一个 MBean 服"
"务，它提供 <literal>Invoker</literal> 的 RMI/IIOP 实现。"
"<literal>IIOPInvoker</literal> 把 IIOP 请求指引到 CORBA servants。这被 "
-"<literal>org.jboss.proxy.ejb.IORFactory</literal> proxy factory 用来创建 RMI/"
+"<literal>org.jboss.proxy.ejb.IORFactory</literal> 代理工厂用来创建 RMI/"
"IIOP 代理。然而，还个 factory 创建 CORBA IORs，而不是 Java 代理 (如 JRMP "
"proxy factory 所为)。<literal>IORFactory</literal> 与给定的企业级 bean 相关"
"联。它在 IIOP 调用者上注册了两个 CORBA servants：用于 bean 的 "
"<literal>EJBHome</literal> 的 <literal>anEjbHomeCorbaServant</literal> 和用"
"于 bean 的 <literal>EJBObject</literal> 的 <literal>EjbObjectCorbaServant</"
-"literal>。"
+"literal>。 "
#. Tag: para
#: J2EE_Reference_Introduction.xml:2257
@@ -11899,7 +11894,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:2417
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"import java.lang.reflect.Method;\n"
"import java.util.HashMap;\n"
@@ -11918,15 +11913,15 @@
"import java.lang.reflect.Method;\n"
"import java.util.HashMap;\n"
"import org.jboss.invocation.MarshalledInvocation;\n"
-" \n"
+"\n"
"HashMap marshalledInvocationMapping = new HashMap();\n"
-" \n"
+"\n"
"// Build the Naming interface method map\n"
"Method[] methods = SRPRemoteServerInterface.class.getMethods();\n"
"for(int m = 0; m < methods.length; m ++) {\n"
" Method method = methods[m];\n"
" Long hash = new Long(MarshalledInvocation.calculateHash(method));\n"
-" marshalledInvocationMapping.put(hash，method);\n"
+" marshalledInvocationMapping.put(hash, method);\n"
"}"
#. Tag: para
@@ -11951,7 +11946,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:2424
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"import org.jboss.invocation.Invocation;\n"
"import org.jboss.invocation.MarshalledInvocation;\n"
@@ -11987,7 +11982,7 @@
msgstr ""
"import org.jboss.invocation.Invocation;\n"
"import org.jboss.invocation.MarshalledInvocation;\n"
-" \n"
+"\n"
"public Object invoke(Invocation invocation)\n"
" throws Exception\n"
"{\n"
@@ -12004,16 +11999,16 @@
" Object[] args = invocation.getArguments();\n"
" Object value = null;\n"
" try {\n"
-" value = method.invoke(theServer，args);\n"
+" value = method.invoke(theServer, args);\n"
" } catch(InvocationTargetException e) {\n"
" Throwable t = e.getTargetException(); \n"
" if (t instanceof Exception) {\n"
" throw (Exception) e;\n"
" } else {\n"
-" throw new UndeclaredThrowableException(t，method.toString());\n"
+" throw new UndeclaredThrowableException(t, method.toString());\n"
" }\n"
" }\n"
-" \n"
+"\n"
" return value;\n"
"}"
More information about the jboss-cvs-commits
mailing list