[jboss-cvs] JBossAS SVN: r73106 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 7 07:36:57 EDT 2008
Author: xhuang at jboss.com
Date: 2008-05-07 07:36:57 -0400 (Wed, 07 May 2008)
New Revision: 73106
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po
Log:
update
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po 2008-05-07 11:31:51 UTC (rev 73105)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po 2008-05-07 11:36:57 UTC (rev 73106)
@@ -9,7 +9,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-12-09 23:23+0000\n"
-"PO-Revision-Date: 2008-05-07 16:40+1000\n"
+"PO-Revision-Date: 2008-05-07 21:36+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -64,7 +64,7 @@
"Unified view of JNDI trees cluster-wide. Client can connect to the HA-JNDI "
"service running on any node in the cluster and find objects bound in JNDI on "
"any other node. This is accomplished via two mechanisms:"
-msgstr ""
+msgstr "群集范围的 JNDI 树的统一视图。客户端可以连接至运行在群集里任何节点上的 HA-JNDI 服务并找到綁定在任何其他节点上的 JNDI 里的对象。这通过两个机制来实现："
#. Tag: para
#: Clustering_Guide_JNDI.xml:33
@@ -74,6 +74,8 @@
"JNDI service has the ability to find things bound in regular JNDI on any "
"node in the cluster."
msgstr ""
+"跨群集的查找。客户端可以执行一个查找，服务器端的 HA-"
+"JNDI 服务能够找到綁定在群集里的任何节点上的常规 JNDI 里的对象。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:37
@@ -82,12 +84,11 @@
"A replicated cluster-wide context tree. An object bound into the HA-JNDI "
"service will be replicated around the cluster, and a copy of that object "
"will be available in-VM on each node in the cluster."
-msgstr ""
+msgstr "复制群集范围的上下文树。綁定在 HA-JNDI 服务里的对象将在群集里复制，其拷贝将对于群集里的每个节点里的 VM 可用。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:46
#, no-c-format
-#, fuzzy
msgid ""
"JNDI is a key component for many other interceptor-based clustering "
"services: those services register themselves with the JNDI so that the "
@@ -96,7 +97,7 @@
"to look up those proxies. However, it is important to understand that using "
"HA-JNDI (or not) has no effect whatsoever on the clustering behavior of the "
"objects that are looked up. To illustrate:"
-msgstr "对于许多其他基于拦截器的群集服务来说，JNDI 是一个关键组件："
+msgstr "对于许多其他基于拦截器的群集服务来说，JNDI 是一个关键组件：那些服务向 JNDI 注册，这样客户就可以查找它们的代理并使用相应服务。HA-JNDI 通过确保客户具有高可用性的方法来查找那些代理来实现这一点。然而，理解使用 HA-JNDI 与否对查找的对象的群集行为并无影响是很重要的。例如："
#. Tag: para
#: Clustering_Guide_JNDI.xml:51
@@ -105,7 +106,7 @@
"If an EJB is not configured as clustered, looking up the EJB via HA-JNDI "
"does not somehow result in the addition of clustering capabilities (load "
"balancing of EJB calls, transparent failover, state replication) to the EJB."
-msgstr ""
+msgstr "如果某个 EJB 未配置为参与群集，通过 HA-JNDI 查找这个 EJB 并不会导致它具有群集能力（如 EJB 调用的负载平衡、透明的失效切换以及状态复制）。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:56
@@ -114,7 +115,7 @@
"If an EJB is configured as clustered, looking up the EJB via regular JNDI "
"instead of HA-JNDI does not somehow result in the removal of the bean "
"proxy's clustering capabilities."
-msgstr ""
+msgstr "而如果某个 EJB 被配置为群集的一部分，那通过常规 JNDI 而不是 HA-JNDI 查找这个 EJB 也不会导致它的群集能力的消失。"
#. Tag: title
#: Clustering_Guide_JNDI.xml:66
@@ -135,7 +136,7 @@
"Other than the need to ensure the appropriate naming properties are provided "
"to the InitialContext, the fact that the naming Context is using HA-JNDI is "
"completely transparent to the client."
-msgstr ""
+msgstr "JBoss 的客户端 HA-JNDI 命名上下文基于客户端拦截器架构。客户端获取一个 HA-JNDI 代理对象（通过 InitialContext 对象）并通过这个代理调用远程服务器上 JNDI 查找服务。客户端通过配置 InitialContext 对象使用的命名属性来指定它需要 HA-JNDI 代理。在“Client Configuration”章节我们将详细讨论这些内容。除了需要把合适的命名属性提供给 InitialContext，命名上下文对 HA-JNDI 的使用对于客户来说是完全透明的。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:70
@@ -208,27 +209,27 @@
"When a remote client does a lookup through HA-JNDI, HA-JNDI will delegate to "
"the local JNDI Context when it cannot find the object within the global "
"cluster-wide Context. The detailed lookup rule is as follows."
-msgstr ""
+msgstr "当远程客户通过 HA-JNDI 执行查找时，如果不能在群集范围的上下文里找到这个对象，HA-JNDI 将委托给本地的 JNDI 上下文。详细的查找规则如下。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:100
-#, fuzzy, no-c-format
+#, no-c-format
msgid "If the binding is available in the cluster-wide JNDI tree, return it."
-msgstr "如果这个绑定在跨群集的 JNDI 树（JNDI tree）里可用。"
+msgstr "如果这个绑定在群集范围的 JNDI 树（JNDI tree）里可用，则返回它。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:103
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"If the binding is not in the cluster-wide tree, delegate the lookup query to "
"the local JNDI service and return the received answer if available."
msgstr ""
-"如果这个绑定不在跨群集的树里，它会把查找请求委托给本地 JNDI 服务并返回可用的"
+"如果这个绑定不在群集范围的树里，它会把查找请求委托给本地 JNDI 服务并返回可用的"
"结果。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:106
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"If not available, the HA-JNDI services asks all other nodes in the cluster "
"if their local JNDI service owns such a binding and returns the answer from "
@@ -263,7 +264,7 @@
#: Clustering_Guide_JNDI.xml:130
#, no-c-format
msgid "Note"
-msgstr ""
+msgstr "注意"
#. Tag: para
#: Clustering_Guide_JNDI.xml:118
@@ -383,22 +384,22 @@
#: Clustering_Guide_JNDI.xml:168
#, no-c-format
msgid "For clients running inside the application server"
-msgstr ""
+msgstr "对于运行在应用服务器内部的客户端"
#. Tag: para
#: Clustering_Guide_JNDI.xml:169
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"If you want to access HA-JNDI from inside the application server, you must "
"explicitly get an InitialContext by passing in JNDI properties. The "
"following code shows how to create a naming Context bound to HA-JNDI:"
msgstr ""
-"如果你要从服务器端访问 HA-JNDI，你必须传入 JNDI 属性来显性地得到 "
-"<literal>InitialContext</literal>。下面的代码展示了怎样访问 HA-JNDI。"
+"如果你要从服务器内部访问 HA-JNDI，你必须传入 JNDI 属性来显性地得到 "
+"<literal>InitialContext</literal>。下面的代码展示了怎样创建一个綁定到 HA-JNDI 的命名上下文："
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:172
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Properties p = new Properties(); \n"
" p.put(Context.INITIAL_CONTEXT_FACTORY, \n"
@@ -409,21 +410,21 @@
" return new InitialContext(p);"
msgstr ""
"Properties p = new Properties(); \n"
-"p.put(Context.INITIAL_CONTEXT_FACTORY, \n"
-" \"org.jnp.interfaces.NamingContextFactory\"); \n"
-"p.put(Context.URL_PKG_PREFIXES, \"jboss.naming:org.jnp.interfaces\"); \n"
-"p.put(Context.PROVIDER_URL, \"localhost:1100\"); // HA-JNDI port. \n"
-"return new InitialContext(p);"
+" p.put(Context.INITIAL_CONTEXT_FACTORY, \n"
+" \"org.jnp.interfaces.NamingContextFactory\"); \n"
+" p.put(Context.URL_PKG_PREFIXES, \"jboss.naming:org.jnp.interfaces"
+"\"); \n"
+" p.put(Context.PROVIDER_URL, \"localhost:1100\"); // HA-JNDI port. \n"
+" return new InitialContext(p);"
#. Tag: para
#: Clustering_Guide_JNDI.xml:173
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The Context.PROVIDER_URL property points to the HA-JNDI service configured "
"in the HANamingService MBean (see the section called “JBoss configuration”)."
msgstr ""
-"<literal>Context.PROVIDER_URL</literal> 属性指向 <literal>HANamingService</"
-"literal> MBean （参看 <xref linkend=\"clustering-jndi-jboss\"/>）里配置的 HA-"
+"Context.PROVIDER_URL 属性指向 HANamingService MBean （参看“JBoss configuration”章节）里配置的 HA-"
"JNDI 服务。"
#. Tag: para
@@ -443,11 +444,11 @@
#: Clustering_Guide_JNDI.xml:183
#, no-c-format
msgid "For clients running outside the application server"
-msgstr ""
+msgstr "对于运行在应用服务器外部的客户端"
#. Tag: para
#: Clustering_Guide_JNDI.xml:185
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The JNDI client needs to be aware of the HA-JNDI cluster. You can pass a "
"list of JNDI servers (i.e., the nodes in the HA-JNDI cluster) to the "
@@ -483,19 +484,19 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:192
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"There is no load balancing behavior in the JNP client lookup process itself. "
"It just goes through the provider lists and uses the first available server "
"to obtain the stub. The HA-JNDI provider list only needs to contain a subset "
"of HA-JNDI nodes in the cluster."
msgstr ""
-"JNP 客户的查找过程中没有用到负载平衡。它只是遍历这个列表来使用第一个可用的服"
-"务器。HA-JNDI 提供者列表只需要包含群集里的 HA-JNDI 节点的一个子集。"
+"JNP 客户的查找过程本身没有用到负载平衡。它只是遍历这个列表并第一个可用的服"
+"务器来获取 stub。HA-JNDI 提供者列表只需要包含群集里的 HA-JNDI 节点的一个子集。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:195
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The downloaded smart proxy contains the list of currently running nodes and "
"the logic to load balance naming requests and to fail-over to another node "
@@ -503,9 +504,9 @@
"server, the list of targets in the proxy interceptor is updated (only if the "
"list has changed since the last call)."
msgstr ""
-"下载的 smart stub 包含了必要时失效切换（fail-over）至另一节点的逻辑和更新的当"
-"前运行节点的列表。而且，每次对服务器执行 JNDI 调用后，stub interceptor 里的目"
-"标节点列表都会被更新（只有在上次调用后又有修改的情况下）"
+"下载的 smart proxy 包含了必要时失效切换（fail-over）至另一节点的逻辑和更新的当"
+"前运行节点的列表。而且，每次对服务器执行 JNDI 调用后，proxy interceptor 里的目"
+"标节点列表都会被更新（只有在上次调用后又有修改的情况下）。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:199
@@ -530,15 +531,15 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:203
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"By default the auto-discovery feature uses multicast group address 230.0.0.4 "
"and port1102."
-msgstr "自动恢复（auto-discovery）特征使用多点传送组地址 230.0.0.4:1102。"
+msgstr "自动发现（auto-discovery）特征使用的缺省多点传送组地址是 230.0.0.4，端口为 1102。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:205
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"In addition to the <literal>java.naming.provider.url</literal> property, you "
"can specify a set of other properties. The following list shows all "
@@ -547,8 +548,8 @@
"properties used with regular JNDI are also available.)"
msgstr ""
"除 <literal>java.naming.provier.url</literal> 属性以外，你还可以指定一系列其"
-"他属性。下面的列表展示了当建立一个新的 <literal>InitialContext</literal> 时，"
-"你可以指定的所有客户端属性。"
+"他属性。下面的列表展示了当建立一个新的 InitialContext 时，"
+"你可以指定的所有客户端属性。（所有的标准的、非群集相关的和常规 JNDI 一起使用的环境属性也可用。）"
#. Tag: para
#: Clustering_Guide_JNDI.xml:208
@@ -656,7 +657,7 @@
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:245
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
" name=\"jboss:service=HAJNDI\"> \n"
@@ -668,12 +669,15 @@
msgstr ""
"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
" name=\"jboss:service=HAJNDI\"> \n"
-" <depends>jboss:service=DefaultPartition</depends> \n"
-"</mbean>"
+" <depends optional-attribute-name=\"ClusterPartition\" \n"
+" proxy-type=\"attribute\">jboss:service=${jboss.partition."
+"name:DefaultPartition}</depends> \n"
+" \n"
+"<mbean>"
#. Tag: para
#: Clustering_Guide_JNDI.xml:246
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"You can see that this MBean depends on the <literal>DefaultPartition</"
"literal> MBean defined above it (discussed earlier in this chapter). In "
@@ -690,18 +694,16 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:252
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Cluster Partition</emphasis> is a required attribute "
"to inject the HAPartition service that HA-JNDI uses for intra-cluster "
"communication."
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis> 是用来指定节点名称的可选属"
-"性。它的缺省值是 <literal>DefaultPartition</literal>。"
+msgstr "<emphasis role=\"bold\">Cluster Partition</emphasis> 是一个必需属性，它注入 HA-JNDI 用于群集内部通信的 HAPartition 服务。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:255
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">BindAddress</emphasis> is an optional attribute to "
"specify the address to which the HA-JNDI server will bind waiting for JNP "
@@ -712,7 +714,7 @@
msgstr ""
"<emphasis role=\"bold\">BindAddress</emphasis> 是一个可选属性，它指定 HA-"
"JNDI 服务器绑定的等待 JNP 客户连接的地址。它只对多宿主主机（multi-homed "
-"computers）有用。"
+"computers）有用。它的缺省值是系统属性 jboss.bind.address 的值，如果该系统属性未设置，则为主机的缺省地址。JBoss 启动时可以使用 -b 命令行参数来设置 jboss.bind.address。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:258
@@ -738,7 +740,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:268
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">RmiPort</emphasis> determines which port the server "
"should use to communicate with the downloaded stub. This attribute is "
@@ -746,21 +748,21 @@
"automatically assigns a RMI port."
msgstr ""
"<emphasis role=\"bold\">RmiPort</emphasis> 决定服务器应与下载的 stub 通信所用"
-"的端口。这个属性是可选的。如果它没有设置，服务器会自动分配一个 RMI 端口。"
+"的端口。这个属性是可选的。它的缺省值是 1101。如果没有进行设置，服务器会自动分配一个 RMI 端口。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:271
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<literal>DiscoveryDisabled</literal> is a boolean flag that disables "
"configuration of the auto discovery multicast listener."
msgstr ""
-"<emphasis role=\"bold\">DiscoveryDisabled</emphasis> 是一个布尔值标记，它可用"
-"来取消自动恢复多点传送侦听者（multicast listener）的配置。"
+"<literal>DiscoveryDisabled</literal> 是一个布尔值标记，它可用"
+"来禁止自动发现多点传送侦听者（multicast listener）的配置。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:277
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">AutoDiscoveryAddress</emphasis> is an optional "
"attribute to specify the multicast address to listen to for JNDI automatic "
@@ -770,8 +772,8 @@
"JBoss is started."
msgstr ""
"<emphasis role=\"bold\">AutoDiscoveryAddress</emphasis> 是一个可选属性，它指"
-"定侦听的用于 JNDI 自动恢复的多点传送地址。它的缺省值是 <literal>230.0.0.4</"
-"literal>。"
+"定侦听的用于 JNDI 自动发现的多点传送地址。它的缺省值是 jboss.partition.udpGroup 系统属性的值，如果未设置则为 <literal>230.0.0.4</literal>。JBoss 启动时可以使用 -u 命令行参数来设置jboss.partition."
+"udpGroup。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:280
@@ -786,15 +788,14 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:286
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">AutoDiscoveryBindAddress</emphasis> sets the "
"interface on which HA-JNDI should listen for auto-discovery request packets. "
"If this attribute is not specified and a <literal>BindAddress</literal> is "
"specified, the <literal>BindAddress</literal> will be used.."
msgstr ""
-"<emphasis role=\"bold\">AutoDiscoveryBindAddress</emphasis> 设置自动恢复引导"
-"程序绑定的地址。如果这个属性没有指定而设置了 <literal>BindAddress</literal>，"
+"<emphasis role=\"bold\">AutoDiscoveryBindAddress</emphasis>：HA-JNDI 应该对这个地址侦听自动发现请求数据包。如果这个属性没有指定而设置了 <literal>BindAddress</literal>，"
"<literal>BindAddress</literal> 将被使用。"
#. Tag: para
@@ -806,7 +807,7 @@
"number of network hops a multicast packet can be allowed to propagate before "
"networking equipment should drop the packet. Despite its name, it does not "
"represent a unit of time."
-msgstr ""
+msgstr "<emphasis role=\"bold\">AutoDiscoveryTTL</emphasis> 指定用于自动发现的 IP 多点传送数据包的 TTL (time-to-live)。这个值代表在网络设备取消多点传送数据包前所允许的最大 hop 数。它并不表示时间单位。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:292
@@ -816,7 +817,7 @@
"name of the LoadBalancePolicyimplementation that should be included in the "
"client proxy. See the earlier section on “Load-Balancing Policies” for "
"details."
-msgstr ""
+msgstr "<emphasis role=\"bold\">LoadBalancePolicy</emphasis> 指定应该包括在客户端代理里的 LoadBalancePolicyimplementation 的类名。详情请参考之前的“Load-Balancing Policies”章节。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:297
@@ -838,7 +839,7 @@
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:303
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<![CDATA[\n"
" <mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
@@ -891,62 +892,60 @@
" --> \n"
" </mbean>]]>"
msgstr ""
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <depends>\n"
-" jboss:service=${jboss.partition.name:DefaultPartition}\n"
-" </depends> \n"
-" <! -- Name of the partition to which the service is linked --> \n"
-" <attribute name=\"PartitionName\">\n"
-" ${jboss.partition.name:DefaultPartition}\n"
-" </attribute> \n"
-" <! -- Bind address of bootstrap and HA-JNDI RMI endpoints --> \n"
-" <attribute name=\"BindAddress\">${jboss.bind.address}</"
-"attribute> \n"
-" <! -- Port on which the HA-JNDI stub is made available --> \n"
-" <attribute name=\"Port\">1100</attribute> \n"
-" <! -- RmiPort to be used by the HA-JNDI service once bound. \n"
-" 0 is for auto. --> \n"
-" <attribute name=\"RmiPort\">1101</attribute> \n"
-" <! -- Accept backlog of the bootstrap socket --> \n"
-" <attribute name=\"Backlog\">50</attribute> \n"
-" <! -- The thread pool service used to control the bootstrap and \n"
-" auto discovery lookups --> \n"
-" <depends optional-attribute-name=\"LookupPool\" \n"
-" proxy-type=\"attribute\">jboss.system:service=ThreadPool</"
-"depends>\n"
-"\n"
-" <! -- A flag to disable the auto discovery via multicast --> \n"
-" <attribute name=\"DiscoveryDisabled\">false</attribute> \n"
-" <! -- Set the auto-discovery bootstrap multicast bind address. --"
-"> \n"
-" <attribute name=\"AutoDiscoveryBindAddress\">\n"
-" ${jboss.bind.address}\n"
-" </attribute> \n"
-" \n"
-" <! -- Multicast Address and group port used for auto-discovery --"
-"> \n"
-" <attribute name=\"AutoDiscoveryAddress\">\n"
-" ${jboss.partition.udpGroup:230.0.0.4}\n"
-" </attribute> \n"
-" <attribute name=\"AutoDiscoveryGroup\">1102</attribute> \n"
-" <! -- The TTL (time-to-live））for autodiscovery IP multicast packets "
-"--> \n"
-" <attribute name=\"AutoDiscoveryTTL\">16</attribute>\n"
-"\n"
-" <! -- Client socket factory to be used for client-server \n"
-" RMI invocations during JNDI queries \n"
-" <attribute name=\"ClientSocketFactory\">custom</attribute> \n"
-" --> \n"
-" <! -- Server socket factory to be used for client-server \n"
-" RMI invocations during JNDI queries \n"
-" <attribute name=\"ServerSocketFactory\">custom</attribute> \n"
-" --> \n"
-"</mbean>"
+"<![CDATA[\n"
+" <mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
+" name=\"jboss:service=HAJNDI\"> \n"
+" <!-- We now inject the partition into the HAJNDI service instead \n"
+" of requiring that the partition name be passed --> \n"
+" <depends optional-attribute-name=\"ClusterPartition\" \n"
+" proxy-type=\"attribute\">jboss:service=${jboss.partition.name:"
+"DefaultPartition}</depends> \n"
+" <!-- Bind address of bootstrap and HA-JNDI RMI endpoints --> \n"
+" <attribute name=\"BindAddress\">${jboss.bind.address}</attribute> \n"
+" <!-- Port on which the HA-JNDI stub is made available --> \n"
+" <attribute name=\"Port\">1100</attribute> \n"
+" <!-- RmiPort to be used by the HA-JNDI service once bound. 0 => "
+"auto. --> \n"
+" <attribute name=\"RmiPort\">1101</attribute> \n"
+" <!-- Accept backlog of the bootstrap socket --> \n"
+" <attribute name=\"Backlog\">50</attribute> \n"
+" <!-- The thread pool service used to control the bootstrap and auto "
+"discovery lookups --> \n"
+" <depends optional-attribute-name=\"LookupPool\" \n"
+" proxy-type=\"attribute\">jboss.system:service=ThreadPool</"
+"depends> \n"
+" <!-- A flag to disable the auto discovery via multicast --> \n"
+" <attribute name=\"DiscoveryDisabled\">false</attribute> \n"
+" <!-- Set the auto-discovery bootstrap multicast bind address. If "
+"not \n"
+" specified and a BindAddress is specified, the BindAddress will be "
+"used. --> \n"
+" <attribute name=\"AutoDiscoveryBindAddress\">${jboss.bind.address}</"
+"attribute> \n"
+" <!-- Multicast Address and group port used for auto-discovery --> \n"
+" <attribute name=\"AutoDiscoveryAddress\">${jboss.partition."
+"udpGroup:230.0.0.4}</attribute> \n"
+" <attribute name=\"AutoDiscoveryGroup\">1102</attribute> \n"
+" <!-- The TTL (time-to-live) for autodiscovery IP multicast packets "
+"--> \n"
+" <attribute name=\"AutoDiscoveryTTL\">16</attribute> \n"
+" <!-- The load balancing policy for HA-JNDI --> \n"
+" <attribute name=\"LoadBalancePolicy\">org.jboss.ha.framework."
+"interfaces.RoundRobin</attribute> \n"
+" \n"
+" <!-- Client socket factory to be used for client-server \n"
+" RMI invocations during JNDI queries \n"
+" <attribute name=\"ClientSocketFactory\">custom</attribute> \n"
+" --> \n"
+" <!-- Server socket factory to be used for client-server \n"
+" RMI invocations during JNDI queries \n"
+" <attribute name=\"ServerSocketFactory\">custom</attribute> \n"
+" --> \n"
+" </mbean>]]>"
#. Tag: para
#: Clustering_Guide_JNDI.xml:304
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"It is possible to start several HA-JNDI services that use different "
"clusters. This can be used, for example, if a node is part of many clusters. "
@@ -958,11 +957,11 @@
"你可以启动几个使用不同群集的 HA-JNDI 服务。例如，这可以用在如果某一节点是属于"
"多个群集系统的情况下。这个时候，你要确保给不同服务设置了不同的端口号或 IP 地"
"址。例如，如果你想把 HA-JNDI 与 example 群集挂钩并改变绑定的端口，Mbean 描述"
-"会象下面的样子。"
+"会和下面类似。"
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:307
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<![CDATA[\n"
"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
@@ -973,11 +972,12 @@
" <attribute name=\"Port\">56789</attribute> \n"
"</mbean> ]]>"
msgstr ""
-"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
-" name=\"jboss:service=HAJNDI\"> \n"
-" <depends>jboss:service=MySpecialPartition</depends> \n"
-" <attribute name=\"PartitionName\">MySpecialPartition</"
-"attribute> \n"
-" <attribute name=\"Port\">56789</attribute> \n"
-"</mbean>"
+"<![CDATA[\n"
+"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
+" name=\"jboss:service=HAJNDI\"> \n"
+"\n"
+" <depends optional-attribute-name=\"ClusterPartition\" \n"
+" proxy-type=\"attribute\">jboss:service=MySpecialPartition</depends> \n"
+" <attribute name=\"Port\">56789</attribute> \n"
+"</mbean> ]]>"
More information about the jboss-cvs-commits
mailing list