[jboss-cvs] JBossAS SVN: r69917 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 18 18:37:35 EST 2008
Author: xhuang at jboss.com
Date: 2008-02-18 18:37:35 -0500 (Mon, 18 Feb 2008)
New Revision: 69917
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Additional_Services.po
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po
Log:
update
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Additional_Services.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Additional_Services.po 2008-02-18 23:31:24 UTC (rev 69916)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Additional_Services.po 2008-02-18 23:37:35 UTC (rev 69917)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Additional_Services\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-11-05 06:03+0000\n"
-"PO-Revision-Date: 2008-02-12 12:13+1000\n"
+"PO-Revision-Date: 2008-02-18 15:20+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <zh at li.org>\n"
"MIME-Version: 1.0\n"
@@ -623,7 +623,6 @@
#. Tag: para
#: J2EE_Additional_Services.xml:236
#, no-c-format
-#, fuzzy
msgid ""
"The <literal>portAttrName</literal> is the attribute name of the MBean "
"service to which the binding port value should be applied, and the "
@@ -640,7 +639,9 @@
"and attribute element content may reference system properties using the "
"<literal>${x}</literal> syntax that is supported by the JBoss services "
"descriptor."
-msgstr "<literal>portAttrName</literal> 是 MBean 服务绑定端口值应该的属性名，"
+msgstr ""
+"<literal>portAttrName</literal> 是应该应用这个绑定端口值的 MBean 服务的属性名，而 <literal>hostAttrName</literal> 是应该应用绑定主机值的 MBean 服务的属性名。如果没有指定 <literal>portName</literal> 属性则不应用绑定端口。类似地，如果 <literal>hostName</literal> 属性没有指定则绑定主机不被应用。可选的属性元素指定任意的 MBean 属性名称，其值是主机和/或端口设置。属性内容里任何对 <literal>${host}</literal> 的引用都用主机绑定替换，而任何 <literal>${port}"
+"</literal> 引用都用端口绑定来代替。<literal>portName</literal>、<literal>hostName</literal> 属性值和属性元素内容可以通过 JBoss 服务描述符支持的 <literal>${x}</literal> 语法引用系统属性。"
#. Tag: para
#: J2EE_Additional_Services.xml:239
@@ -1637,27 +1638,23 @@
"timer MBean to configure timer events at regular intervals and to transform "
"them into JMX notifications more suitable for other services. The "
"<literal>TimerService</literal> MBean takes the following attributes:"
-msgstr ""
+msgstr "标准的 JMX 定时器不产生任何定时器事件，除非它被要求这么做。为了帮助定时器 MBean 的配置，JBoss 提供了一个补充的 <literal>TimerService</literal> MBean。它和定时器 MBean 进行交互，以固定时间间隔配置定时器事件并把它们转换成更适合于其他服务的 JMX 通知。<literal>TimerService</literal> MBean 使用下列的属性："
#. Tag: para
#: J2EE_Additional_Services.xml:480
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">NotificationType</emphasis>: This is the type of the "
"notification to be generated."
-msgstr ""
-"<emphasis role=\"bold\">notification-type</emphasis>：这个元素包含用逗号隔开"
-"的通知类型串。"
+msgstr "<emphasis role=\"bold\">NotificationType</emphasis>：这是产生的通知的类型。"
#. Tag: para
#: J2EE_Additional_Services.xml:485
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">NotificationMessage</emphasis>: This is the message "
"that should be associated with the generated notification."
-msgstr ""
-"<emphasis role=\"bold\">notification-type</emphasis>：这个元素包含用逗号隔开"
-"的通知类型串。"
+msgstr "<emphasis role=\"bold\">NotificationMessage</emphasis>：这是应该和产生的通知相关联的消息。"
#. Tag: para
#: J2EE_Additional_Services.xml:490
@@ -1668,41 +1665,37 @@
"specified with a unit like \"30min\" or \"4h\". Valid time suffixes are "
"<literal>msec</literal>, <literal>sec</literal>, <literal>min</literal> and "
"<literal>h</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">TimerPeriod</emphasis>：这是通知之间间隔的时间。除非另外指定（如 \"30min\" 或 \"4h\"），它以毫秒为单位。其有效的后缀是 <literal>msec</literal>、 <literal>sec</literal>、<literal>min</literal> 和 <literal>h</literal>。"
#. Tag: para
#: J2EE_Additional_Services.xml:495
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Repeatitions</emphasis>: This is the number of times "
"the alert should be generated. A value of 0 indicates the alert should "
"repeat indefinitely."
-msgstr ""
-"<emphasis role=\"bold\">ServerBindPort</emphasis>：用于服务器套接字的端口。如"
-"果为 0 则表示使用匿名端口。"
+msgstr "<emphasis role=\"bold\">Repeatitions</emphasis>：应该产生警告的次数。0 值表示警告应该无限重复。"
#. Tag: para
#: J2EE_Additional_Services.xml:500
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">TimerMbean</emphasis>: This is the "
"<literal>ObjectName</literal> of the time MBean that this "
"<literal>TimerService</literal> instance should configure notifications for."
-msgstr ""
-"<emphasis role=\"bold\">PartitionObjectName</emphasis>：与代理关联的群集服务"
-"的 JMX <literal>ObjectName</literal>。"
+msgstr "<emphasis role=\"bold\">TimerMbean</emphasis>：这个 <literal>TimerService</literal> 实例为之配置通知的定时器 MBean 的 <literal>ObjectName</literal>。"
#. Tag: para
#: J2EE_Additional_Services.xml:505
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The following sample illustrates the the use of the <literal>TimerService</"
"literal> MBean."
-msgstr "<literal>HANamingService</literal> MBean 的完整缺省配置如下所示。"
+msgstr "下面的例子解释了 <literal>TimerService</literal> MBean 的用法。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:508
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<mbean code=\"org.jboss.monitor.services.TimerService\" \n"
" name=\"jboss.monitor:name=Heartbeat,type=TimerService\">\n"
@@ -1716,12 +1709,16 @@
" </depends>\n"
"</mbean>"
msgstr ""
-"<mbean code=\"org.jboss.naming.NamingAlias\" \n"
-" name=\"jboss.mq:service=NamingAlias,fromName=QueueConnectionFactory"
-"\">\n"
-" <attribute name=\"ToName\">ConnectionFactory</attribute>\n"
-" <attribute name=\"FromName\">QueueConnectionFactory</"
+"<mbean code=\"org.jboss.monitor.services.TimerService\" \n"
+" name=\"jboss.monitor:name=Heartbeat,type=TimerService\">\n"
+" <attribute name=\"NotificationType\">jboss.monitor.heartbeat</"
"attribute>\n"
+" <attribute name=\"NotificationMessage\">JBoss is alive!</"
+"attribute>\n"
+" <attribute name=\"TimerPeriod\">60sec</attribute>\n"
+" <depends optional-attribute-name=\"TimerMBean\">\n"
+" jboss.monitor:name=Heartbeat,type=Timer\n"
+" </depends>\n"
"</mbean>"
#. Tag: para
@@ -1734,6 +1731,9 @@
"that wants to receive this periodic notifications can subscribe to the "
"notification."
msgstr ""
+"这个 MBean 的配置设置 <literal>jboss.monitor:"
+"name=Heartbeat,type=Timer</literal> 定时器每隔 60 秒就产生一个 <literal>jboss."
+"monitor.heartbeat</literal> 通知。任何想要接收这个定期通知的服务都可以订阅这个通知。"
#. Tag: para
#: J2EE_Additional_Services.xml:512
@@ -1746,6 +1746,8 @@
"for any events generated by the heartbeat timer used in the previous "
"examples."
msgstr ""
+"JBoss 提供一个简单的 <literal>NotificationListener</"
+"literal> MBean 来作为示例，它可以侦听特定的通知并在这个事件产生时记录日志信息。这个 MBean 对于调试或手工观察通知来说非常有用。下面的 MBean 定义侦听前面例子里的 heartbeat 定时器产生的任何事件。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:515
@@ -1761,6 +1763,15 @@
" </attribute>\n"
"</mbean>"
msgstr ""
+"<mbean code=\"org.jboss.monitor.services.NotificationListener\" \n"
+" name=\"jboss.monitor:service=NotificationListener\">\n"
+" <attribute name=\"SubscriptionList\">\n"
+" <subscription-list>\n"
+" <mbean name=\"jboss.monitor:name=Heartbeat,type=Timer\" /"
+">\n"
+" </subscription-list>\n"
+" </attribute>\n"
+"</mbean>"
#. Tag: para
#: J2EE_Additional_Services.xml:516
@@ -1775,7 +1786,7 @@
"create notification filters that select only the notification types desired. "
"The following listing shows how we can limit notifications to only the "
"<literal>jboss.monitor.heartbeat</literal> type the timer service configured."
-msgstr ""
+msgstr "<literal>subscription-list</literal> 元素列出 listener 应该侦听的 MBean。请注意，我们所侦听的 MBean 是实际的定时器 MBean 的名字而不是 <literal>TimerService</literal> MBean。因为定时器可能产生由多个 <literal>TimerService</literal> 实例配置的多个事件，你可能需要依据通知类型进行过滤。<literal>filter</literal> 元素可以用来创建仅选择所需通知类型的通知过滤器。下面的列表演示了我们如何把通知限制为定时器服务所配置的 <literal>jboss.monitor.heartbeat</literal> 类型。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:519
@@ -1795,6 +1806,19 @@
" </attribute>\n"
"</mbean>"
msgstr ""
+"<mbean code=\"org.jboss.monitor.services.NotificationListener\"\n"
+" name=\"jboss.monitor:service=NotificationListener\">\n"
+" <attribute name=\"SubscriptionList\">\n"
+" <subscription-list>\n"
+" <mbean name=\"jboss.monitor:name=Heartbeat,type=Timer\">\n"
+" <filter factory=\"NotificationFilterSupportFactory\">\n"
+" <enable type=\"jboss.monitor.heartbeat\"/"
+"> \n"
+" </filter>\n"
+" </mbean>\n"
+" </subscription-list>\n"
+" </attribute>\n"
+"</mbean>"
#. Tag: para
#: J2EE_Additional_Services.xml:520
@@ -1805,7 +1829,7 @@
"executes a specified script when events are received. The script can be "
"written in any bean shell scripting language. The ScriptingListener accepts "
"has the following parameters."
-msgstr ""
+msgstr "作为更有趣的 listener 的一个例子，我们来看看 ScriptingListener。这个 listener 侦听特定的事件并在接收到事件时执行指定的脚本。这个脚本可以以任何 Bean Shell 语言编写。ScriptingListener 接受下列的参数。"
#. Tag: para
#: J2EE_Additional_Services.xml:525
@@ -1814,7 +1838,7 @@
"<emphasis role=\"bold\">ScriptLanguage</emphasis>: This is the language the "
"script is written in. This should be <literal>beanshell</literal>, unless "
"you have loaded libraries for another beanshell compatible language."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ScriptLanguage</emphasis>：这是编写该脚本所用的语言。除非你已经加载和其他 beanshell 兼容语言相关的库，否则它应该是 <literal>beanshell</literal>。"
#. Tag: para
#: J2EE_Additional_Services.xml:530
@@ -1823,18 +1847,16 @@
"<emphasis role=\"bold\">Script</emphasis>: This is the text of the script to "
"evaluate. It is good practice to enclose the script in a CDATA section to "
"minimize conflicts between scripting language syntax and XML syntax."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Script</emphasis>：这是被赋值的脚本的内容。把脚本包括在 CDATA 标记里来最小化脚本语言语法和 XML 语法之间的冲突是一个不错的做法。"
#. Tag: para
#: J2EE_Additional_Services.xml:535
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">SubscriptionList</emphasis>: This is the list of "
"MBeans that this MBean will listen to for events that will trigger the "
"script."
-msgstr ""
-"<emphasis role=\"bold\">directory</emphasis>：这是建立访问日志文件的目录路"
-"径。"
+msgstr "<emphasis role=\"bold\">SubscriptionList</emphasis>：这是一个 MBean 的列表，这些 MBean 侦听将触发这个脚本的事件。"
#. Tag: para
#: J2EE_Additional_Services.xml:540
@@ -2004,6 +2026,8 @@
"will be started and stopped in tandem with the Barrier. When the barrier "
"controller is undeployed the barrier is destroyed."
msgstr ""
+"当 barrier controller 被部署时，barrier 被实例化、注册并进入 create 状态。此后，当接收到相应的通知时，barrier 将启动或停止。因此，其他服务只需要用普通的 <literal><depends></"
+"literal> 标记来依赖 barrier MBean，而不需要担心复杂的生命周期问题。它们可以和 Barrier 一前一后地启动和停止。当 barrier controller 被卸载时，barrier 被销毁。"
#. Tag: para
#: J2EE_Additional_Services.xml:569
@@ -2018,7 +2042,7 @@
"notifications, so that you can identify quickly from which subscription a "
"notification is originating (because your listener can have many active "
"subscriptions)."
-msgstr ""
+msgstr "我们用 <literal>SubscriptionList</literal> 属性配置 barrier controller 的通知。要确认启动和停止的通知，我们用一个 handback string 对象把这两种订阅进行关联。如果指定了 Handback 对象，它将在接受通知的时候（例如调用 <literal>handleNotification()</literal> 时）和通知一起传回来验证接收的通知，所以你可以快速地确认通知从哪个订阅而来（因为你的 Listener 可能有多个活动的订阅）。"
#. Tag: para
#: J2EE_Additional_Services.xml:572
@@ -2031,6 +2055,8 @@
"barrier controller. Thus we can have more than one notifications triggering "
"the starting or stopping of the barrier."
msgstr ""
+"所以，我们用任何 handback 字符串标记产生启动/停止通知的订阅，且为 barrier controller 的 <literal>StartBarrierHandback</literal>（以及相应的 "
+"<literal>StopBarrierHandback</literal>）属性配置相同的字符串。因此，我们可以有多于一个的触发启动或停止 Barrier 的通知。"
#. Tag: para
#: J2EE_Additional_Services.xml:575
@@ -2044,7 +2070,7 @@
"crossed, but it could be anything. We've used this because it prints out "
"to the console starting and stopping messages, so we know when the service "
"gets activated/deactivated."
-msgstr ""
+msgstr "下面的例子展示了依赖于 Tomcat 连接器的一个服务。事实上，对于想要访问 Tomcat 内部的 Selvlet 的服务来说，这是一个很常用的模式。依赖于这个例子里的 Barrier 的服务是一个简单的内存监控程序，它创建后台线程并监控内存的使用情况，当超过设定限额时则发出通知，或是进行其他处理。我们使用它在控制台上打印启动和停止消息，这样我们就知道服务在什么时候激活或取消。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:578
@@ -2212,7 +2238,7 @@
"using the <literal>startBarrier()</literal> and <literal>stopBarrier()</"
"literal> operations on the barrier controller. The attribute "
"<literal>BarrierStateString</literal> indicates the status of the barrier."
-msgstr ""
+msgstr "如果你在正运行的服务器里热部署它，Barrier 将被停止，因为到 barrier controller 被部署时，启动通知已经被捕获了（目前还没有克服这个的办法）。然而，如果你重启动这个服务器，Barrier 将在 Tomcat 连接器激活后启动。你也可以通过 barrier controller 里的 <literal>startBarrier()</literal> 和 <literal>stopBarrier()</literal> 操作手工地启动或停止 Barrier。属性 <literal>BarrierStateString</literal> 指示 Barrier 的状态。"
#. Tag: title
#: J2EE_Additional_Services.xml:585
@@ -2229,7 +2255,7 @@
"managers. In this respect the snmp-adaptor acts as a SNMP agent. Future "
"versions may offer support for full agent get/set functionality that maps "
"onto MBean attributes or operations."
-msgstr ""
+msgstr "JBoss 有一个 SNMP 适配器，它可以用来拦截 MBean 发出的 JMX 通知，把它们转换成 trap 并发送到 SNMP 管理者。此时的 SNMP 适配器充当 SNMP 代理的角色。将来的版本可以提供对完整的映射至 MBean 属性或操作的代理 get/set 功能的支持。"
#. Tag: para
#: J2EE_Additional_Services.xml:589
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po 2008-02-18 23:31:24 UTC (rev 69916)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po 2008-02-18 23:37:35 UTC (rev 69917)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Messaging_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-11-05 06:03+0000\n"
-"PO-Revision-Date: 2008-01-24 17:43+1000\n"
+"PO-Revision-Date: 2008-02-18 16:35+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <zh at li.org>\n"
"MIME-Version: 1.0\n"
@@ -2234,13 +2234,13 @@
"processed the message. This shows that many MDBs may actively process "
"messages posted to a destination. Concurrent processing is one of the "
"benefits of MDBs."
-msgstr ""
+msgstr "客户端接收的消息包括一个 \"processed by: NNN\" 后缀，这里的 NNN 是处理消息的 MDB 实例的 <literal>hashCode</literal> 值。这表示多个 MDB 可以活动地处理发送到目的地的消息。并行处理是 使用 MDB 的好处之一。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:172
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBoss MQ Overview"
-msgstr "JBoss MBean 服务"
+msgstr "JBoss MQ 概述"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:173
@@ -2250,12 +2250,14 @@
"level services to client applications. The services that make up the JBossMQ "
"JMS implementation are introduced in this section."
msgstr ""
+"JBossMQ 由几个服务组成，它们为客户应用程序提供 JMS API 级的服务。本节将介绍组成 JBossMQ "
+"JMS 实现的服务。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:177
#, no-c-format
msgid "Invocation Layer"
-msgstr ""
+msgstr "调用层（Invocation Layer）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:178
@@ -2269,7 +2271,7 @@
"handle the transport details of messaging. They delegate messages to the JMS "
"server JMX gateway service known as the invoker. This is similar to how the "
"detached invokers expose the EJB container via different transports."
-msgstr ""
+msgstr "调用层（Invocation Layer，IL）服务负责处理客户端用来发送和接收消息的通信协议。JBossMQ 可以支持不同类型的调用层服务的同时运行。所有的调用层服务都支持双向通信，这允许客户同时发送和接收消息。调用层服务只处理消息的传输细节。它们把消息委托给 JMS 服务器或 JMX 网关服务（称为调用者）。这和脱管调用者怎样通过不同的传输协议开放 EJB 容器是类似的。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:181
More information about the jboss-cvs-commits
mailing list