[jboss-cvs] JBossAS SVN: r84657 - 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 Feb 23 19:56:24 EST 2009
Author: xhuang at jboss.com
Date: 2009-02-23 19:56:24 -0500 (Mon, 23 Feb 2009)
New Revision: 84657
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-02-24 00:55:36 UTC (rev 84656)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Reference_Introduction.po 2009-02-24 00:56:24 UTC (rev 84657)
@@ -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-23 12:20+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2009-02-24 10:56+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -1918,7 +1918,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:437
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The class <literal>C</literal> is defined by <literal>L1</literal> and so "
"<literal>L1</literal> is used to initiate loading of the classes "
@@ -1942,15 +1942,14 @@
"both the fully qualified name of the class and the defining class loader."
msgstr ""
"<literal>L1</literal>定义了<literal>C</literal>，所以<literal>L1</literal>被"
-"用来初始化<literal>C.f()</literal>方法里引用的<literal>Spoofed</literal>和 "
-"<literal>Delegated</literal>类的加载。虽然<literal>L1</literal>定义了"
+"用来初始化 <literal>C.f()</literal> 方法里引用的 <literal>Spoofed</literal> 和 <literal>Delegated</literal> 类的加载。虽然<literal>L1</literal>定义了"
"<literal>Spoofed</literal>类，但是因为<literal>L1</literal>委托了"
"<literal>L2</literal>，所以<literal>Delegated</literal>是由<literal>L2</"
"literal>定义的。既然<literal>L2</literal>定义了<literal>Delegated</literal>，"
"<literal>L2</literal>将被用来初始化<literal>Delegated.g()</literal>方法上下文"
"里的<literal>Spoofed</literal>的加载。在这个例子里，<literal>L1</literal> 和 "
-"<literal>L2</literal>都定义了不同版本的<literal>Spoofed</literal>，如<xref "
-"linkend=\"ch2.ldcon.ex\"/>结尾处所示。既然<literal>C.f()</literal>相信"
+"<literal>L2</literal>都定义了不同版本的<literal>Spoofed</literal>，如 <xref linkend=\"LinkageErrors___Making_Sure_You_Are_Who_You_Say_You_Are-"
+"Classes_demonstrating_the_need_for_loading_constraints\"/> 结尾处所示。既然<literal>C.f()</literal>相信"
"<literal>x</literal>是<literal><Spoofed,L1></literal>的一个实例，它能够"
"访问<literal>Delegated.g()</literal>返回的<literal><Spoofed,L2></"
"literal>的私有字段<literal>secret_value</literal>，这是由于1.1和更早版本的"
@@ -1958,7 +1957,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:440
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Java addresses this problem by generating loader constraints to validate "
"type consistency when the types being used are coming from different "
@@ -1983,22 +1982,17 @@
"literal> will result in a <literal>LinkageError</literal>."
msgstr ""
"为了解决这个问题，当被使用的类型来自于不同的defining类加载器时，Java通过生成"
-"加载器约束来确认类型一致性。对于例子<xref linkend=\"ch2.ldcon.ex\"/>，当"
-"<literal>C.f() </literal>方法的第一行指出类型<literal>Spoofed</literal>必须相"
-"同而不管<literal>Spoofed</literal>的加载是否由<literal>L1</literal>还是"
-"<literal>L2</literal>初始化时，虚拟机(VM)生成一个约束"
+"加载器约束来确认类型一致性。对于例子 <xref linkend="
+"\"LinkageErrors___Making_Sure_You_Are_Who_You_Say_You_Are-"
+"Classes_demonstrating_the_need_for_loading_constraints\"/>，当 <literal>C.f() </literal> 方法的第一行指出类型 <literal>Spoofed</literal> 必须相同而不管 <literal>Spoofed</literal> 的加载是否由 <literal>L1</literal> 还是 <literal>L2</literal> 初始化时，虚拟机(VM)生成一个约束"
"<literal>Spoofed<superscript>L1</superscript>=Spoofed<superscript>L2</"
-"superscript> </literal>。它不管是<literal>L1</literal> 还是 <literal>L2</"
-"literal>，甚至是其他的类加载器定义了<literal>Spoofed</literal>，它只关心只有"
-"一个<literal>Spoofed</literal>类被定义。如果<literal>L1</literal> 或者 "
-"<literal>L2</literal>已经定义了不同版本的<literal>Spoofed</literal>，执行这个"
-"检查时就会马上生成一个<literal>LinkageError</literal>。否则，这个约束将被记"
-"录，当<literal>Delegated.g()</literal>被执行的时候，任何试图装载重复版本的"
-"<literal>Spoofed</literal>都将导致<literal>LinkageError</literal>错误。M"
+"superscript> </literal>。它不管是 <literal>L1</literal> 还是 <literal>L2</"
+"literal>，甚至是其他的类加载器定义了 <literal>Spoofed</literal>，它只关心只有"
+"一个 <literal>Spoofed</literal> 类被定义。如果 <literal>L1</literal> 或者 <literal>L2</literal> 已经定义了不同版本的 <literal>Spoofed</literal>，执行这个检查时就会马上生成一个<literal>LinkageError</literal>。否则，这个约束将被记录，当 <literal>Delegated.g()</literal> 被执行的时候，任何试图装载重复版本的 <literal>Spoofed</literal> 都将导致 <literal>LinkageError</literal> 错误。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:443
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Now let's take a look at how a <literal>LinkageError</literal> can occur "
"with a concrete example. <xref linkend="
@@ -2006,9 +2000,10 @@
"A_concrete_example_of_a_LinkageError\"/> gives the example main class along "
"with the custom class loader used."
msgstr ""
-"让我们看一下在一个具体例子里<literal>LinkageError</literal>是怎样产生的。"
-"<xref linkend=\"ch2.linkerror.ex\"/>给出了所使用的 main class 和自定义类加载"
-"器的例子。"
+"让我们看一下在一个具体例子里 <literal>LinkageError</literal> 是怎样产生的。"
+"<xref linkend="
+"\"LinkageErrors___Making_Sure_You_Are_Who_You_Say_You_Are-"
+"A_concrete_example_of_a_LinkageError\"/> 给出了所使用的主要类和自定义类加载器的例子。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:446
@@ -2280,7 +2275,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:449
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The key component in this example is the <literal>URLClassLoader</literal> "
"subclass <literal>Ex0URLClassLoader</literal>. This class loader "
@@ -2304,21 +2299,22 @@
"The_ExIAEd_class_used_to_demonstrate_IllegalAccessException_due_to_duplicate_class_loaders"
"\"/>, and the constructor was:"
msgstr ""
-"这个例子里的关键部件是<literal>URLClassLoader</literal>的子类"
-"<literal>Ex0URLClassLoader</literal>。这个类加载器实现覆盖了缺省的父委托模型"
-"来允许<literal>ucl0</literal> 和 <literal>ucl1</literal>实例加载"
-"<literal>ExObj2</literal>类并设立从<literal>ucl0</literal> 到 <literal>ucl1</"
-"literal>的委托关系。在30和31行里，<literal>ucl0</literal> "
-"<literal>Ex0URLClassLoader</literal> 被用来加载<literal>ExCtx</literal> 和 "
-"<literal>ExObj2</literal> 类。在<literal>ExLE.main</literal>的第45行，"
+"这个例子里的关键部件是 <literal>URLClassLoader</literal> 的子类 <literal>Ex0URLClassLoader</literal>。这个类加载器实现覆盖了缺省的父委托模型"
+"来允许 <literal>ucl0</literal> 和 <literal>ucl1</literal> 实例加载"
+"<literal>ExObj2</literal> 类并设立从 <literal>ucl0</literal> 到 <literal>ucl1</"
+"literal> 的委托关系。在 30 和 31 行里，<literal>ucl0</literal> "
+"<literal>Ex0URLClassLoader</literal> 被用来加载 <literal>ExCtx</literal> 和 "
+"<literal>ExObj2</literal> 类。在 <literal>ExLE.main</literal> 的第45行，"
"<literal>ucl1</literal><literal>Ex0URLClassLoader</literal>被用来再次加载 "
"<literal>ExObj2</literal>类。这时<literal>ucl0</literal> 和 <literal>ucl1</"
"literal>类加载器已经定义了<literal>ExObj2</literal> 类。从<literal>ucl0</"
"literal>到<literal>ucl1</literal>的委托关系在51行通过<literal>ucl0."
"setDelegate(ucl1)</literal>方法调用被设立。最后，在<literal>ExLE.main</"
"literal>的第54行，<literal>ExCtx</literal>的实例通过用<literal>ucl0</literal>"
-"加载的类被创建。<literal>ExCtx</literal>类和<xref linkend=\"ch2.threeclasses."
-"ex\"/>里出现的一样，构造函数是："
+"加载的类被创建。<literal>ExCtx</literal>类和 <xref linkend="
+"\"IllegalAccessException___Doing_what_you_should_not-"
+"The_ExIAEd_class_used_to_demonstrate_IllegalAccessException_due_to_duplicate_class_loaders"
+"\"/> 里出现的一样，构造函数是："
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:452
@@ -2382,7 +2378,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:459
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"This generates a loading constraint of <literal>ExObj2<superscript>ucl0</"
"superscript> = ExObj2<superscript>ucl1</superscript></literal> since the "
@@ -2393,17 +2389,16 @@
"constraint will be violated and should generate a <literal>LinkageError</"
"literal> when run. Run the example using the following command:"
msgstr ""
-"既然<literal>ExObj2</literal>类型必须在<literal>ucl0</literal> and "
-"<literal>ucl1</literal>类加载器实例里保持一致性，这生成了一个"
+"既然 <literal>ExObj2</literal> 类型必须在 <literal>ucl0</literal> 和 <literal>ucl1</literal> 类加载器实例里保持一致性，这生成了一个"
"<literal>ExObj2<superscript>ucl0</superscript> = ExObj2<superscript>ucl1</"
"superscript> </literal>的加载约束。因为我们在设立委托关系前已经用"
-"<literal>ucl0</literal> 和<literal>ucl1</literal>加载了<literal>ExObj2</"
-"literal>，运行时将违反这个约束并产生<literal>LinkageError</literal>。用下面的"
+"<literal>ucl0</literal> 和 <literal>ucl1</literal> 加载了<literal>ExObj2</"
+"literal>，运行时将违反这个约束并产生 <literal>LinkageError</literal>。用下面的"
"命令运行这个例子："
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:462
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples]$ ant -Dchap=jmx -Dex=0e run-example\n"
"Buildfile: build.xml\n"
@@ -2425,25 +2420,25 @@
"[java] at java.lang.Class.newInstance(Class.java:303)\n"
"[java] at org.jboss.book.jmx.ex0.ExLE.main(ExLE.java:53)"
msgstr ""
-"[examples]$ ant -Dchap=chap2 -Dex=0e run-example\n"
+"[examples]$ ant -Dchap=jmx -Dex=0e run-example\n"
"Buildfile: build.xml\n"
"...\n"
-"[java] java.lang.LinkageError: loader constraints violated when linking org/"
-"jboss/chap2/ex0/E\n"
-"xObj2 class\n"
-"[java] at org.jboss.chap2.ex0.ExCtx.<init>(ExCtx.java:24)\n"
-"[java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native "
+"[java] java.lang.LinkageError: loader constraints violated when linking \n"
+" org/jboss/book/jmx/ex0/ExObj2 class\n"
+"[java] at org.jboss.book.jmx.ex0.ExCtx.<init>(ExCtx.java:24)\n"
+"[java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native "
"Method)\n"
-"[java] at sun.reflect.NativeConstructorAccessorImpl.newInstance"
-"(NativeConstructorAccessorImpl\n"
-".java:39)\n"
-"[java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance"
-"(DelegatingConstructorAcce\n"
-"ssorImpl.java:27)\n"
-"[java] at java.lang.reflect.Constructor.newInstance(Constructor.java:274)\n"
-"[java] at java.lang.Class.newInstance0(Class.java:308)\n"
-"[java] at java.lang.Class.newInstance(Class.java:261)\n"
-"[java] at org.jboss.chap2.ex0.ExLE.main(ExLE.java:53)"
+"[java] at sun.reflect.NativeConstructorAccessorImpl.newInstance"
+"(NativeConstructorAccessor\n"
+" Impl.java:39) \n"
+"[java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance"
+"(DelegatingConstructor\n"
+" AccessorImpl.java:27)\n"
+"[java] at java.lang.reflect.Constructor.newInstance(Constructor."
+"java:494)\n"
+"[java] at java.lang.Class.newInstance0(Class.java:350)\n"
+"[java] at java.lang.Class.newInstance(Class.java:303)\n"
+"[java] at org.jboss.book.jmx.ex0.ExLE.main(ExLE.java:53)"
#. Tag: para
#: J2EE_Reference_Introduction.xml:463
@@ -2451,19 +2446,17 @@
msgid ""
"As expected, a LinkageError is thrown while validating the loader "
"constraints required by line 24 of the <literal>ExCtx</literal> constructor."
-msgstr ""
-"如我们所期望的，当确认<literal>ExCtx</literal>构造函数的第24行里要求的加载器"
-"约束时，LinkageError 被抛出。"
+msgstr "如我们所期望的，当确认 <literal>ExCtx</literal> 构造函数的第 24 行里要求的加载器约束时，LinkageError 被抛出。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:467
#, no-c-format
msgid "Debugging Class Loading Issues"
-msgstr "Debugging Class Loading Issues"
+msgstr "调试类加载的问题"
#. Tag: para
#: J2EE_Reference_Introduction.xml:468
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Debugging class loading issues comes down to finding out where a class was "
"loaded from. A useful tool for this is the code snippet shown in <xref "
@@ -2471,9 +2464,8 @@
"Obtaining_debugging_information_for_a_Class\"/> taken from the org.jboss."
"util.Debug class of the book examples."
msgstr ""
-"Debugging class loading issues的目的是找出类是从什么地方加载的。本书例子的"
-"org.jboss.util.Debug类里的<xref linkend=\"ch2.debuginfo.ex\"/>所展示的代码片"
-"段是一个很有用的工具。"
+"调试类加载的问题需要找出类是从什么地方加载的。本书例子的"
+"org.jboss.util.Debug类里的<xref linkend=\"ch2.debuginfo.ex\"/> 所展示的代码片段是一个很有用的工具。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:471
@@ -2553,7 +2545,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:473
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Firstly, every Class object knows its defining <literal>ClassLoader</"
"literal> and this is available via the <literal>getClassLoader()</literal> "
@@ -2565,12 +2557,8 @@
"<literal>URLClassLoader</literal> you can also see the URLs used for class "
"and resource loading."
msgstr ""
-"关键的内容用黑体标出。第一个是每个Class 对象都知道它的defining "
-"<literal>ClassLoader</literal>和可以通过<literal>getClassLoader()</literal>方"
-"法来获得。 <literal>Class</literal>类型的作用域和我们在前面关于类转换异常，非"
-"法的访问异常和链接错误的内容里的一样。从<literal>ClassLoader</literal>里，你"
-"可以看到组成父委托的类加载器的层次。如果类加载器是一个"
-"<literal>URLClassLoader</literal>，你也可以看到用于类和资源加载的URLs."
+"首先，每个 Class 对象都知道它的 defining <literal>ClassLoader</literal> 和可以通过<literal>getClassLoader()</literal> 方法来获得。<literal>Class</literal>类型的作用域和我们在前面关于类转换异常，非法的访问异常和链接错误的内容里的一样。从 <literal>ClassLoader</literal> 里，你"
+"可以看到组成父委托的类加载器的层次。如果类加载器是一个 <literal>URLClassLoader</literal>，你也可以看到用于类和资源加载的 URL."
#. Tag: para
#: J2EE_Reference_Introduction.xml:476
@@ -2597,7 +2585,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:479
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Beyond that it may be useful to view the details of classes being loaded "
"into the JBoss server. You can enable verbose logging of the JBoss class "
@@ -2605,8 +2593,9 @@
"linkend=\"Debugging_Class_Loading_Issues-An_example_log4j."
"xml_configuration_fragment_for_enabling_verbose_class_loading_logging\"/>."
msgstr ""
-"如<xref linkend=\"ch2.log4j.ex\"/>所示，你可以用Log4j配置片段来启用JBoss类加"
-"载层的verbose logging。"
+"查看加载到 JBoss 服务器里类的细节是很有用的。如 <xref "
+"linkend=\"Debugging_Class_Loading_Issues-An_example_log4j."
+"xml_configuration_fragment_for_enabling_verbose_class_loading_logging\"/> 所示，你可以用 Log4j 配置片段来启用 JBoss 类加载层的详尽日志（verbose logging）模式。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:482
@@ -2675,15 +2664,17 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:493
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Now that we have the role of class loaders in the Java type system defined, "
"let's take a look at the JBoss class loading architecture. <xref linkend="
"\"Inside_the_JBoss_Class_Loading_Architecture-"
"The_core_JBoss_class_loading_components\"/>."
msgstr ""
-"既然我们已经了解了Java类型体系里的类加载器的地位，让我们看看JBoss的类加载架"
-"构。<xref linkend=\"ch2.loadarch.fig\"/>。"
+"既然我们已经了解了 Java 类型体系里的类加载器的作用，让我们看看 JBoss 的类加载架"
+"构。<xref linkend="
+"\"Inside_the_JBoss_Class_Loading_Architecture-"
+"The_core_JBoss_class_loading_components\"/>。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:497
@@ -2693,7 +2684,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:504
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The central component is the <literal>org.jboss.mx.loading."
"UnifiedClassLoader3</literal> (UCL) class loader. This is an extension of "
@@ -2710,15 +2701,10 @@
"system in more detail later in <xref linkend=\"Using_JMX_as_a_Microkernel-"
"JBoss_MBean_Services\"/>."
msgstr ""
-"<literal>org.jboss.mx.loading.UnifiedClassLoader3</literal> (UCL) class "
-"loader是中心部件。它是<literal>java.net.URLClassLoader</literal>的扩展，它覆"
-"盖(Overrides)了标准父委托模型来使用类和资源的共享库(repository)。这个共享库是"
-"<literal>org.jboss.mx.loading.UnifiedLoaderRepository3</literal>。每个UCL都和"
-"单个的<literal>UnifiedLoaderRepository3</literal>相关联，而"
-"<literal>UnifiedLoaderRepository3</literal>通常对应许多的UCL。为了加载类和资"
-"源，UCL可以有多个URL与之关联。部署者(Deployers)把顶级部署的UCL作为共享的类加"
-"载器，所有的部署档案文件都分配给这个类加载器。我们将会在后面的<xref linkend="
-"\"ch2.mbeanservice.sect\"/>里详细地讨论JBoss部署者和它们与类加载系统的关系。"
+"<literal>org.jboss.mx.loading.UnifiedClassLoader3</literal> (UCL) 类加载器是中心部件。它是<literal>java.net.URLClassLoader</literal> 的扩展，它覆盖了标准父委托模型来使用类和资源的共享库(repository)。这个共享库是 <literal>org.jboss.mx.loading.UnifiedLoaderRepository3</literal>。每 个UCL 都和单个的 <literal>UnifiedLoaderRepository3</literal> 相关联，而 <literal>UnifiedLoaderRepository3</literal> 通常对应许多的 UCL。为了加载类和资"
+"源，UCL 可以有多个 URL 与之关联。部署者(Deployer)把顶级部署的 UCL 作为共享的类加"
+"载器，所有的部署档案文件都分配给这个类加载器。我们将会在后面的 <xref linkend=\"Using_JMX_as_a_Microkernel-"
+"JBoss_MBean_Services\"/> 里详细地讨论 JBoss 部署者和它们与类加载系统的关系。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:507
@@ -2798,7 +2784,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:529
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Another useful source of information on classes is the "
"UnifiedLoaderRepository itself. This is an MBean that contains operations to "
@@ -2810,11 +2796,10 @@
"\"Viewing_Classes_in_the_Loader_Repository-"
"The_default_class_LoaderRepository_MBean_view_in_the_JMX_console\"/>."
msgstr ""
-"另外一个关于类的信息的有用资源就是UnifiedLoaderRepository自己。它是一个包含显"
-"示类和包信息的操作的MBean。缺省的库存在于标准的JMX名"
-"<literal>JMImplementation:name=Default,service=LoaderRepository</literal>下，"
-"它的MBean可以通过JMX控制台主页里的链接来访问。<xref linkend=\"ch2.loaderjmx."
-"fig\"/>展示了这个MBean的JMX控制台视图。"
+"另外一个关于类的信息的有用资源就是 UnifiedLoaderRepository 自己。它是一个包含显示类和包信息的操作的 MBean。缺省的库存在于标准的 JMX 名 <literal>JMImplementation:name=Default,service=LoaderRepository</literal> 下，"
+"它的 MBean 可以通过 JMX 控制台主页里的链接来访问。<xref linkend="
+"\"Viewing_Classes_in_the_Loader_Repository-"
+"The_default_class_LoaderRepository_MBean_view_in_the_JMX_console\"/> 展示了这个MBean的JMX控制台视图。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:533
@@ -4194,7 +4179,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1144
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"JBoss comes with its own implementation of a JMX HTML adaptor that allows "
"one to view the server's MBeans using a standard web browser. The "
@@ -4204,9 +4189,11 @@
"\"Inspecting_the_Server___the_JMX_Console_Web_Application-"
"The_JBoss_JMX_console_web_application_agent_view\"/>."
msgstr ""
-"JBoss带有自己的JMX HTML适配器的实现，它允许使用标准的web浏览器来查看服务器的"
-"MBean。控制台web应用程序的缺省URL是<ulink url=\"http://localhost:8080/jmx-"
-"console/\"></ulink>。你可以类似于<xref linkend=\"ch2.console1.fig\"/>的内容。"
+"JBoss 带有自己的 JMX HTML 适配器的实现，它允许使用标准的 web 浏览器来查看服务器的"
+"MBean。控制台 web 应用程序的缺省 URL 是<ulink url=\"http://localhost:8080/jmx-"
+"console/\"></ulink>。你可以看到类似于 <xref linkend="
+"\"Inspecting_the_Server___the_JMX_Console_Web_Application-"
+"The_JBoss_JMX_console_web_application_agent_view\"/> 的内容。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1148
@@ -4216,7 +4203,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1155
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The top view is called the agent view and it provides a listing of all "
"MBeans registered with the <literal>MBeanServer</literal> sorted by the "
@@ -4228,11 +4215,12 @@
"The_MBean_view_for_the_jboss.systemtypeServer_MBean\"/> shows the MBean view "
"for the <literal>jboss.system:type=Server</literal> MBean."
msgstr ""
-"顶层的视图被称作代理视图，它提供所有在<literal>MBeanServer</literal>注册的"
-"MBean的列表，并根据MBean的<literal>ObjectName</literal>的域名部分来排序。域名"
-"下面是该域名的MBean。当你选择其中一个MBean时，你将会进入MBean视图。它允许你查"
-"看和编辑MBean的属性以及调用操作。例如，<xref linkend=\"ch2.console2.fig\"/>展"
-"示了<literal>jboss.system:type=Server</literal>MBean的MBean视图。"
+"顶层的视图被称作代理视图，它提供所有在 <literal>MBeanServer</literal> 注册的 MBean 的列表，并根据 MBean 的 <literal>ObjectName</literal> 的域名部分来排序。域名"
+"下面是该域名的 MBean。当你选择其中一个 MBean 时，你将会进入该 MBean 视图。它允许你查"
+"看和编辑 MBean 的属性以及调用操作。例如，<xref "
+"linkend=\"Inspecting_the_Server___the_JMX_Console_Web_Application-"
+"The_MBean_view_for_the_jboss.systemtypeServer_MBean\"/> 展"
+"示了 <literal>jboss.system:type=Server</literal> MBean 的 MBean 视图。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1159
@@ -4263,7 +4251,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1171
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Since the JMX console web application is just a standard servlet, it may be "
"secured using standard J2EE role based security. The <literal>jmx-console."
@@ -4277,18 +4265,14 @@
"files are located in the <literal>server/production/conf/props</literal> "
"directory."
msgstr ""
-"既然JMX控制台应用程序是一个标准的servlet，它可以使用标准的J2EE基于角色的安全"
-"性。作为未封装的WAR部署的<literal>jmx-console.war</literal> 包括了快速启用简"
-"单用户名和密码访问限制的模板设定。如果你看一下<literal>server/default/"
-"deploy</literal>目录下的<literal>jmx-console.war</literal>，你会找到"
-"<literal>WEB-INF</literal>目录下的<literal>web.xml</literal> 和 "
-"<literal>jboss-web.xml</literal>描述符。<literal>jmx-console-roles."
-"properties</literal> 和 <literal>jmx-console-users.properties</literal> 都在"
-"<literal>server/default/conf/props</literal>目录下。"
+"既然 JMX 控制台应用程序是一个标准的 servlet，它可以使用标准的 J2EE 基于角色的安全"
+"性。作为未封装的 WAR 部署的 <literal>jmx-console.war</literal> 包括了快速启用简"
+"单用户名和密码访问限制的模板设定。如果你看一下 <literal>server/default/"
+"deploy</literal> 目录下的 <literal>jmx-console.war</literal>，你会找到 <literal>WEB-INF</literal> 目录下的 <literal>web.xml</literal> 和 <literal>jboss-web.xml</literal> 描述符。<literal>jmx-console-roles.properties</literal> 和 <literal>jmx-console-users.properties</literal> 都在 <literal>server/default/conf/props</literal> 目录下。"
#. Tag: para
#: J2EE_Reference_Introduction.xml:1174
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"By uncommenting the security sections of the <literal>web.xml</literal> and "
"<literal>jboss-web.xml</literal> descriptors as shown in <xref linkend="
@@ -4299,12 +4283,12 @@
"The username and password are determined by the <literal>admin=admin </"
"literal>line in the <literal>jmx-console-users.properties</literal> file."
msgstr ""
-"如果去掉<xref linkend=\"ch2.secureconsole.ex\"/>所展示的<literal>web.xml</"
-"literal> 和 <literal>jboss-web.xml</literal>描述符里安全性设置部分的注释，你"
-"可以启用基本的HTTP认证，只允许密码为<literal>admin</literal>的用户"
-"<literal>admin</literal>访问JMX控制台应用程序。用户名和密码由<literal>jmx-"
-"console-users.properties</literal>文件里的<literal>admin=admin </literal>行来"
-"决定。"
+"如果去掉 <xref linkend="
+"\"Securing_the_JMX_Console-The_jmx_console.war_web."
+"xml_descriptors_with_the_security_elements_uncommented.\"/> 所展示的 <literal>web.xml</"
+"literal> 和 <literal>jboss-web.xml</literal> 描述符里安全性设置部分的注释，你"
+"可以启用基本的 HTTP 认证，只允许密码为 <literal>admin</literal> 的用户 <literal>admin</literal> 访问JMX控制台应用程序。用户名和密码由 <literal>jmx-"
+"console-users.properties</literal> 文件里的 <literal>admin=admin </literal> 行来决定。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1177
@@ -4440,14 +4424,14 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1181
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Make these changes and then when you try to access the JMX Console URL, you "
"will see a dialog similar to that shown in <xref linkend="
"\"Securing_the_JMX_Console-The_JMX_Console_basic_HTTP_login_dialog.\"/>."
msgstr ""
-"做了这些修改后，当你试图访问JXM控制台URL时，你将看到和<xref linkend=\"ch2."
-"basicauth.fig\"/>相似的对话框。"
+"做了这些修改后，当你试图访问 JXM 控制台 URL 时，你将看到和 <xref linkend="
+"\"Securing_the_JMX_Console-The_JMX_Console_basic_HTTP_login_dialog.\"/> 相似的对话框。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1185
@@ -4457,14 +4441,14 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1192
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"You probably to use the properties files for securing access to the JMX "
"console application. To see how to properly configure the security settings "
"of web applications see <xref linkend=\"Security_on_JBoss\"/>."
msgstr ""
-"你可能使用属性文件来设定访问JMX控制台应用程序的安全性。关于怎样正确配置web应"
-"用程序的安全设置，请参考<xref linkend=\"ch8.chapter\"/>。"
+"你可能使用属性文件来设定访问 JMX 控制台应用程序的安全性。关于怎样正确配置 web 应"
+"用程序的安全设置，请参考 <xref linkend=\"Security_on_JBoss\"/>。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1200
@@ -4490,16 +4474,15 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1204
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"shows a client that makes use of the <literal>RMIAdaptor</literal> interface "
"to query the <literal>MBeanInfo</literal> for the <literal>JNDIView</"
"literal> MBean. It also invokes the MBean's <literal>list(boolean)</"
"literal> method and displays the result."
msgstr ""
-"展示了一个客户用<literal>RMIAdaptor</literal>接口来为<literal>JNDIView</"
-"literal> MBean查询<literal>MBeanInfo</literal>。它也调用了MBean的"
-"<literal>list(boolean)</literal>方法并显示最后的结果。"
+"展示了一个客户用 <literal>RMIAdaptor</literal> 接口来为 <literal>JNDIView</"
+"literal> MBean 查询 <literal>MBeanInfo</literal>。它也调用了 MBean 的 <literal>list(boolean)</literal> 方法并显示最后的结果。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1207
@@ -4509,7 +4492,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1208
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"public class JMXBrowser\n"
"{\n"
@@ -4606,7 +4589,7 @@
" }\n"
"\n"
" if (p < params.length-1) {\n"
-" System.out.print(','); \n"
+" System.out.print(','); \n"
" }\n"
" }\n"
" System.out.println(\")\");\n"
@@ -4615,7 +4598,7 @@
" // Invoke the list(boolean) op\n"
" String[] sig = {\"boolean\"};\n"
" Object[] opArgs = {Boolean.TRUE};\n"
-" Object result = server.invoke(name，\"list\"，opArgs，sig);\n"
+" Object result = server.invoke(name, \"list\", opArgs, sig);\n"
"\n"
" System.out.println(\"JNDIView.list(true) output:\\n\"+result);\n"
" }\n"
@@ -4631,7 +4614,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1212
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples]$ ant -Dchap=jmx -Dex=4 run-example\n"
"...\n"
@@ -4745,9 +4728,9 @@
"Ref)\n"
" [java] </pre>"
msgstr ""
-"[examples]$ ant -Dchap=chap2 -Dex=4 run-example\n"
+"[examples]$ ant -Dchap=jmx -Dex=4 run-example\n"
"...\n"
-" \n"
+" \n"
"run-example4:\n"
" [java] JNDIView Class: org.jboss.mx.modelmbean.XMBean\n"
" [java] JNDIView Operations: \n"
@@ -4785,7 +4768,7 @@
" [java] | +- HsqlDbRealm (class: org.jboss.security.plugins."
"SecurityDomainContext)\n"
" [java] +- timedCacheFactory (class: javax.naming.Context)\n"
-" [java] Failed to lookup: timedCacheFactory，errmsg=null\n"
+" [java] Failed to lookup: timedCacheFactory, errmsg=null\n"
" [java] +- TransactionPropagationContextExporter (class: org.jboss.tm."
"TransactionPropag\n"
"ationContextFactory)\n"
@@ -4885,7 +4868,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1220
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[bin]$ ./twiddle.sh -h\n"
"A JMX client to 'twiddle' with a remote JBoss server.\n"
@@ -4904,20 +4887,20 @@
" -q, --quiet Be somewhat more quiet"
msgstr ""
"[bin]$ ./twiddle.sh -h\n"
-"A JMX client to 'twiddle' with a remote JBoss server.\n"
+"A JMX client to 'twiddle' with a remote JBoss server.\n"
"\n"
"usage: twiddle.sh [options] <command> [command_arguments]\n"
"\n"
"options:\n"
-" -h，--help Show this help message\n"
+" -h, --help Show this help message\n"
" --help-commands Show a list of commands\n"
" -H=<command> Show command specific help\n"
" -c=command.properties Specify the command.properties file to use\n"
" -D<name>[=<value>] Set a system property\n"
" -- Stop processing options\n"
-" -s，--server=<url> The JNDI URL of the remote server\n"
-" -a，--adapter=<name> The JNDI name of the RMI adapter to use\n"
-" -q，--quiet Be somewhat more quiet"
+" -s, --server=<url> The JNDI URL of the remote server\n"
+" -a, --adapter=<name> The JNDI name of the RMI adapter to use\n"
+" -q, --quiet Be somewhat more quiet"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1222
@@ -5026,7 +5009,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1242
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[bin]$ ./twiddle.sh -H query\n"
"Query the server for a list of matching MBeans\n"
@@ -5048,15 +5031,15 @@
msgstr ""
"[bin]$ ./twiddle.sh -H query\n"
"Query the server for a list of matching MBeans\n"
-" \n"
+"\n"
"usage: query [options] <query>\n"
"options:\n"
-" -c，--count Display the matching MBean count\n"
+" -c, --count Display the matching MBean count\n"
" -- Stop processing options\n"
"Examples:\n"
-" query all mbeans: query '*:*'\n"
-" query all mbeans in the jboss.j2ee domain: query 'jboss.j2ee:*'\n"
-"[bin]$ ./twiddle.sh -s toki query 'jboss:service=invoker,*'\n"
+" query all mbeans: query '*:*'\n"
+" query all mbeans in the jboss.j2ee domain: query 'jboss.j2ee:*'\n"
+"[bin]$ ./twiddle.sh -s toki query 'jboss:service=invoker,*'\n"
"jboss:readonly=true,service=invoker,target=Naming,type=http\n"
"jboss:service=invoker,type=jrmp\n"
"jboss:service=invoker,type=local\n"
@@ -5072,7 +5055,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1246
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[bin]$ ./twiddle.sh -H get\n"
"Get the values of one or more MBean attributes\n"
@@ -5103,7 +5086,7 @@
msgstr ""
"[bin]$ ./twiddle.sh -H get\n"
"Get the values of one or more MBean attributes\n"
-" \n"
+"\n"
"usage: get [options] <name> [<attr>+]\n"
" If no attribute names are given all readable attributes are retrieved\n"
"options:\n"
@@ -5136,7 +5119,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1250
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[bin]$ ./twiddle.sh -H info\n"
"Get the metadata for an MBean\n"
@@ -5190,9 +5173,9 @@
msgstr ""
"[bin]$ ./twiddle.sh -H info\n"
"Get the metadata for an MBean\n"
-" \n"
+"\n"
"usage: info <mbean-name>\n"
-" Use '*' to query for all attributes\n"
+" Use '*' to query for all attributes\n"
"[bin]$ Description: Management Bean.\n"
"+++ Attributes:\n"
" Name: ServerAddress\n"
@@ -5246,7 +5229,7 @@
#. Tag: programlisting
#: J2EE_Reference_Introduction.xml:1254
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[bin]$ ./twiddle.sh -H invoke\n"
"Invoke an operation on an MBean\n"
@@ -5342,11 +5325,11 @@
msgstr ""
"[bin]$ ./twiddle.sh -H invoke\n"
"Invoke an operation on an MBean\n"
-" \n"
+"\n"
"usage: invoke [options] <query> <operation> (<arg>)*\n"
"\n"
"options:\n"
-" -q，--query-type[=<type>] Treat object name as a query\n"
+" -q, --query-type[=<type>] Treat object name as a query\n"
" -- Stop processing options\n"
"\n"
"query type:\n"
@@ -5370,7 +5353,7 @@
" | +- HsqlDbRealm (class: org.jboss.security.plugins."
"SecurityDomainContext)\n"
" +- timedCacheFactory (class: javax.naming.Context)\n"
-"Failed to lookup: timedCacheFactory，errmsg=null\n"
+"Failed to lookup: timedCacheFactory, errmsg=null\n"
" +- TransactionPropagationContextExporter (class: org.jboss.tm."
"TransactionPropagationContext\n"
"Factory)\n"
@@ -5440,7 +5423,7 @@
#. Tag: para
#: J2EE_Reference_Introduction.xml:1261
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"With the detached invokers and a somewhat generalized proxy factory "
"capability, you can really talk to the JMX server using the "
@@ -5455,12 +5438,11 @@
"using to the <literal>RMIAdaptor</literal> interface over any protocol for "
"which a proxy factory service exists."
msgstr ""
-"用脱管调用者(detached invokers)和有几分普遍的proxy factory能力，你实际上可以"
-"用<literal>InvokerAdaptorService</literal>和proxy factory服务在你选择的协议上"
-"来开放<literal>RMIAdaptor</literal>或类似的接口。我们将在<xref linkend=\"ch2."
-"remoteaccess\"/>里介绍detached invoker和proxy factory。请参考<xref linkend="
-"\"ch2.detinv.sect\"/>里的一个关于invoker服务的例子，它允许在proxy factory服务"
-"存在的任何协议上用<literal>RMIAdaptor</literal>接口访问MBean服务器。"
+"使用脱管调用者（detached invokers）和有几分普遍的代理工厂（proxy factory）能力，你实际上可以"
+"用 <literal>InvokerAdaptorService</literal> 和代理工厂服务在你选择的协议上来开放 <literal>RMIAdaptor</literal> 或类似的接口。我们将在 <xref linkend=\"The_JBoss_JMX_Microkernel-"
+"Remote_Access_to_Services_Detached_Invokers\"/> 里介绍脱管调用者和代理工厂。请参考<xref linkend="
+"\"Remote_Access_to_Services_Detached_Invokers-"
+"A_Detached_Invoker_Example_the_MBeanServer_Invoker_Adaptor_Service\"/> 里的一个关于 invoker 服务的例子，它允许在代理工厂服务存在的任何协议上用 <literal>RMIAdaptor</literal> 接口访问 MBean 服务器。"
#. Tag: title
#: J2EE_Reference_Introduction.xml:1269
More information about the jboss-cvs-commits
mailing list