[jboss-cvs] JBossAS SVN: r83767 - 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 2 05:08:10 EST 2009
Author: xhuang at jboss.com
Date: 2009-02-02 05:08:10 -0500 (Mon, 02 Feb 2009)
New Revision: 83767
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po 2009-02-02 09:54:27 UTC (rev 83766)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Clustering_Guide_JNDI.po 2009-02-02 10:08:10 UTC (rev 83767)
@@ -1,18 +1,20 @@
+# translation of Clustering_Guide_JNDI.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007 Free Software Foundation, Inc.
+# Copyright (C) 2007, 2009 Free Software Foundation, Inc.
# Automatically generated, 2007.
#
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2009-02-02 20:07+1000\n"
+"Last-Translator: Xi HUANG\n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Clustering_Guide_JNDI.xml:5
@@ -27,7 +29,7 @@
"JNDI is one of the most important services provided by the application "
"server. The JBoss HA-JNDI (High Availability JNDI) service brings the "
"following features to JNDI:"
-msgstr ""
+msgstr "JNDI 是应用服务器提供的最重要的服务之一。JBoss HA-JNDI（高可用性 JNDI）服务为 JNDI 增添了如下的功能："
#. Tag: para
#: Clustering_Guide_JNDI.xml:10
@@ -37,7 +39,7 @@
"connected to the HA-JNDI service on a particular JBoss AS instance, and that "
"service fails or is shut down, the HA-JNDI client can transparently fail "
"over to another AS instance."
-msgstr ""
+msgstr "命名操作的透明的失效切换。如果 HA-JNDI 命名上下文连接到某个 JBoss AS 实例的 HA-JNDI 服务上，且这个服务发生故障或关闭了，这个 HA-JNDI 客户端可以透明地切换到另外一个 AS 实例。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:15
@@ -46,13 +48,13 @@
"Load balancing of naming operations. An HA-JNDI naming Context will "
"automatically load balance its requests across all the HA-JNDI servers in "
"the cluster."
-msgstr ""
+msgstr "命名操作的负载平衡。HA-JNDI 命名上下文将自动平衡群集里所有 HA-JNDI 服务器的请求负载。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:20
#, no-c-format
msgid "Automatic client discovery of HA-JNDI servers (using multicast)."
-msgstr ""
+msgstr "HA-JNDI 服务器（使用多点传送）的自动客户发现（discovery）。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:25
@@ -61,7 +63,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
@@ -70,7 +72,7 @@
"Cross-cluster lookups. A client can perform a lookup and the server side HA-"
"JNDI service has the ability to find things bound in regular JNDI on any "
"node in the cluster."
-msgstr ""
+msgstr "跨群集查找。客户端可以执行查找，然后服务器端的 HA-JNDI 服务能够找到绑定在群集里任何节点的常规 JNDI 上的对象。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:37
@@ -79,7 +81,7 @@
"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
@@ -92,7 +94,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 ""
+msgstr "对于许多其他基于拦截器的群集服务来说，JNDI 是一个关键组件：这些服务在 JNDI 里进行注册，这样客户端就可以查找其代理并利用它们的服务。为了实现这一点，HA-JNDI 通过确保客户度具有高可用性的方法来查找这些代理。然而，理解使用 HA-JNDI 与否对所查找对象的群集行为没有任何影响是很重要的。例如："
#. Tag: para
#: Clustering_Guide_JNDI.xml:51
@@ -101,7 +103,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
@@ -110,7 +112,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
@@ -131,11 +133,11 @@
"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 代理。这在“客户端配置”章节里会进行详细描述。不需要确保把合适的命名属性提供给 InitialContext，使用 HA-JNDI 的命名上下文对于客户来说是完全透明的。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:70
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"On the server side, he the HA-JNDI service maintains a cluster-wide context "
"tree. The cluster wide tree is always available as long as there is one node "
@@ -144,7 +146,7 @@
"bound into the local JNDI context tree. An application can bind its objects "
"to either tree. The design rationale for this architecture is as follows:"
msgstr ""
-"JBoss HA-JNDI （高可用性 JNDI）服务维护了一个跨群集的上下文树（context "
+"在服务器端，JBoss HA-JNDI （高可用性 JNDI）服务维护了一个跨群集的上下文树（context "
"tree）。只要群集里有一个节点，这个树就会存在。群集里的每个 JNDI 节点也维护子"
"集的本地 JNDI 上下文。服务器端的应用程序可以把它的对象绑定在两者中的任意一个"
"上。在本部分内容里，你将学习怎样区分这两种树和在应用部署时的最佳做法。这个架"
@@ -152,7 +154,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:75
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"It avoids migration issues with applications that assume that their JNDI "
"implementation is local. This allows clustering to work out-of-the-box with "
@@ -163,12 +165,12 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:81
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"In a homogeneous cluster, this configuration actually cuts down on the "
"amount of network traffic. A homogenous cluster is one where the same types "
"of objects are bound under the same names on each node."
-msgstr "在同样的群集里，这个配置实际上降低了网络的负载。"
+msgstr "在同样的群集里，这个配置实际上降低了网络的负载。同质群集是指的相同类型的对象以相同的名字绑定在每个节点上。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:86
@@ -183,7 +185,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:92
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"On the server side, a naming <literal>Context</literal> obtained via a call "
"to new <literal>InitialContext()</literal> will be bound to the local-only, "
@@ -191,11 +193,10 @@
"homes and such will not be bound to the cluster-wide JNDI Context, but "
"rather, each home will be bound into the local JNDI."
msgstr ""
-"在服务器端，<literal>new InitialContext()</literal> 将会绑定到一个仅用于本地"
+"在服务器端，通过 <literal>new InitialContext()</literal> 获得的命名 <literal>Context</literal>将会绑定到一个仅用于本地"
"的，非跨群集的 JNDI 上下文（实际上是基本 JNDI）。因此，所有 EJB 主接口"
"（homes）都不会绑定到跨群集的 JNDI 上下文。但是，每个主接口都会绑定到本地 "
-"JNDI 上。当远程的客户通过 HA-JNDI 发起一个查找，HA-JNDI 在全局跨群集上下文找"
-"不到这个对象时会委托给本地 JNDI 上下文。详细的查找规则如下所示。"
+"JNDI 上。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:95
@@ -205,16 +206,18 @@
"the local JNDI Context when it cannot find the object within the global "
"cluster-wide Context. The detailed lookup rule is as follows."
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."
@@ -224,7 +227,7 @@
#. 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 "
@@ -252,18 +255,18 @@
"their proxies are always bound in local JNDI, not HA-JNDI. So, an EJB home "
"lookup done through HA-JNDI will always be delegated to the local JNDI "
"instance."
-msgstr ""
+msgstr "实际上，对象很少会绑定在群集范围的 JNDI 树上；它们通常会绑定在本地的 JNDI 树上。例如，当 EJB 被部署时，它们的代理总是绑定在本地 JNDI 而不是 HA-JNDI 上。所以，通过 HA-JNDI 完成的 EJB Home 查找总是被委托给本地 JNDI 实例。"
#. Tag: title
#: Clustering_Guide_JNDI.xml:117 Clustering_Guide_JNDI.xml:124
#: Clustering_Guide_JNDI.xml:130
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Note"
msgstr "备注"
#. Tag: para
#: Clustering_Guide_JNDI.xml:118
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"If different beans (even of the same type, but participating in different "
"clusters) use the same JNDI name, this means that each JNDI server will have "
@@ -276,16 +279,16 @@
"that across the cluster different names are used for logically different "
"bindings."
msgstr ""
-"所以，当 EJB home 通过 HA-JNDI 查找，总会委托给本地 JNDI 实例。如果不同的 "
+"如果不同的 "
"beans（即使是相同的类型,但在不同的群集里）使用同一个 JNDI 名称，这意味着每个 "
"JNDI 服务器将会有一个不同的 \"target\" 绑定（节点 1 上的 JNDI 将有一个用于 "
"bean A 的绑定,节点 2 会有一个用于 bean B 的相同名字的绑定）。因此，如果客户为"
"这个名字执行 HA-JNDI 查询，这个查询会在群集里的任何 JNDI 服务器上调用并返回本"
-"地绑定的 stub。而且，它未必是客户所希望的正确的 stub!"
+"地绑定的 stub。而且，它未必是客户所希望的正确的 stub! 所以，确保群集里不同的绑定使用不同的名字是最佳办法。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:125
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"You cannot currently use a non-JNP JNDI implementation (i.e. LDAP) for your "
"local JNDI implementation if you want to use HA-JNDI. However, you can use "
@@ -293,14 +296,14 @@
"into the JBoss JNDI namespace. Furthermore, nothing prevents you using one "
"centralized JNDI server for your whole cluster and scrapping HA-JNDI and JNP."
msgstr ""
-"如果你想使用 HA-JNDI，你不能有一个用于本地 JNDI 实现的 non-JNP JNDI 实现"
+"如果你想使用 HA-JNDI，你不能有一个用于本地 JNDI 实现的非 JNP JNDI 实现"
"（如：LDAP）。然而，你可以用 <literal>ExternalContext</literal> MBean 来运用 "
"JNDI 联合把非 JBoss JNDI trees 绑定到 JBoss JNDI 命名空间里。而且，你也可以对"
"整个群集使用集中式的 JNDI 服务器，而不用 HA-JNDI 和 JNP。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:131
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"If a binding is only made available on a few nodes in the cluster (for "
"example because a bean is only deployed on a small subset of nodes in the "
@@ -379,22 +382,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。"
+"<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"
@@ -405,21 +408,22 @@
" 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-"
+"literal> MBean （参看“JBoss 配置”章节）里配置的 HA-"
"JNDI 服务。"
#. Tag: para
@@ -430,11 +434,11 @@
"homed cluster (several JBoss instances on one machine bound to different "
"IPs). A safer method is not to specify the Context.PROVIDER_URL (which does "
"not work in all scenarios) but the partition name property:"
-msgstr ""
+msgstr "然而，这并不适用于所有情况，特别是当运行在多宿主群集（同一主机的多个 JBoss 实例绑定在不同的 IP 上）里时。更安全的方法是不要指定 Context.PROVIDER_URL（它不适用于所有情况）但指定 partition name 属性："
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:179
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Properties p = new Properties();\n"
" p.put(Context.INITIAL_CONTEXT_FACTORY, \"org.jnp.interfaces."
@@ -445,12 +449,14 @@
"name.\n"
" 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);"
+"Properties p = new Properties();\n"
+" p.put(Context.INITIAL_CONTEXT_FACTORY, \"org.jnp.interfaces."
+"NamingContextFactory\");\n"
+" p.put(Context.URL_PKG_PREFIXES, \"jboss.naming:org.jnp.interfaces"
+"\");\n"
+" p.put(\"jnp.partitionName\", \"DefaultPartition\"); // partition "
+"name.\n"
+" return new InitialContext(p);"
#. Tag: para
#: Clustering_Guide_JNDI.xml:180
@@ -464,16 +470,18 @@
"properties, and then programatically create a Properties object that loads "
"that file's contents."
msgstr ""
+"不要试图通过 jndi.properties 文件或者编辑 AS 的 conf/jndi.properties 文件来简化过程。这样做有可能损坏应用程序或应用服务器。如果你想具体化客户端配置，有个办法是部署名字不为 jndi."
+"properties 的文件，然后在程序里创建加载该文件内容的 Properties 对象。"
#. Tag: title
#: Clustering_Guide_JNDI.xml:187
#, no-c-format
msgid "For clients running outside the application server"
-msgstr ""
+msgstr "对于运行在应用服务器外部的客户端"
#. Tag: para
#: Clustering_Guide_JNDI.xml:189
-#, 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 "
@@ -492,10 +500,8 @@
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:191
#, no-c-format
-msgid ""
-"java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
-msgstr ""
-"java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
+msgid "java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
+msgstr "java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100"
#. Tag: para
#: Clustering_Guide_JNDI.xml:192
@@ -511,7 +517,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:196
-#, 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 "
@@ -523,7 +529,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:199
-#, 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 "
@@ -532,12 +538,12 @@
"list has changed since the last call)."
msgstr ""
"下载的 smart stub 包含了必要时失效切换（fail-over）至另一节点的逻辑和更新的当"
-"前运行节点的列表。而且，每次对服务器执行 JNDI 调用后，stub interceptor 里的目"
-"标节点列表都会被更新（只有在上次调用后又有修改的情况下）"
+"前运行节点的列表。而且，每次对服务器执行 JNDI 调用后，代理拦截器里的目"
+"标节点列表都会被更新（只有在上次调用后又有修改的情况下）。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:203
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"If the property string java.naming.provider.url is empty or if all servers "
"it mentions are not reachable, the JNP client will try to discover a HA-JNDI "
@@ -550,23 +556,22 @@
msgstr ""
"如果属性字符串 <literal>java.naming.provider.url</literal> 是空或者它标明的所"
"有服务器是不可到达的，JNP client 会试图通过网络上的多点传送（multicast）调用"
-"来恢复 HA-JNDI 服务器。请参考 <xref linkend=\"clustering-jndi-jboss\"/>关于怎"
+"来恢复 HA-JNDI 服务器。请参考“JBoss 配置”章节里关于怎"
"样在 JNDI 服务器节点上配置自动恢复（auto-discovery）的内容。通过自动恢复，客"
"户端不需要任何配置就可以获得一个有效的 HA-JNDI 服务器节点。当然，为了自动恢复"
-"能够工作，客户应用程序必须和服务器节点（使用 EJB 服务器的 web servlets）在同"
-"一局域网里。局域网和广域网也必须配置成可以传送这样的多点传送数据包。"
+"能够工作，局域网和广域网之间的网络段（Segment）也必须配置成可以传送这样的多点传送数据包。 "
#. Tag: para
#: Clustering_Guide_JNDI.xml:207
-#, 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:209
-#, 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 "
@@ -576,18 +581,18 @@
msgstr ""
"除 <literal>java.naming.provier.url</literal> 属性以外，你还可以指定一系列其"
"他属性。下面的列表展示了当建立一个新的 <literal>InitialContext</literal> 时，"
-"你可以指定的所有客户端属性。"
+"你可以指定的所有客户端属性。（所有的普通 JNDI 使用的标准的、非群集相关的环境属性也是可用的。）"
#. Tag: para
#: Clustering_Guide_JNDI.xml:212
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<literal>java.naming.provider.url</literal>: Provides a list of IP addresses "
"and port numbers for HA-JNDI provider nodes in the cluster. The client tries "
"those providers one by one and uses the first one that responds."
msgstr ""
"<literal>java.naming.provier.url</literal>：提供群集里 HA-JNDI 提供者节点的 "
-"IP 地址和端口号的列表。客户端会尝试这些提供者并使用第一个响应的服务器。"
+"IP 地址和端口号的列表。客户端会尝试这些提供者并使用第一个响应的服务器。 "
#. Tag: para
#: Clustering_Guide_JNDI.xml:217
@@ -603,7 +608,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:222
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<literal>jnp.partitionName</literal>: In an environment where multiple HA-"
"JNDI services bound to distinct clusters (a.k.a. partitions), are running, "
@@ -614,12 +619,11 @@
"discovery select the first HA-JNDI server that responds, irregardless of the "
"cluster partition name."
msgstr ""
-"<literal>jnp.partitionName</literal>：在有多个绑定在不同的群集系统的 HA-JNDI "
+"<literal>jnp.partitionName</literal>：在有多个绑定在不同的群集系统（也称为 Partition）的 HA-JNDI "
"服务的环境里，这个属性允许你配置当使用自动恢复（automatic discovery）特征时广"
-"播至哪个群集。如果你没有使用自动恢复特征（就是说你可在以在 <literal>java."
-"naming.provider.url</literal> 里显性地提供有效的 JNDI 节点的列表），这个属性"
+"播至哪个群集。如果你没有使用自动恢复特征（就是说 jnp.disableDiscovery 为 true），这个属性"
"就不会被使用。在缺省情况下，这个属性不会被设置，自动恢复选择第一个响应的 HA-"
-"JNDI 服务器，而不管在哪个群集系统里。"
+"JNDI 服务器，而不管在哪个群集系统里。 "
#. Tag: para
#: Clustering_Guide_JNDI.xml:225
@@ -634,7 +638,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:229
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<literal>jnp.discoveryGroup</literal>: Determines which multicast group "
"address is used for the automatic discovery. Default is 230.0.0.4. Must "
@@ -642,18 +646,20 @@
"JNDI service."
msgstr ""
"<literal>jnp.discoveryGroup</literal>：决定用于自动恢复的多点传送组地址。它的"
-"缺省值是 <literal>230.0.0.4</literal>。"
+"缺省值是 230.0.0.4。它必须符合服务器端 HA-"
+"JNDI 服务配置的 AutoDiscoveryAddress 值。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:232
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<literal>jnp.discoveryPort</literal>: Determines which multicast group port "
"is used for the automatic discovery. Default is 1102. Must match the value "
"of the AutoDiscoveryPort configured on the server side HA-JNDI service."
msgstr ""
"<literal>jnp.discoveryPort</literal>：决定用于自动恢复的多点传送组端口。它的"
-"缺省值是 <literal>1102</literal>。"
+"缺省值是 1102。它必须符合服务器端 HA-"
+"JNDI 服务配置的 AutoDiscoveryPort 值。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:235
@@ -664,7 +670,7 @@
"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 "<literal>jnp.discoveryTTL</literal>：指定自动发现的 IP 多点传送数据包的 TTL（time-to-live）。这个值代表了在网络设备取消多点传送包之前允许传递的网络 hop 的个数。它并不代表单元时间。"
#. Tag: title
#: Clustering_Guide_JNDI.xml:246
@@ -684,7 +690,7 @@
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:249
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
" name=\"jboss:service=HAJNDI\"> \n"
@@ -696,12 +702,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:250
-#, 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 "
@@ -714,22 +723,20 @@
"literal> MBean（在本章之前的部分曾讨论过）。在其他配置里，你可以把那个元素"
"（element）放在 <literal>jboss-services.xml</literal> 或者 <literal>/"
"deploy</literal> 目录下的其他 JBoss 配置文件里来启用 HA-JNDI 服务。这个 "
-"MBean 的可用属性如下所示。"
+"MBean 的可用属性如下所示。 "
#. Tag: para
#: Clustering_Guide_JNDI.xml:256
-#, 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:259
-#, 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 "
@@ -740,7 +747,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:262
@@ -766,7 +773,7 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:272
-#, 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 "
@@ -774,21 +781,21 @@
"automatically assigns a RMI port."
msgstr ""
"<emphasis role=\"bold\">RmiPort</emphasis> 决定服务器应与下载的 stub 通信所用"
-"的端口。这个属性是可选的。如果它没有设置，服务器会自动分配一个 RMI 端口。"
+"的端口。这个属性是可选的。它的缺省值是 1101。如果它没有设置，服务器会自动分配一个 RMI 端口。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:275
-#, 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> 是一个布尔值标记，它可用"
+"<literal>DiscoveryDisabled</literal> 是一个布尔值标记，它可用"
"来取消自动恢复多点传送侦听者（multicast listener）的配置。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:281
-#, 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 "
@@ -798,8 +805,9 @@
"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:284
@@ -814,16 +822,15 @@
#. Tag: para
#: Clustering_Guide_JNDI.xml:290
-#, 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>，"
-"<literal>BindAddress</literal> 将被使用。"
+"<emphasis role=\"bold\">AutoDiscoveryBindAddress</emphasis> 设置 HA-JNDI 应该侦听自动恢复请求包的接口。如果这个属性没有指定而设置了 <literal>BindAddress</literal>，"
+"<literal>BindAddress</literal> 将被使用。 "
#. Tag: para
#: Clustering_Guide_JNDI.xml:293
@@ -834,7 +841,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:296
@@ -844,7 +851,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 的类名。相关细节请参考之前的“负载平衡策略”章节。"
#. Tag: para
#: Clustering_Guide_JNDI.xml:301
@@ -866,7 +873,7 @@
#. 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"
@@ -919,62 +926,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:308
-#, 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. "
@@ -990,7 +995,7 @@
#. Tag: programlisting
#: Clustering_Guide_JNDI.xml:311
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<![CDATA[\n"
"<mbean code=\"org.jboss.ha.jndi.HANamingService\" \n"
@@ -1001,10 +1006,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