[jboss-cvs] JBossAS SVN: r69764 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Feb 10 23:37:26 EST 2008
Author: xhuang at jboss.com
Date: 2008-02-10 23:37:26 -0500 (Sun, 10 Feb 2008)
New Revision: 69764
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_Connectors_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-11 02:29:19 UTC (rev 69763)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Additional_Services.po 2008-02-11 04:37:26 UTC (rev 69764)
@@ -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-04 16:35+1000\n"
+"PO-Revision-Date: 2008-02-11 11:55+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <zh at li.org>\n"
"MIME-Version: 1.0\n"
@@ -26,12 +26,11 @@
#. Tag: para
#: J2EE_Additional_Services.xml:7
#, no-c-format
-#, fuzzy
msgid ""
"This chapter discusses useful MBean services that are not discussed "
"elsewhere either because they are utility services not necessary for running "
"JBoss, or they don't fit into a current section of the book."
-msgstr "本章讨论一些其他章节没有涉及的有用的 MBean 服务，它们并不是运行 JBoss 所必需的服务，或者是"
+msgstr "本章讨论一些其他章节没有涉及的有用的 MBean 服务，它们要么不是运行 JBoss 所必需的服务，要么是不能安插在其他章节的内容。"
#. Tag: title
#: J2EE_Additional_Services.xml:11
@@ -159,7 +158,6 @@
#. Tag: para
#: J2EE_Additional_Services.xml:79
#, no-c-format
-#, fuzzy
msgid ""
"<emphasis role=\"bold\">ConfigurationURL</emphasis>: The URL for the log4j "
"configuration file. This can refer to either a XML document parsed by the "
@@ -169,45 +167,39 @@
"null, the file extension. The default setting of <literal>resource:log4j."
"xml</literal> refers to the <literal>conf/log4j.xml</literal> file of the "
"active server configuration file set."
-msgstr "<emphasis role=\"bold\">ConfigurationURL</emphasis>：log4j 配置文件的 URL。"
+msgstr ""
+"<emphasis role=\"bold\">ConfigurationURL</emphasis>：log4j 配置文件的 URL。它可以引用一个由 <literal>org.apache.log4j.xml.DOMConfigurator</literal> 解析的 XML 文档或 <literal>org.apache.log4j.PropertyConfigurator</literal> 解析的 Java 属性文件。文件的类型由 URL 的 Content Type 决定，如果为 null，则由文件后缀名决定。<literal>resource:log4j."
+"xml</literal> 的缺省设置引用活动的服务器配置文件集里的 <literal>conf/log4j.xml</literal> 文件。"
#. Tag: para
#: J2EE_Additional_Services.xml:84
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">RefreshPeriod</emphasis>: The time in seconds "
"between checks for changes in the log4 configuration specified by the "
"<literal>ConfigurationURL</literal> attribute. The default value is 60 "
"seconds."
-msgstr ""
-"<emphasis role=\"bold\">ScanPeriod</emphasis>：运行scanner线程间隔的毫秒数。"
-"它的缺省值是5000(5秒)。"
+msgstr "<emphasis role=\"bold\">RefreshPeriod</emphasis>：检查 <literal>ConfigurationURL</literal> 属性指定的 log4 配置是否修改的时间间隔。它的缺省值是 60 秒。"
#. Tag: para
#: J2EE_Additional_Services.xml:89
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">CatchSystemErr</emphasis>: This boolean flag if "
"true, indicates if the <literal>System.err</literal> stream should be "
"redirected onto a log4j category called <literal>STDERR</literal>. The "
"default is true."
-msgstr ""
-"<emphasis role=\"bold\">LenientEjbLink</emphasis>：这个标记指出在尝试 "
-"<literal>jboss-web.xml</literal> 里的 <literal>jndi-name</literal> 时应该忽"
-"略 <literal>ejb-link</literal> 错误。这个标记的缺省值是 ture。"
+msgstr "<emphasis role=\"bold\">CatchSystemErr</emphasis>：这个标记如果为 true，表示 <literal>System.err</literal> 流是否应该重定向到名为 <literal>STDERR</literal> 的 log4j 类别。这个标记的缺省值是 ture。"
#. Tag: para
#: J2EE_Additional_Services.xml:94
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">CatchSystemOut</emphasis>: This boolean flag if "
"true, indicates if the <literal>System.out</literal> stream should be "
"redirected onto a log4j category called <literal>STDOUT</literal>. The "
"default is true."
-msgstr ""
-"<emphasis role=\"bold\">LenientEjbLink</emphasis>：这个标记指出在尝试 "
-"<literal>jboss-web.xml</literal> 里的 <literal>jndi-name</literal> 时应该忽"
-"略 <literal>ejb-link</literal> 错误。这个标记的缺省值是 ture。"
+msgstr "<emphasis role=\"bold\">CatchSystemOut</emphasis>：这个标记如果为 true，表示 <literal>System.out</literal> 流是否应该重定向到名为 <literal>STDOUT</literal> 的 log4j 类别。这个标记的缺省值是 ture。"
#. Tag: para
#: J2EE_Additional_Services.xml:99
@@ -218,12 +210,14 @@
"literal>. As of log4j1.2.8 this needs to be set to avoid a possible deadlock "
"on exception at the appender level. See bug#696819."
msgstr ""
+"<emphasis role=\"bold\">Log4jQuietMode</emphasis>：这个布尔值标记如果为 true，则设置 <literal>org.apache.log4j.helpers.LogLog.setQuiteMode</"
+"literal>。log4j1.2.8 需要设置它来避免可能发生的 appender 级别异常的死锁。请参考 bug#696819。"
#. Tag: title
#: J2EE_Additional_Services.xml:107
#, no-c-format
msgid "System Properties Management"
-msgstr ""
+msgstr "系统属性管理"
#. Tag: para
#: J2EE_Additional_Services.xml:108
@@ -233,13 +227,13 @@
"service. It supports setting of the VM global property values just as "
"<literal>java.lang.System.setProperty</literal> method and the VM command "
"line arguments do."
-msgstr ""
+msgstr "系统属性的管理可以用系统属性服务来完成。它支持对 VM 全局属性值的设置，就象 <literal>java.lang.System.setProperty</literal> 方法和 VM 命令行参数所执行的功能一样。"
#. Tag: para
#: J2EE_Additional_Services.xml:111
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Its configurable attributes include:"
-msgstr "可配置的属性如下："
+msgstr "它的可配置属性包括："
#. Tag: para
#: J2EE_Additional_Services.xml:116
@@ -251,6 +245,8 @@
"<literal>property=value</literal> statement is given on a separate line "
"within the body of the <literal>Properties</literal> attribute element."
msgstr ""
+"<emphasis role=\"bold\">Properties</emphasis>：这是多个属性 <literal>name=value</literal> 对的集合，它的格式使用 <literal>java.util."
+"Properites.load(java.io.InputStream)</literal> 方法。每个 <literal>property=value</literal> 声明都在 <literal>Properties</literal> 属性元素体里以单独一行的方式给定。"
#. Tag: para
#: J2EE_Additional_Services.xml:121
@@ -266,6 +262,10 @@
"literal> file when running with the <literal>default</literal> configuration "
"file set."
msgstr ""
+"<emphasis role=\"bold\">URLList</emphasis>：这是一个加载属性文件格式化内容的用逗号隔开的 URL 字符串列表。如果这个列表里的组件是相对路径而不是 URL，它将被当作性对于 <literal><jboss-dist>/server/<config></"
+"literal> 目录的文件路径来处理。例如，当运行 <literal>default</literal> 配置文件集时，组件 <literal>conf/local."
+"properties</literal> 将被当作指向 <literal><jboss-dist>/server/production/conf/local.properties</"
+"literal> 的文件 URL。"
#. Tag: para
#: J2EE_Additional_Services.xml:126
@@ -273,7 +273,7 @@
msgid ""
"The following illustrates the usage of the system properties service with an "
"external properties file."
-msgstr ""
+msgstr "下面解释了系统属性服务和外部属性文件的用法。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:129
@@ -290,6 +290,16 @@
" </attribute>\n"
"</mbean>"
msgstr ""
+"<mbean code=\"org.jboss.varia.property.SystemPropertiesService\"\n"
+" name=\"jboss.util:type=Service,name=SystemProperties\">\n"
+" \n"
+" <!-- Load properties from each of the given comma separated URLs --"
+">\n"
+" <attribute name=\"URLList\">\n"
+" http://somehost/some-location.properties,\n"
+" ./conf/somelocal.properties\n"
+" </attribute>\n"
+"</mbean>"
#. Tag: para
#: J2EE_Additional_Services.xml:130
@@ -297,7 +307,7 @@
msgid ""
"The following illustrates the usage of the system properties service with an "
"embedded properties list."
-msgstr ""
+msgstr "下面解释了系统属性服务和内嵌属性列表的用法。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:133
@@ -313,12 +323,21 @@
" \n"
"</mbean>"
msgstr ""
+"<mbean code=\"org.jboss.varia.property.SystemPropertiesService\"\n"
+" name=\"jboss.util:type=Service,name=SystemProperties\">\n"
+" <!-- Set properties using the properties file style. -->\n"
+" <attribute name=\"Properties\">\n"
+" property1=This is the value of my property\n"
+" property2=This is the value of my other property\n"
+" </attribute>\n"
+" \n"
+"</mbean>"
#. Tag: title
#: J2EE_Additional_Services.xml:137
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Property Editor Management"
-msgstr "属性名"
+msgstr "属性编辑器管理"
#. Tag: para
#: J2EE_Additional_Services.xml:138
@@ -333,6 +352,10 @@
"service is configured in <literal>deploy/properties-service.xml</literal> "
"and supports the following attributes:"
msgstr ""
+"在 JBoss 里，JavaBean 属性编辑器被用来从服务文件读取数据以及在 JMX 控制台里编辑属性值。<literal>java."
+"bean.PropertyEditorManager</literal> 类控制系统里的 <literal>java.bean."
+"PropertyEditor</literal> 实例。在 JBoss 里，属性编辑器管理者可以通过 <literal>org.jboss.varia.property."
+"PropertyEditorManagerService</literal> MBean 进行管理。属性编辑器管理者服务在 <literal>deploy/properties-service.xml</literal> 里进行配置并支持下面的属性："
#. Tag: para
#: J2EE_Additional_Services.xml:143
@@ -343,7 +366,7 @@
"defining the property editor to type mappings that should be preloaded into "
"the property editor manager. The value type of this attribute is a string so "
"that it may be set from a string without requiring a custom property editor."
-msgstr ""
+msgstr "<emphasis role=\"bold\">BootstrapEditors</emphasis>：它是一个定义可以预加载到属性编辑器管理者里的属性编辑器和类型映射的 <literal>property_editor_class=editor_value_type_class</literal> 对的列表。这个属性的值是一个字符串，所以它可以根据从不要求自定义属性编辑器的字符串进行设置。"
#. Tag: para
#: J2EE_Additional_Services.xml:148
@@ -354,7 +377,7 @@
"<literal>java.util.Properties</literal>. Setting it from a string value in a "
"service file requires a custom property editor for properties objects "
"already be loaded. JBoss provides a suitable property editor."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Editors</emphasis>：它和 <literal>BootstrapEditors</literal> 属性的功能相同，但它的类型是 <literal>java.util.Properties</literal>。通过服务文件里的字符串对它进行设置要求用于已加载的属性对象的自定义属性编辑器。JBoss 提供了一个合适的属性编辑器。"
#. Tag: para
#: J2EE_Additional_Services.xml:153
@@ -369,12 +392,14 @@
"<literal>org.jboss.mx.util.propertyeditor</literal>, to the front of the new "
"search path."
msgstr ""
+"<emphasis role=\"bold\">EditorSearchPath</emphasis>：这个属性允许在 <literal>PropertyEditorManager</literal> 编辑器软件包搜索路径上设置编辑器软件包搜索路径。既然只能有一个搜索路径，设置这个值将覆盖 JBoss 建立的缺省搜索路径。如果你设置了这个值，请确保把 JBoss 搜索路径 <literal>org.jboss.util.propertyeditor</literal> 和 "
+"<literal>org.jboss.mx.util.propertyeditor</literal> 添加到新的搜索路径前面。"
#. Tag: title
#: J2EE_Additional_Services.xml:161
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Services Binding Management"
-msgstr "JNDI 绑定管理者(Binding Manager)"
+msgstr "服务绑定管理"
#. Tag: para
#: J2EE_Additional_Services.xml:162
@@ -390,6 +415,8 @@
"<literal>conf/jboss-service.xml</literal>. The set of configurable "
"attributes it supports include:"
msgstr ""
+"对于 JBoss 里所有独立部署的服务，如果在给定主机上运行多个实例，编辑配置文件来避免端口冲突可能是件相当乏味的事情。绑定服务（binding service）允许你对多个 JBoss 实例集中进行端口配置。在 JBoss 正常加载了服务后，<literal>ServiceConfigurator</"
+"literal> 将服务绑定管理者加入队列来处理对现有服务的覆盖。服务绑定管理者在 <literal>conf/jboss-service.xml</literal> 里进行配置。它支持的可配置属性包括："
#. Tag: para
#: J2EE_Additional_Services.xml:167
@@ -398,7 +425,7 @@
"<emphasis role=\"bold\">ServerName</emphasis>: This is the name of the "
"server configuration this JBoss instance is associated with. The binding "
"manager will apply the overrides defined for the named configuration."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ServerName</emphasis>：这是这个 JBoss 实例所关联的服务器配置的名称。绑定管理者将根据该配置里的定义进行覆盖。"
#. Tag: para
#: J2EE_Additional_Services.xml:172
@@ -411,19 +438,18 @@
"literal>. The factory provides a <literal>ServicesStore</literal> instance "
"responsible for providing the names configuration sets."
msgstr ""
+"<emphasis role=\"bold\">StoreFactoryClassName</emphasis>：这个是实现 <literal>ServicesStoreFactory</literal> 接口的类的名称。你可以提供自己的实现，或使用缺省的基于 XML 的库：<literal>org.jboss.services.binding.XMLServicesStoreFactory</"
+"literal>。这个工厂提供了一个 <literal>ServicesStore</literal> 实例来负责这些配置集。"
#. Tag: para
#: J2EE_Additional_Services.xml:177
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">StoreURL</emphasis>: This is the URL of the "
"configuration store contents, which is passed to the <literal>ServicesStore</"
"literal> instance to load the server configuration sets from. For the XML "
"store, this is a simple service binding file."
-msgstr ""
-"<emphasis role=\"bold\">ClientConnectPort</emphasis>：客户传入 "
-"<literal>Socket(addr, port)</literal> 构造函数的端口。它的缺省值是服务器侦听"
-"套接字的端口号。"
+msgstr "<emphasis role=\"bold\">StoreURL</emphasis>：这是配置库内容的 URL，它被传递给 <literal>ServicesStore</literal> 实例来加载服务器配置集。对于 XML 库来说，这是一个简单的服务绑定文件。"
#. Tag: para
#: J2EE_Additional_Services.xml:182
@@ -433,10 +459,12 @@
"the <literal>ports-01</literal> configuration from the <literal>sample-"
"bindings.xml</literal> file provided in the JBoss examples directory."
msgstr ""
+"下面是一个简单的服务绑定管理者配置，它使用 JBoss examples 目录下提供的 <literal>sample-"
+"bindings.xml</literal> 文件里的 <literal>ports-01</literal> 配置。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:185
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<mbean code=\"org.jboss.services.binding.ServiceBindingManager\" \n"
" name=\"jboss.system:service=ServiceBindingManager\">\n"
@@ -449,12 +477,15 @@
" </attribute>\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</"
-"attribute>\n"
+"<mbean code=\"org.jboss.services.binding.ServiceBindingManager\" \n"
+" name=\"jboss.system:service=ServiceBindingManager\">\n"
+" <attribute name=\"ServerName\">ports-01</attribute>\n"
+" <attribute name=\"StoreURL\">\n"
+" ../docs/examples/binding-manager/sample-bindings.xml\n"
+" </attribute>\n"
+" <attribute name=\"StoreFactoryClassName\">\n"
+" org.jboss.services.binding.XMLServicesStoreFactory \n"
+" </attribute>\n"
"</mbean>"
#. Tag: para
@@ -464,28 +495,28 @@
"The structure of the binding file is shown in <xref linkend="
"\"Services_Binding_Management-The_binding_service_file_structure\"/>."
msgstr ""
+"<xref linkend="
+"\"Services_Binding_Management-The_binding_service_file_structure\"/> 展示了这个绑定文件的结构。"
#. Tag: title
#: J2EE_Additional_Services.xml:190
#, no-c-format
msgid "The binding service file structure"
-msgstr ""
+msgstr "绑定服务文件的结构"
#. Tag: para
#: J2EE_Additional_Services.xml:197
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The elements are:"
-msgstr "子元素是："
+msgstr "它的元素包括："
#. Tag: para
#: J2EE_Additional_Services.xml:202
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">service-bindings</emphasis>: The root element of the "
"configuration file. It contains one or more server elements."
-msgstr ""
-"<emphasis role=\"bold\">DiscoveryDisabled</emphasis> 是一个布尔值标记，它可用"
-"来取消自动恢复多点传送侦听者（multicast listener）的配置。"
+msgstr "<emphasis role=\"bold\">service-bindings</emphasis>：配置文件的根元素。"
#. Tag: para
#: J2EE_Additional_Services.xml:207
@@ -497,7 +528,7 @@
"the name that correlates with the <literal>ServiceBindingManager</"
"literal><literal>ServerName</literal> attribute value. The server element "
"content consists of one or more <literal>service-config</literal> elements."
-msgstr ""
+msgstr "<emphasis role=\"bold\">server</emphasis>：这是 JBoss 服务器实例配置的基类。它有一个定义它应用的 JBoss 实例名称的 <literal>name</literal> 属性.这个属性是必需的，它和 <literal>ServiceBindingManager</literal><literal>ServerName</literal> 属性值相关联。server 元素的内容由一个或多个 <literal>service-config</literal> 元素组成。"
#. Tag: para
#: J2EE_Additional_Services.xml:212
@@ -512,7 +543,7 @@
"knows how to handle bindings for the target service. Its contents consists "
"of an optional <literal>delegate-config</literal> element and one or more "
"binding elements."
-msgstr ""
+msgstr "<emphasis role=\"bold\">service-config</emphasis>：这个元素代表对一个 MBean 服务配置的覆盖。它有一个必需的名称属性：该配置所应用的 MBean 服务的 JMX <literal>ObjectName</literal> 字符串。它也有一个必需的 <literal>delegateClass</literal> 名称属性，用来指定处理目标服务的绑定的 <literal>ServicesConfigDelegate</literal> 实现的类名。它的内容由可选的 <literal>delegate-config</literal> 元素以及一个或多个 binding 元素组成。"
#. Tag: para
#: J2EE_Additional_Services.xml:217
@@ -526,7 +557,7 @@
"<literal>host</literal> attributes respectively. If the port is not "
"specified it defaults to 0 meaning choose an anonymous port. If the host is "
"not specified it defaults to null meaning any address."
-msgstr ""
+msgstr "<emphasis role=\"bold\">binding</emphasis>：<literal>binding</literal> 元素指定一对端口和地址。它有一个可选 <literal>name</literal> 属性，为某个服务提供多个绑定。Web 容器的多个虚拟主机就是一个例子。端口和地址通过可选的 <literal>port</literal> 和 <literal>host</literal> 属性进行指定。如果没有指定端口，则缺省为 0，这表示匿名端口。如果没有指定主机，则缺省为 null，表示任意地址。"
#. Tag: para
#: J2EE_Additional_Services.xml:222
@@ -543,24 +574,26 @@
"literal> are arbitrary, but there is no way to specify and a element can "
"have any number of attributes with a DTD."
msgstr ""
+"<emphasis role=\"bold\">delegate-config</emphasis>：<literal>delegate-"
+"config</literal> 元素是 <literal>ServicesConfigDelegate</literal> 实现所使用的任意的 XML 片段。<literal>hostName</literal> 和 <literal>portName</literal> 属性只适用于 "
+" <literal>AttributeMappingDelegate</literal>，它们被用来阻止可识别 DTD 的编辑器意识到它们在 <literal>AttributeMappingDelegate</literal> 配置里的存在。通常，<literal>delegate-config</literal> 的属性和内容都是任意的，但不能指定一个元素可以有任何数目的带有 DTD 定义的属性。"
#. Tag: para
#: J2EE_Additional_Services.xml:227
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The three <literal>ServicesConfigDelegate</literal> implementations are "
"<literal>AttributeMappingDelegate</literal>, <literal>XSLTConfigDelegate</"
"literal>, and <literal>XSLTFileDelegate</literal>."
msgstr ""
-"人员（Person）表中将包括 <literal>pid</literal>，<literal>birthday</"
-"literal>，<literal>initial</literal>，<literal>first</literal>和 "
-"<literal>last</literal> 等字段。"
+"<literal>AttributeMappingDelegate</literal>、<literal>XSLTConfigDelegate</"
+"literal> 和 <literal>XSLTFileDelegate</literal> 是 3 个对 <literal>ServicesConfigDelegate</literal> 的实现。"
#. Tag: title
#: J2EE_Additional_Services.xml:231
#, no-c-format
msgid "AttributeMappingDelegate"
-msgstr ""
+msgstr "AttributeMappingDelegate"
#. Tag: para
#: J2EE_Additional_Services.xml:232
@@ -569,7 +602,7 @@
"The <literal>AttributeMappingDelegate</literal> class is an implementation "
"of the <literal>ServicesConfigDelegate</literal> that expects a "
"<literal>delegate-config</literal> element of the form:"
-msgstr ""
+msgstr "<literal>AttributeMappingDelegate</literal> 类是对 <literal>ServicesConfigDelegate</literal> 的实现，它要求下列形式的 <literal>delegate-config</literal> 元素："
#. Tag: programlisting
#: J2EE_Additional_Services.xml:235
@@ -581,10 +614,16 @@
" <!-- ... -->\n"
"</delegate-config>"
msgstr ""
+"<delegate-config portName=\"portAttrName\" hostName=\"hostAttrName\">\n"
+" <attribute name=\"someAttrName\">someHostPortExpr</"
+"attribute>\n"
+" <!-- ... -->\n"
+"</delegate-config>"
#. 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 "
@@ -601,7 +640,7 @@
"and attribute element content may reference system properties using the "
"<literal>${x}</literal> syntax that is supported by the JBoss services "
"descriptor."
-msgstr ""
+msgstr "<literal>portAttrName</literal> 是 MBean 服务绑定端口值应该的属性名，"
#. Tag: para
#: J2EE_Additional_Services.xml:239
@@ -609,7 +648,7 @@
msgid ""
"The sample listing illustrates the usage of "
"<literal>AttributeMappingDelegate</literal>."
-msgstr ""
+msgstr "示例列表解释了 <literal>AttributeMappingDelegate</literal> 的用法。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:242
@@ -622,6 +661,12 @@
" <binding port=\"1099\" />\n"
"</service-config>"
msgstr ""
+"<service-config name=\"jboss:service=Naming\"\n"
+" delegateClass=\"org.jboss.services.binding."
+"AttributeMappingDelegate\">\n"
+" <delegate-config portName=\"Port\"/>\n"
+" <binding port=\"1099\" />\n"
+"</service-config>"
#. Tag: para
#: J2EE_Additional_Services.xml:243
@@ -631,13 +676,13 @@
"<literal>Port</literal> attribute value overridden to 1099. The "
"corresponding setting from the jboss1 server configuration overrides the "
"port to 1199."
-msgstr ""
+msgstr "在这里，<literal>jboss:service=Naming</literal> MBean 服务的 <literal>Port</literal> 属性值被覆盖为 1099。jboss1 服务器配置里对应的设置将其覆盖为 1199。"
#. Tag: title
#: J2EE_Additional_Services.xml:249
#, no-c-format
msgid "XSLTConfigDelegate"
-msgstr ""
+msgstr "XSLTConfigDelegate"
#. Tag: para
#: J2EE_Additional_Services.xml:250
@@ -647,6 +692,8 @@
"<literal>ServicesConfigDelegate</literal> that expects a <literal>delegate-"
"config</literal> element of the form:"
msgstr ""
+"<literal>XSLTConfigDelegate</literal> 类是对 <literal>ServicesConfigDelegate</literal> 的实现，它要求下列形式的 <literal>delegate-"
+"config</literal> 元素："
#. Tag: programlisting
#: J2EE_Additional_Services.xml:253 J2EE_Additional_Services.xml:268
@@ -661,6 +708,14 @@
" <!-- ... -->\n"
"</delegate-config>"
msgstr ""
+"<delegate-config>\n"
+" <xslt-config configName=\"ConfigurationElement\"><![CDATA[\n"
+" Any XSL document contents...\n"
+" ]]>\n"
+" </xslt-config>\n"
+" <xslt-param name=\"param-name\">param-value</xslt-param>\n"
+" <!-- ... -->\n"
+"</delegate-config>"
#. Tag: para
#: J2EE_Additional_Services.xml:254
@@ -676,16 +731,19 @@
"literal>, and their values are set to the configuration host and port "
"bindings."
msgstr ""
+"<literal>xslt-config</literal> 子元素的内容指定了一个任意的 XSL 脚本片段，它应用于 <literal>configName</literal> 属性命名的 MBean 服务属性。这个属性的类型必须是 <literal>org.w3c.dom.Element</literal>。可选的 <literal>xslt-param</literal> 元素指定 XSL 脚本里使用的参数值。缺省将定义两个 XSL 参数：<literal>host</literal> 和 <literal>port</"
+"literal>，它们的值被设置为配置主机和端口绑定。"
#. Tag: para
#: J2EE_Additional_Services.xml:257
#, no-c-format
+#, fuzzy
msgid ""
"The <literal>XSLTConfigDelegate</literal> is used to transform services "
"whose <literal>port/interface</literal> configuration is specified using a "
"nested XML fragment. The following example maps the port number on "
"hypersonic datasource:"
-msgstr ""
+msgstr "<literal>XSLTConfigDelegate</literal> "
#. Tag: programlisting
#: J2EE_Additional_Services.xml:260
@@ -731,12 +789,51 @@
" <binding host=\"localhost\" port=\"1901\"/>\n"
"</service-config>"
msgstr ""
+"<service-config name=\"jboss.jca:service=ManagedConnectionFactory,"
+"name=DefaultDS\" \n"
+" delegateClass=\"org.jboss.services.binding.XSLTConfigDelegate"
+"\">\n"
+" <delegate-config>\n"
+" <xslt-config configName=\"ManagedConnectionFactoryProperties\">"
+"<![CDATA[\n"
+"<xsl:stylesheet\n"
+" xmlns:xsl='http://www.w3.org/1999/XSL/Transform' "
+"version='1.0'>\n"
+"\n"
+" <xsl:output method=\"xml\" />\n"
+" <xsl:param name=\"host\"/>\n"
+" <xsl:param name=\"port\"/>\n"
+"\n"
+" <xsl:template match=\"/\">\n"
+" <xsl:apply-templates/>\n"
+" </xsl:template>\n"
+"\n"
+" <xsl:template match=\"config-property[@name='ConnectionURL']"
+"\">\n"
+" <config-property type=\"java.lang.String\" name=\"ConnectionURL"
+"\">\n"
+" jdbc:hsqldb:hsql://<xsl:value-of select='$host'/>:<"
+"xsl:value-of select='$port'/>\n"
+" </config-property>\n"
+" </xsl:template>\n"
+"\n"
+" <xsl:template match=\"*|@*\">\n"
+" <xsl:copy>\n"
+" <xsl:apply-templates select=\"@*|node()\"/>\n"
+" </xsl:copy>\n"
+" </xsl:template>\n"
+"</xsl:stylesheet>\n"
+"]]>\n"
+" </xslt-config>\n"
+" </delegate-config>\n"
+" <binding host=\"localhost\" port=\"1901\"/>\n"
+"</service-config>"
#. Tag: title
#: J2EE_Additional_Services.xml:264
#, no-c-format
msgid "XSLTFileDelegate"
-msgstr ""
+msgstr "XSLTFileDelegate"
#. Tag: para
#: J2EE_Additional_Services.xml:265
@@ -770,7 +867,7 @@
msgid ""
"The following example maps the host and port values for the Tomcat "
"connectors:"
-msgstr ""
+msgstr "下面的例子映射了 Tomcat 连接器的主机和端口值："
#. Tag: programlisting
#: J2EE_Additional_Services.xml:275
@@ -844,12 +941,79 @@
" <binding port=\"8280\"/>\n"
"</service-config>"
msgstr ""
+"<service-config name=\"jboss.web:service=WebServer\"\n"
+" delegateClass=\"org.jboss.services.binding.XSLTFileDelegate"
+"\">\n"
+" <delegate-config>\n"
+" <xslt-config configName=\"ConfigFile\"><![CDATA[\n"
+" <xsl:stylesheet\n"
+" xmlns:xsl='http://www.w3.org/1999/XSL/Transform' "
+"version='1.0'>\n"
+"\n"
+" <xsl:output method=\"xml\" />\n"
+" <xsl:param name=\"port\"/>\n"
+"\n"
+" <xsl:variable name=\"portAJP\" select=\"$port - 71\"/>\n"
+" <xsl:variable name=\"portHttps\" select=\"$port + 363\"/>\n"
+"\n"
+" <xsl:template match=\"/\">\n"
+" <xsl:apply-templates/>\n"
+" </xsl:template>\n"
+"\n"
+" <xsl:template match = \"Connector\">\n"
+" <Connector>\n"
+" <xsl:for-each select=\"@*\">\n"
+" <xsl:choose>\n"
+" <xsl:when test=\"(name() = 'port' and . = "
+"'8080')\">\n"
+" <xsl:attribute name=\"port\">\n"
+" <xsl:value-of select=\"$port\" />\n"
+" </xsl:attribute>\n"
+" </xsl:when>\n"
+" <xsl:when test=\"(name() = 'port' and . = "
+"'8009')\">\n"
+" <xsl:attribute name=\"port\">\n"
+" <xsl:value-of select=\"$portAJP\" />\n"
+" </xsl:attribute>\n"
+" </xsl:when>\n"
+" <xsl:when test=\"(name() = 'redirectPort')\">\n"
+" <xsl:attribute name=\"redirectPort\">\n"
+" <xsl:value-of select=\"$portHttps\" />\n"
+" </xsl:attribute>\n"
+" </xsl:when>\n"
+" <xsl:when test=\"(name() = 'port' and . = "
+"'8443')\">\n"
+" <xsl:attribute name=\"port\">\n"
+" <xsl:value-of select=\"$portHttps\" />\n"
+" </xsl:attribute>\n"
+" </xsl:when>\n"
+" <xsl:otherwise>\n"
+" <xsl:attribute name=\"{name()}\"><xsl:value-of "
+"select=\".\" /></xsl:attribute>\n"
+" </xsl:otherwise>\n"
+" </xsl:choose>\n"
+" </xsl:for-each>\n"
+" <xsl:apply-templates/>\n"
+" </Connector>\n"
+" </xsl:template>\n"
+"\n"
+" <xsl:template match=\"*|@*\">\n"
+" <xsl:copy>\n"
+" <xsl:apply-templates select=\"@*|node()\"/>\n"
+" </xsl:copy>\n"
+" </xsl:template>\n"
+" </xsl:stylesheet>\n"
+" ]]>\n"
+" </xslt-config>\n"
+" </delegate-config>\n"
+" <binding port=\"8280\"/>\n"
+"</service-config>"
#. Tag: title
#: J2EE_Additional_Services.xml:279
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The Sample Bindings File"
-msgstr "映射文件"
+msgstr "示例绑定文件"
#. Tag: para
#: J2EE_Additional_Services.xml:280
@@ -862,12 +1026,14 @@
"and <literal>jboss1</literal> by running the following command from the book "
"examples directory:"
msgstr ""
+"JBoss 带有的服务绑定配置文件可以在同一主机上启动最多 3 个独立的 JBoss 实例。我们在这里将逐步地启动两个实例并查看示例配置。首先从 book 例程的 examples 目录下运行下列命令来创建两个服务器配置文件集 <literal>jboss0</literal> "
+"和 <literal>jboss1</literal>："
#. Tag: programlisting
#: J2EE_Additional_Services.xml:283
-#, fuzzy, no-c-format
+#, no-c-format
msgid "[examples]$ ant -Dchap=misc -Dex=1 run-example"
-msgstr "[examples]$ ant -Dchap=chap2 -Dex=3 run-example"
+msgstr "[examples]$ ant -Dchap=misc -Dex=1 run-example"
#. Tag: para
#: J2EE_Additional_Services.xml:284
@@ -879,10 +1045,13 @@
"service.xml</literal> descriptor with one that has the "
"<literal>ServiceBindingManager</literal> configuration enabled as follows:"
msgstr ""
+"这会创建 <literal>server/production</literal> 配置文件集的拷贝： <literal>server/jboss0</literal> 和 "
+"<literal>server/jboss1</literal>，然后把 <literal>conf/jboss-"
+"service.xml</literal> 描述符用下面启用了 <literal>ServiceBindingManager</literal> 配置的文件替换："
#. Tag: programlisting
#: J2EE_Additional_Services.xml:287
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<mbean code=\"org.jboss.services.binding.ServiceBindingManager\"\n"
" name=\"jboss.system:service=ServiceBindingManager\">\n"
@@ -895,12 +1064,15 @@
" </attribute>\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.services.binding.ServiceBindingManager\"\n"
+" name=\"jboss.system:service=ServiceBindingManager\">\n"
+" <attribute name=\"ServerName\">${jboss.server.name}</"
"attribute>\n"
+" <attribute name=\"StoreURL\">${jboss.server.base.dir}/misc-ex1-"
+"bindings.xml</attribute>\n"
+" <attribute name=\"StoreFactoryClassName\">\n"
+" org.jboss.services.binding.XMLServicesStoreFactory\n"
+" </attribute>\n"
"</mbean>"
#. Tag: para
@@ -918,6 +1090,8 @@
"ports, while the <literal>jboss1</literal> configuration adds 100 to each "
"port number."
msgstr ""
+"这里的配置名称是 <literal>${jboss.server.name}</literal>。JBoss 将用我们用 <literal>-c</literal> 选项传递给 run 脚本的实际服务器配置名替换它。根据运行的配置，它将是 <literal>jboss0</literal> 或 <literal>jboss1</literal>。绑定管理者将找到 <literal>misc-ex1-"
+"bindings.xml</literal> 里相应的服务器配置部分并应用覆盖。对于端口，<literal>jboss0</literal> 配置使用缺省设置，而 <literal>jboss1</literal> 配置则为每个端口号码加上 100。"
#. Tag: para
#: J2EE_Additional_Services.xml:291
@@ -929,13 +1103,13 @@
"console log are different for the <literal>jboss1</literal> server. To test "
"out that both instances work correctly, try accessing the web server of the "
"first JBoss on port 8080 and then try the second JBoss instance on port 8180."
-msgstr ""
+msgstr "要测试这个示例配置，可以用之前创建的 <literal>jboss0</literal> and <literal>jboss1</literal> 配置文件集来启动两个 JBoss 实例。对于 <literal>jboss1</literal> 服务器，在控制台日志里你可以发现端口号码的不同。要测试这两个实例是否正常工作，你可以用端口 8080 访问第一个 JBoss 实例的 web 服务器，然后用端口 8180 访问第二个 JBoss 实例。"
#. Tag: title
#: J2EE_Additional_Services.xml:299
-#, fuzzy, no-c-format
+#, no-c-format
msgid "RMI Dynamic Class Loading"
-msgstr "动态关联抓取"
+msgstr "RMI 动态类加载"
#. Tag: para
#: J2EE_Additional_Services.xml:300
@@ -944,38 +1118,34 @@
"The <literal>WebService</literal> MBean provides dynamic class loading for "
"RMI access to the server EJBs. The configurable attributes for the service "
"are as follows:"
-msgstr ""
+msgstr "<literal>WebService</literal> MBean 为 RMI 访问服务器的 EJB 提供了动态的类加载功能。这个访问的可配置属性是："
#. Tag: para
#: J2EE_Additional_Services.xml:305
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Port</emphasis>: the <literal>WebService</literal> "
"listening port number. A port of 0 will use any available port."
-msgstr ""
-"<emphasis role=\"bold\">PartitionObjectName</emphasis>：与代理关联的群集服务"
-"的 JMX <literal>ObjectName</literal>。"
+msgstr "<emphasis role=\"bold\">Port</emphasis>：<literal>WebService</literal> 侦听的端口号码。0 值表示任何可用的端口。"
#. Tag: para
#: J2EE_Additional_Services.xml:310
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Host</emphasis>: Set the name of the public "
"interface to use for the host portion of the RMI codebase URL."
-msgstr ""
-"<emphasis role=\"bold\">name</emphasis>：构造函数的名字，它必须和实现类名一"
-"致。"
+msgstr "<emphasis role=\"bold\">Host</emphasis>：设置 RMI codebase URL 的主机部分。"
#. Tag: para
#: J2EE_Additional_Services.xml:315
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">BindAddress</emphasis>: the specific address the "
"<literal>WebService</literal> listens on. This can be used on a multi-homed "
"host for a <literal>java.net.ServerSocket</literal> that will only accept "
"connect requests to one of its addresses."
msgstr ""
-"<emphasis role=\"bold\">BindAddress</emphasis>：<literal>NamingService</"
+"<emphasis role=\"bold\">BindAddress</emphasis>：<literal>WebService</"
"literal> 侦听的特定地址。它可以用在多宿主主机上，使用只接受其中一个地址的连接"
"请求的 <literal>java.net.ServerSocket</literal>。"
@@ -999,7 +1169,7 @@
"<emphasis role=\"bold\">DownloadServerClasses</emphasis>: A flag indicating "
"if the server should attempt to download classes from thread context class "
"loader when a request arrives that does not have a class loader key prefix."
-msgstr ""
+msgstr "<emphasis role=\"bold\">DownloadServerClasses</emphasis>：指定当不带有类加载器键值前缀的请求到达时，服务器是否应该试图从线程上下文类加载器下载类。"
#. Tag: para
#: J2EE_Additional_Services.xml:330
@@ -1010,25 +1180,24 @@
"the thread context class loader. Note that allowing this is generally a "
"security risk as it allows access to server configuration files which may "
"contain security settings."
-msgstr ""
+msgstr "<emphasis role=\"bold\">DownloadResources</emphasis>：指定服务器是否应该试图用线程上下文类加载器下载非类文件资源。注意，设定这个标记通常具有安全方面的风险，因为它允许对可能包含安全性设置的服务器配置文件的访问。"
#. Tag: para
#: J2EE_Additional_Services.xml:335
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ThreadPool</emphasis>: The <literal>org.jboss.util."
"threadpool.BasicThreadPoolMBean</literal> instance thread pool used for the "
"class loading."
msgstr ""
-"<emphasis role=\"bold\">LoadBalancePolicy</emphasis>：与代理关联的 "
-"<literal>org.jboss.ha.framework.interfaces.LoadBalancePolicy</literal> 接口实"
-"现的类名。"
+"<emphasis role=\"bold\">ThreadPool</emphasis>：用于类加载的 <literal>org.jboss.util."
+"threadpool.BasicThreadPoolMBean</literal> 实例线程池。"
#. Tag: title
#: J2EE_Additional_Services.xml:343
#, no-c-format
msgid "Scheduling Tasks"
-msgstr ""
+msgstr "任务调度"
#. Tag: para
#: J2EE_Additional_Services.xml:344
@@ -1051,12 +1220,15 @@
"timer service for the basic scheduling. They extend the behavior of the "
"timer service as described in the following sections."
msgstr ""
+"JBoss 在 <literal>org."
+"jboss.varia.scheduler.Scheduler</literal> 和 <literal>org.jboss.varia."
+"scheduler.ScheduleManager</literal> MBean 里包含了两种不同的 JMX 定时器服务。这两者都依赖 JMX 定时器服务来进行基本的调度。如后续章节所示，它们扩展了定时器服务。"
#. Tag: title
#: J2EE_Additional_Services.xml:351
#, no-c-format
msgid "org.jboss.varia.scheduler.Scheduler"
-msgstr ""
+msgstr "org.jboss.varia.scheduler.Scheduler"
#. Tag: para
#: J2EE_Additional_Services.xml:352
@@ -1065,33 +1237,32 @@
"The Scheduler differs from the <literal>TimerMBean</literal> in that the "
"<literal>Scheduler</literal> directly invokes a callback on an instance of a "
"user defined class, or an operation of a user specified MBean."
-msgstr ""
+msgstr "这个调度程序（Scheduler）和 <literal>TimerMBean</literal> 不同，因为 <literal>Scheduler</literal> 直接调用用户自定义类实例的回调方法、或是用户指定的 MBean 的操作。"
#. Tag: para
#: J2EE_Additional_Services.xml:357
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">InitialStartDate</emphasis>: Date when the initial "
"call is scheduled. It can be either:"
-msgstr ""
-"<emphasis role=\"bold\">InitialStateRetrievalTimeout</emphasis> 指定的取得初"
-"始状态所需要等待的时间（毫秒数）。"
+msgstr "<emphasis role=\"bold\">InitialStartDate</emphasis>：初始调用预定的日期。它可以是："
#. Tag: para
#: J2EE_Additional_Services.xml:362
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<literal>NOW</literal>: date will be the current time plus 1 seconds"
-msgstr "<literal>\".\"</literal> — 映射为父元素"
+msgstr "<literal>NOW</literal>：当前时间加上 1 秒。"
#. Tag: para
#: J2EE_Additional_Services.xml:367
#, no-c-format
msgid "A number representing the milliseconds since 1/1/1970"
-msgstr ""
+msgstr "代表从 1/1/1970 起的毫秒数"
#. Tag: para
#: J2EE_Additional_Services.xml:372
#, no-c-format
+#, fuzzy
msgid ""
"Date as String able to be parsed by <literal>SimpleDateFormat</literal> with "
"default format pattern \"<literal>M/d/yy h:mm a</literal>\". If the date is "
@@ -1101,6 +1272,8 @@
"start at the next scheduled time. When no start date is available in the "
"future the <literal>Scheduler</literal> will not start."
msgstr ""
+"字符型的日期可以用 <literal>SimpleDateFormat</literal> 和缺省格式 \"<literal>M/d/yy h:mm a</literal>\" 进行解析。如果这个日期是过去的日期，<literal>Scheduler</literal> 将 "
+"这意味着当你重启 MBean（如重启 JBoss）时，它将在下一个预定的时间启动。当未来没有可用的启动日期时，<literal>Scheduler</literal> 将不会启动。"
#. Tag: para
#: J2EE_Additional_Services.xml:377
@@ -1604,6 +1777,8 @@
"that the beanshell script has a reference to the MBean server and can "
"execute operations against other MBeans."
msgstr ""
+"下面的例子解释了 <literal>ScriptingListener</"
+"literal> 的用法。当之前配置的定时器产生 heartbeat 通知时，beanshell 脚本将被执行，把当前的内存值输出到标准输出上（也可以重定向到某个日志文件里）。请注意，beanshell 脚本里有对 MBean 服务器的引用，它可以执行针对其他 MBean 的操作。"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:543
@@ -1632,6 +1807,28 @@
" </attribute>\n"
"</mbean>"
msgstr ""
+"<mbean code=\"org.jboss.monitor.services.ScriptingListener\" \n"
+" name=\"jboss.monitor:service=ScriptingListener\"> \n"
+" <attribute name=\"SubscriptionList\">\n"
+" <subscription-list>\n"
+" <mbean name=\"jboss.monitor:name=Heartbeat,type=Timer\"/>\n"
+" </subscription-list>\n"
+" </attribute>\n"
+" <attribute name=\"ScriptLanguage\">beanshell</attribute>\n"
+" <attribute name=\"Script\">\n"
+" <![CDATA[\n"
+" import javax.management.ObjectName;\n"
+"\n"
+" /* poll free memory and thread count */ \n"
+" ObjectName target = new ObjectName(\"jboss.system:type=ServerInfo\");\n"
+"\n"
+" long freeMemory = server.getAttribute(target, \"FreeMemory\");\n"
+" long threadCount = server.getAttribute(target, \"ActiveThreadCount\");\n"
+"\n"
+" log.info(\"freeMemory\" + freeMemory + \", threadCount\" + threadCount);\n"
+"]]>\n"
+" </attribute>\n"
+"</mbean>"
#. Tag: para
#: J2EE_Additional_Services.xml:544
@@ -1643,12 +1840,14 @@
"notifications that could be generated from a timer. Additionally, any MBean "
"can be coded to listen for timer-generated notifications."
msgstr ""
+"当然，你并不仅限于这些 JBoss 提供的通知 listener。其他服务，如 barrier 服务（参考 <xref linkend="
+"\"Additional_Services-The_BarrierController_Service\"/>），接受并处理定时器产生的通知。此外，你可以对任何 MBean 进行编程，使它侦听定时器产生的通知。"
#. Tag: title
#: J2EE_Additional_Services.xml:550
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The BarrierController Service"
-msgstr "The ServiceController MBean"
+msgstr "BarrierController Service"
#. Tag: para
#: J2EE_Additional_Services.xml:551
@@ -1662,6 +1861,8 @@
"<literal>serviceB.start()</literal> is called before <literal>serviceA.start"
"()</literal>."
msgstr ""
+"用 <depends> 标记表示服务之间的依赖关系是使一个服务的生命周期依赖于另外一个服务的方便的办法。例如，当 <literal>serviceA</literal> 依赖于 <literal>serviceB</literal> 时，JBoss 将确保 <literal>serviceB.create()</literal> 在 <literal>serviceA.create()</literal> 之前被调用，且<literal>serviceB.start()</literal> 在 <literal>serviceA.start"
+"()</literal> 之前被调用。"
#. Tag: para
#: J2EE_Additional_Services.xml:554
@@ -1674,6 +1875,8 @@
"operations are exposed so you cannot simply express a dependency like: if "
"JBoss is fully started then start my own service."
msgstr ""
+"然而，有时候服务并不能遵循 JBoss 的生命周期模型。例如，它们不开放 create/start/stop/destroy 等生命周期方法。<literal>jboss.system:type=Server "
+"MBean</literal> 就是一个例子，它代表 JBoss 服务器自身。所有生命周期方法都不开放，你不能够简单地表达依赖关系，如：如果 JBoss 完全地启动了就启动我自己的服务。"
#. Tag: para
#: J2EE_Additional_Services.xml:557
@@ -1687,6 +1890,8 @@
"started. So putting a dependency on this MBean, if we want to hit a webpage "
"through Tomcat, will do no good."
msgstr ""
+"或者，即使它们遵循 JBoss 的生命周期模型，完成某个生命周期方法（如 <literal>start</literal> 方法）并不足以描述依赖关系。例如，将 Tomcat 服务器内嵌在 JBoss 里的 <literal>jboss.web:"
+"service=WebServer</literal> MBean 直到服务器完全启动后才启动 Tomcat 连接器。所以，根据这个 MBean 上的依赖关系，如果我们想通过 Tomcat 访问一个 web 页面，那将很差劲。"
#. Tag: para
#: J2EE_Additional_Services.xml:560
@@ -1703,6 +1908,9 @@
"implement more complex dependencies. This technique has been generalized "
"with the barrier controller service."
msgstr ""
+"目前我们用 JMX 通知解决这种并非关键的依赖关系。例如，当服务器完全启动后，<literal>jboss.system:type=Server</literal> "
+"MBean 产生一个类型为 <literal>org.jboss.system.server.started</"
+"literal> 的通知，而在关闭后产生一个类型为 <literal>org.jboss.system.server.stopped</literal> 的通知。类似地，当 Tomcat 连接器启动后，<literal>jboss.web:service=WebServer</literal> 产生一个类型为 <literal>jboss.tomcat.connectors.started</literal> 的通知。服务可以订阅这些通知来实现更为复杂的依赖关系。Barrier controller 服务推广了这种技术。"
#. Tag: para
#: J2EE_Additional_Services.xml:563
@@ -1712,7 +1920,7 @@
"<literal>ListenerServiceMBeanSupport</literal> and thus can subscribe to any "
"notification in the system. It uses the received notifications to control "
"the lifecycle of a dynamically created MBean called the barrier."
-msgstr ""
+msgstr "Barrier controller 是继承了 <literal>ListenerServiceMBeanSupport</literal> 的一个相对简单的 MBean 服务，它订阅了系统里的任何通知。它使用接收的通知来控制名为 barrier 的动态创建的 MBean 的生命周期。"
#. Tag: para
#: J2EE_Additional_Services.xml:566
@@ -1847,6 +2055,80 @@
" \n"
"</server>"
msgstr ""
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<!-- $Id: J2EE_Additional_Services.xml,v 1.4 2007/06/22 08:38:25 skittoli "
+"Exp $ -->\n"
+"\n"
+"<server>\n"
+" <!--\n"
+" In this example we have the BarrierController controlling a Barrier\n"
+" that is started when we receive the \"jboss.tomcat.connectors.started\"\n"
+" notification from the Tomcat mbean, and stopped when we receive the\n"
+" \"org.jboss.system.server.stopped\" notification from the server mbean.\n"
+" \n"
+" The dependent services need only define a dependency on the Barrier "
+"mbean!\n"
+" -->\n"
+" <mbean code=\"org.jboss.system.BarrierController\"\n"
+" name=\"jboss:service=BarrierController\">\n"
+" \n"
+" <!-- Whether to have the Barrier initially started or not -->\n"
+" <attribute name=\"BarrierEnabledOnStartup\">false</"
+"attribute>\n"
+" \n"
+" <!-- Whether to subscribe for notifications after startup -->\n"
+" <attribute name=\"DynamicSubscriptions\">true</attribute>\n"
+" \n"
+" <!-- Dependent services will depend on this mbean -->\n"
+" <attribute name=\"BarrierObjectName\">jboss:name=TomcatConnector,"
+"type=Barrier</attribute>\n"
+" \n"
+" <!-- The notification subscription handback that starts the barrier --"
+">\n"
+" <attribute name=\"StartBarrierHandback\">start</attribute>\n"
+" \n"
+" <!-- The notification subscription handback that stops the barrier --"
+">\n"
+" <attribute name=\"StopBarrierHandback\">stop</attribute>\n"
+" \n"
+" <!-- The notifications to subscribe for, along with their handbacks --"
+">\n"
+" <attribute name=\"SubscriptionList\">\n"
+" <subscription-list>\n"
+" <mbean name=\"jboss.web:service=WebServer\" handback=\"start"
+"\">\n"
+" <filter factory=\"NotificationFilterSupportFactory\">\n"
+" <enable type=\"jboss.tomcat.connectors.started\"/>\n"
+" </filter>\n"
+" </mbean>\n"
+" <mbean name=\"jboss.system:type=Server\" handback=\"stop\">\n"
+" <filter factory=\"NotificationFilterSupportFactory\">\n"
+" <enable type=\"org.jboss.system.server.stopped\"/>\n"
+" </filter>\n"
+" </mbean> \n"
+" </subscription-list>\n"
+" </attribute>\n"
+" </mbean>\n"
+"\n"
+" <!--\n"
+" An example service that depends on the Barrier we declared above.\n"
+" This services creates a background thread and monitors the memory\n"
+" usage. When it exceeds the defined thresholds it emits notifications\n"
+" -->\n"
+" <mbean code=\"org.jboss.monitor.services.MemoryMonitor\"\n"
+" name=\"jboss.monitor:service=MemoryMonitor\">\n"
+"\n"
+" <attribute name=\"FreeMemoryWarningThreshold\">20m</"
+"attribute>\n"
+" <attribute name=\"FreeMemoryCriticalThreshold\">15m</"
+"attribute>\n"
+" \n"
+" <!-- The BarrierObjectName configured in the BarrierController --"
+">\n"
+" <depends>jboss:name=TomcatConnector,type=Barrier</depends>\n"
+" </mbean>\n"
+" \n"
+"</server>"
#. Tag: para
#: J2EE_Additional_Services.xml:579
@@ -1866,7 +2148,7 @@
#: J2EE_Additional_Services.xml:585
#, no-c-format
msgid "Exposing MBean Events via SNMP"
-msgstr ""
+msgstr "通过 SNMP 开放 MBean 事件"
#. Tag: para
#: J2EE_Additional_Services.xml:586
@@ -1890,6 +2172,8 @@
"can then be configured to intercept the notification and map it onto an SNMP "
"traps. The adaptor uses the JoeSNMP package from OpenNMS as the SNMP engine."
msgstr ""
+"这个服务可以用来集成 JBoss 和更高的系统/网络管理平台（如 HP OpenView），使 MBean 为这些系统所用。MBean 开发人员可以为任何重要事件（如服务器的冷启动）产生 notification 来开发 MBean，"
+"然后可以配置适配器来拦截通知并映射到 SNMP trap。适配器把 OpenNMS 里的 JoeSNMP 软件包作为 SNMP 引擎使用。"
#. Tag: para
#: J2EE_Additional_Services.xml:592
@@ -1900,23 +2184,22 @@
"you'll need to copy it to your configuration if you want to use it. "
"Inside the snmp-adaptor.sar directory, there are two configuration files "
"that control the SNMP service."
-msgstr ""
+msgstr "SNMP 服务在 <literal>snmp-adaptor.sar</literal> 里进行配置。这个服务只在 <literal>all</literal> 配置里可用，所以你如果要使用它，你将需要把相关配置复制到你的配置里。在 snmp-adaptor.sar 目录里，有两个用于考之 SNMP 服务的配置文件。"
#. Tag: para
#: J2EE_Additional_Services.xml:597
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">managers.xml</emphasis>: configures where to send "
"traps. The content model for this file is shown in <xref linkend="
"\"_Exposing_MBean_Events_via_SNMP-The_schema_for_the_SNMP_managers_file\"/>."
msgstr ""
-"<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集（参"
-"看 <xref linkend=\"jbosscache-jgroups\"/>）指定 JGroup 配置选项的元素"
-"（element）。"
+"<emphasis role=\"bold\">managers.xml</emphasis>：配置往哪发送 trap。<xref linkend="
+"\"_Exposing_MBean_Events_via_SNMP-The_schema_for_the_SNMP_managers_file\"/> 展示了这个文件的内容模型。"
#. Tag: para
#: J2EE_Additional_Services.xml:602
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">notifications.xml</emphasis>: specifies the exact "
"mapping of each notification type to a corresponding SNMP trap. The content "
@@ -1924,9 +2207,9 @@
"\"_Exposing_MBean_Events_via_SNMP-"
"The_schema_for_the_notification_to_trap_mapping_file\"/>."
msgstr ""
-"<emphasis role=\"bold\">PartitionConfig</emphasis> 是一个用来为这个群集（参"
-"看 <xref linkend=\"jbosscache-jgroups\"/>）指定 JGroup 配置选项的元素"
-"（element）。"
+"<emphasis role=\"bold\">notifications.xml</emphasis>：指定每个通知类型和对应的 SNMP trap 的确切映射关系。<xref linkend="
+"\"_Exposing_MBean_Events_via_SNMP-"
+"The_schema_for_the_notification_to_trap_mapping_file\"/> 展示了这文件的内容模型。"
#. Tag: para
#: J2EE_Additional_Services.xml:607
@@ -1936,36 +2219,32 @@
"adaptor.sar/META-INF/jboss-service.xml</literal>. The configurable "
"parameters are:"
msgstr ""
+"<literal>SNMPAgentService</literal> MBean 在 <literal>snmp-"
+"adaptor.sar/META-INF/jboss-service.xml</literal> 里进行配置。其可配置参数是："
#. Tag: para
#: J2EE_Additional_Services.xml:612
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">HeartBeatPeriod</emphasis>: The period in seconds at "
"which heartbeat notifications are generated."
-msgstr ""
-"<emphasis role=\"bold\">descriptors</emphasis>：与通知元数据相关联的任何描述"
-"符。"
+msgstr "<emphasis role=\"bold\">HeartBeatPeriod</emphasis>：以秒为单位的 heartbeat 通知产生的时间间隔。"
#. Tag: para
#: J2EE_Additional_Services.xml:617
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ManagersResName</emphasis>: Specifies the resource "
"name of the <literal>managers.xml</literal> file."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderClass</emphasis> 指定了 "
-"<literal>CacheLoader</literal> 实现的完整类名。"
+msgstr "<emphasis role=\"bold\">ManagersResName</emphasis>：指定 <literal>managers.xml</literal> 文件的资源名称。"
#. Tag: para
#: J2EE_Additional_Services.xml:622
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">NotificationMapResName</emphasis>: Specifies the "
"resource name of the <literal>notications.xml</literal> file."
-msgstr ""
-"<emphasis role=\"bold\">CacheLoaderClass</emphasis> 指定了 "
-"<literal>CacheLoader</literal> 实现的完整类名。"
+msgstr "<emphasis role=\"bold\">NotificationMapResName</emphasis>：指定 <literal>notications.xml</literal> 文件的资源名称。"
#. Tag: para
#: J2EE_Additional_Services.xml:627
@@ -1975,38 +2254,36 @@
"jboss.jmx.adaptor.snmp.agent.TrapFactory</literal> implementation class that "
"takes care of translation of JMX Notifications into SNMP V1 and V2 traps."
msgstr ""
+"<emphasis role=\"bold\">TrapFactoryClassName</emphasis>：处理从 JMX 通知到 SNMP V1 和 V2 trap 的 <literal>org."
+"jboss.jmx.adaptor.snmp.agent.TrapFactory</literal> 实现类。"
#. Tag: para
#: J2EE_Additional_Services.xml:632
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">TimerName</emphasis>: Specifies the JMX ObjectName "
"of the JMX timer service to use for heartbeat notifications."
-msgstr ""
-"<emphasis role=\"bold\">TransactionManagerService</emphasis>：JTA 事务管理服"
-"务的 JMX ObjectName。"
+msgstr "<emphasis role=\"bold\">TimerName</emphasis>：指定用于 heartbeat 通知的 JMX 定时器访问的 JMX ObjectName。"
#. Tag: para
#: J2EE_Additional_Services.xml:637
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">SubscriptionList</emphasis>: Specifies which MBeans "
"and notifications to listen for."
-msgstr ""
-"<emphasis role=\"bold\">descriptors</emphasis>：与通知元数据相关联的任何描述"
-"符。"
+msgstr "<emphasis role=\"bold\">SubscriptionList</emphasis>：指定侦听的 MBean 和通知。"
#. Tag: title
#: J2EE_Additional_Services.xml:643
#, no-c-format
msgid "The schema for the SNMP managers file"
-msgstr ""
+msgstr "SNMP 管理者文件的模式"
#. Tag: title
#: J2EE_Additional_Services.xml:651
#, no-c-format
msgid "The schema for the notification to trap mapping file"
-msgstr ""
+msgstr "notification 到 trap 映射文件的模式"
#. Tag: para
#: J2EE_Additional_Services.xml:658
@@ -2018,5 +2295,5 @@
"configuration to redirect the log output to a file. "
"<literal>SnmpAgentService</literal> and <literal>TrapdService</literal> are "
"not dependent on each other."
-msgstr ""
+msgstr "<literal>TrapdService</literal> 是一个充当 SNMP 管理者的简单的 MBean。它为传入 trap 侦听一个可配置端口并用系统 logger 登记为 DEBUG 消息。你可以修改 log4j 配置来把日志输出重定向到一个文件里。<literal>SnmpAgentService</literal> 和 <literal>TrapdService</literal> 不相互依赖。"
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po 2008-02-11 02:29:19 UTC (rev 69763)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po 2008-02-11 04:37:26 UTC (rev 69764)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Connectors_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-12-09 23:23+0000\n"
-"PO-Revision-Date: 2008-01-31 12:53+1000\n"
+"PO-Revision-Date: 2008-02-11 14:37+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <zh at li.org>\n"
"MIME-Version: 1.0\n"
@@ -1468,6 +1468,11 @@
"The_simplified_JCA_DataSource_configuration_descriptor_top_level_schema_elements"
"\"/>."
msgstr ""
+"<xref linkend="
+"\"Configuring_JDBC_DataSources-"
+"The_simplified_JCA_DataSource_configuration_descriptor_top_level_schema_elements"
+"\"/> 里展示了 <literal>*-ds.xml</"
+"literal> 配置部署文件的顶层 datasource 元素的模式。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:444
@@ -1475,7 +1480,7 @@
msgid ""
"The simplified JCA DataSource configuration descriptor top-level schema "
"elements"
-msgstr ""
+msgstr "简化的 JCA 数据源配置描述符顶层模式元素"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:451
@@ -1483,7 +1488,7 @@
msgid ""
"Multiple datasource configurations may be specified in a configuration "
"deployment file. The child elements of the datasources root are:"
-msgstr ""
+msgstr "多个数据源配置可以在同一个配置部署文件里指定。datasources 根的子元素是："
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:456
@@ -1494,7 +1499,7 @@
"<literal>jboss-service.xml</literal> descriptor that results from the "
"transformation. This may be used to configure services used by the "
"datasources."
-msgstr ""
+msgstr "<emphasis role=\"bold\">mbean</emphasis>：可以指定任何数目的 mbean 元素来定义应该把包含在 <literal>jboss-service.xml</literal> 描述符里的 MBean 服务。这可以用来配置数据源所使用的服务。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:461
@@ -1508,6 +1513,9 @@
"schema is given in <xref linkend=\"Configuring_JDBC_DataSources-"
"The_non_transactional_DataSource_configuration_schema\"/>."
msgstr ""
+"<emphasis role=\"bold\">no-tx-datasource</emphasis>：这个元素用来指定 (<literal>org.jboss.resource.connectionmanager</literal>) "
+"<literal>NoTxConnectionManager</literal> 服务配置。<literal>NoTxConnectionManager</literal> 是一个不支持事务的 JCA 连接管理者。<xref linkend=\"Configuring_JDBC_DataSources-"
+"The_non_transactional_DataSource_configuration_schema\"/> 给出了 <literal>no-tx-datasource</literal> 子元素模式。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:466
@@ -1529,6 +1537,8 @@
"literal> started and is used. The <literal>local-tx-datasource</literal> "
"child element schema is given in"
msgstr ""
+"<emphasis role=\"bold\">local-tx-datasource</emphasis>：这个元素用来指定 (<literal>org.jboss.resource.connectionmanager</literal>) "
+"<literal>LocalTxConnectionManager</literal> 服务配置。<literal>LocalTxConnectionManager</literal> 实现了实现 <literal>XAResource</literal> 并通过事务管理者来管理事务的 <literal>ConnectionEventListener</literal>。为了确保本地事务里的事情全部发生相同的 <literal>ManagedConnection</literal> 里，它包括了一个映射 <literal>ManagedConnection</literal> 的 xid。当连接被请求或带有连接的事务被使用时，它进行检查全局事务里是否有 <literal>ManagedConnection</literal> 存在，如果有就使用它。否则启动 <literal>LocalTransaction</literal> 的 <literal>ManagedConnection</literal> 将被使用。给出了 <literal>local-tx-datasource</literal> 子元素模式。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:471
More information about the jboss-cvs-commits
mailing list