[jboss-cvs] JBossAS SVN: r102212 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Mar 10 01:05:18 EST 2010
Author: xhuang at jboss.com
Date: 2010-03-10 01:05:17 -0500 (Wed, 10 Mar 2010)
New Revision: 102212
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po
Log:
update
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po 2010-03-10 06:02:00 UTC (rev 102211)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po 2010-03-10 06:05:17 UTC (rev 102212)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:17\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-03-09 12:22+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,22 +22,9 @@
msgstr "群集的 Session EJB"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Session EJBs provide remote invocation services. They are clustered based on "
-"the client-side interceptor architecture. The client application for a "
-"clustered session bean is the same as the client for the non-clustered "
-"version of the session bean, except for some minor changes. No code change "
-"or re-compilation is needed on the client side. Now, let's check out how to "
-"configure clustered session beans in EJB 3.0 and EJB 2.x server applications "
-"respectively."
-msgstr ""
-"Session EJBs 提供远程的调用服务。它们按照客户端拦截器架构（client-side "
-"interceptor architecture）组成群集系统。群集的 session bean 的客户应用程序和"
-"非群集的版本是一模一样的，除了对启用 HA-JNDI 查找的 <literal>java.naming."
-"provier.url</literal> 系统属性的少许改动。对于客户端来说，不需要任何的源码改"
-"动或重新编译。现在，让我们看看怎么分别在 EJB 2.x 和 EJB 3.0 服务器应用程序里"
-"配置群集的 session beans。"
+#, no-c-format
+msgid "Session EJBs provide remote invocation services. They are clustered based on the client-side interceptor architecture. The client application for a clustered session bean is the same as the client for the non-clustered version of the session bean, except for some minor changes. No code change or re-compilation is needed on the client side. Now, let's check out how to configure clustered session beans in EJB 3.0 and EJB 2.x server applications respectively."
+msgstr "Session EJBs 提供远程的调用服务。它们按照客户端拦截器架构（client-side interceptor architecture）组成群集系统。除了少许改动，群集的 session bean 的客户应用程序和非群集的版本是一模一样的。对于客户端来说，不需要任何的源码改动或重新编译。现在，让我们看看怎么分别在 EJB 2.x 和 EJB 3.0 服务器应用程序里配置群集的 session bean。"
#. Tag: title
#, no-c-format
@@ -45,144 +32,84 @@
msgstr "EJB 3.0 里的 Stateless Session Bean"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Clustering stateless session beans is probably the easiest case since no "
-"state is involved. Calls can be load balanced to any participating node (i."
-"e. any node that has this specific bean deployed) of the cluster."
-msgstr ""
-"群集的 stateless session beans 有可能是最简单的：因为不涉及到状态，调用可以在"
-"群集里的任何节点（部署有这个 bean 的节点）上进行负载平衡。要群集一个 bean，你"
-"需要修改它的 <literal>jboss.xml</literal> 描述符，使它包含一个 <literal><"
-"clustered></literal> 标签。"
+#, no-c-format
+msgid "Clustering stateless session beans is probably the easiest case since no state is involved. Calls can be load balanced to any participating node (i.e. any node that has this specific bean deployed) of the cluster."
+msgstr "群集的 stateless session beans 有可能是最简单的：因为不涉及到状态，调用可以在群集里的任何节点（部署有这个 bean 的节点）上进行负载平衡。"
#. Tag: para
#, no-c-format
-msgid ""
-"To cluster a stateless session bean in EJB 3.0, simply annotate the bean "
-"class with the <literal>@Clustered</literal> annotation. This annotation "
-"contains optional parameters for overriding both the load balance policy and "
-"partition to use."
-msgstr ""
+msgid "To cluster a stateless session bean in EJB 3.0, simply annotate the bean class with the <literal>@Clustered</literal> annotation. This annotation contains optional parameters for overriding both the load balance policy and partition to use."
+msgstr "要在 EJB 3.0 里群集 stateless session bean，只要简单地用 <literal>@Clustered</literal> 进行注解就可以了。这个注解包含了覆盖负载平衡策略和分区的可选参数。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">partition</emphasis> specifies the name of the "
-"cluster the bean participates in. While the <literal>@Clustered</literal> "
-"annotation lets you override the default partition, "
-"<literal>DefaultPartition</literal>, for an individual bean, you can "
-"override this for all beans using the <literal>jboss.partition.name</"
-"literal> system property."
-msgstr ""
-"<emphasis role=\"bold\">partition-name</emphasis> 指定 bean 所参与的群集名。"
-"它的缺省值是 <literal>DefaultPartition</literal>。缺省的分区名也可以用 "
-"<literal>jboss.partition.name</literal> 系统属性跨系统地被指定。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">partition</emphasis> specifies the name of the cluster the bean participates in. While the <literal>@Clustered</literal> annotation lets you override the default partition, <literal>DefaultPartition</literal>, for an individual bean, you can override this for all beans using the <literal>jboss.partition.name</literal> system property."
+msgstr "<emphasis role=\"bold\">partition</emphasis> 指定 bean 所参与的群集名。虽然 <literal>@Clustered</literal> 注解让你覆盖它的缺省值 <literal>DefaultPartition</literal>，但对于个体的 bean 来说，你可以用 <literal>jboss.partition.name</literal> 系统属性来进行覆盖。"
#. Tag: para
#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">loadBalancePolicy</emphasis> defines the name of a "
-"class implementing <literal>org.jboss.ha.client.loadbalance."
-"LoadBalancePolicy</literal>, indicating how the bean stub should balance "
-"calls made on the nodes of the cluster. The default value, "
-"<literal>LoadBalancePolicy</literal> is a special token indicating the "
-"default policy for the session bean type. For stateless session beans, the "
-"default policy is <literal>org.jboss.ha.client.loadbalance.RoundRobin</"
-"literal>. You can override the default value using your own implementation, "
-"or choose one from the list of available policies:"
-msgstr ""
+msgid "<emphasis role=\"bold\">loadBalancePolicy</emphasis> defines the name of a class implementing <literal>org.jboss.ha.client.loadbalance.LoadBalancePolicy</literal>, indicating how the bean stub should balance calls made on the nodes of the cluster. The default value, <literal>LoadBalancePolicy</literal> is a special token indicating the default policy for the session bean type. For stateless session beans, the default policy is <literal>org.jboss.ha.client.loadbalance.RoundRobin</literal>. You can override the default value using your own implementation, or choose one from the list of available policies:"
+msgstr "<emphasis role=\"bold\">loadBalancePolicy</emphasis> 定义了实现 <literal>org.jboss.ha.client.loadbalance.LoadBalancePolicy</literal> 的类名，指出 bean stub 应该平衡节点间的调用。缺省值 <literal>LoadBalancePolicy</literal> 是一个特殊的令牌，它表示 session bean 类型的缺省策略。对于 stateless session bean，缺省策略是 <literal>org.jboss.ha.client.loadbalance.RoundRobin</literal>。你可以用自己的实现覆盖这个缺省值，或者从可用策略里选择一个："
#. Tag: term
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<literal>org.jboss.ha.client.loadbalance.RoundRobin</literal>"
-msgstr "<literal>org.jboss.cache.TreeCache</literal> (EJB3SFSB)"
+msgstr "<literal>org.jboss.ha.client.loadbalance.RoundRobin</literal>"
#. Tag: para
#, no-c-format
-msgid ""
-"Starting with a random target, always favors the next available target in "
-"the list, ensuring maximum load balancing always occurs."
-msgstr ""
+msgid "Starting with a random target, always favors the next available target in the list, ensuring maximum load balancing always occurs."
+msgstr "从随机目标开始，总是偏向于下一个可用目标，确保最大的负载平衡。"
#. Tag: term
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<literal>org.jboss.ha.client.loadbalance.RandomRobin</literal>"
-msgstr "<literal>org.jboss.cache.TreeCache</literal> (EJB3SFSB)"
+msgstr "<literal>org.jboss.ha.client.loadbalance.RandomRobin</literal>"
#. Tag: para
#, no-c-format
-msgid ""
-"Randomly selects its target without any consideration to previously selected "
-"targets."
-msgstr ""
+msgid "Randomly selects its target without any consideration to previously selected targets."
+msgstr "随机选取目标而不考虑之前所选的目标。"
#. Tag: term
#, no-c-format
msgid "<literal>org.jboss.ha.client.loadbalance.aop.FirstAvailable</literal>"
-msgstr ""
+msgstr "<literal>org.jboss.ha.client.loadbalance.aop.FirstAvailable</literal>"
#. Tag: para
#, no-c-format
-msgid ""
-"Once a target is chosen, always favors that same target; i.e. no further "
-"load balancing occurs. Useful in cases where \"sticky session\" behavior is "
-"desired, e.g. stateful session beans."
-msgstr ""
+msgid "Once a target is chosen, always favors that same target; i.e. no further load balancing occurs. Useful in cases where \"sticky session\" behavior is desired, e.g. stateful session beans."
+msgstr "一旦选取了目标，总是偏好相同的目标；也就是不再进行负载平衡。用于采用 \"sticky session\" 行为的时候，如 stateful session bean。"
#. Tag: term
#, no-c-format
-msgid ""
-"<literal>org.jboss.ha.client.loadbalance.aop."
-"FirstAvailableIdenticalAllProxies</literal>"
-msgstr ""
+msgid "<literal>org.jboss.ha.client.loadbalance.aop.FirstAvailableIdenticalAllProxies</literal>"
+msgstr "<literal>org.jboss.ha.client.loadbalance.aop.FirstAvailableIdenticalAllProxies</literal>"
#. Tag: para
#, no-c-format
-msgid ""
-"Similar to <literal>FirstAvailable</literal>, except that the favored target "
-"is shared across all proxies."
-msgstr ""
+msgid "Similar to <literal>FirstAvailable</literal>, except that the favored target is shared across all proxies."
+msgstr "和 <literal>FirstAvailable</literal> 类似，除了偏好的目标在各代理间共享。"
#. Tag: para
#, no-c-format
-msgid ""
-"Here is an example of a clustered EJB 3.0 stateless session bean "
-"implementation."
+msgid "Here is an example of a clustered EJB 3.0 stateless session bean implementation."
msgstr "这里是一个群集的 EJB 3.0 stateless session bean 实现的例子。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Rather than using the <literal>@Clustered</literal> annotation, you can also "
-"enable clustering for a session bean in jboss.xml:"
-msgstr ""
-"<literal>@Clustered</literal> 注解也可以忽略而使用 jboss.xml 里的群集配置："
+#, no-c-format
+msgid "Rather than using the <literal>@Clustered</literal> annotation, you can also enable clustering for a session bean in jboss.xml:"
+msgstr "<literal>@Clustered</literal> 注解也可以忽略而使用 jboss.xml 里的群集配置： "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The <literal><clustered>true</clustered></literal> element is "
-"really just an alias for the <literal><container-name>Clustered "
-"Stateless SessionBean</container-name></literal> element in the conf/"
-"standardjboss.xml file."
-msgstr ""
-"<literal><clustered>True</clustered></literal> 元素实际上是 conf/"
-"standard-jboss.xml 文件里的 <literal><configuration-name>Clustered "
-"Stateless SessionBean</configuration-name></literal> 元素。"
+#, no-c-format
+msgid "The <literal><clustered>true</clustered></literal> element is really just an alias for the <literal><container-name>Clustered Stateless SessionBean</container-name></literal> element in the conf/standardjboss.xml file."
+msgstr "<literal><clustered>true</clustered></literal> 元素实际上是 conf/standard-jboss.xml 文件里的 <literal><configuration-name>Clustered Stateless SessionBean</configuration-name></literal> 元素。 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"In the bean configuration, only the <clustered> element is necessary "
-"to indicate that the bean needs to support clustering features. The default "
-"values for the optional <cluster-config> elements match those of the "
-"corresponding properties from the <literal>@Clustered</literal> annotation."
-msgstr ""
-"在 bean 配置里，只有 <literal><clustered></literal> 元素是强制的。它指"
-"出这个 bean 在群集里运行。<literal><cluster-config></literal> 元素是可"
-"选的，我们在上面的配置样本里指出了它的缺省值。下面是关于 <literal><"
-"cluster-config></literal> 元素里属性的描述。"
+#, no-c-format
+msgid "In the bean configuration, only the <clustered> element is necessary to indicate that the bean needs to support clustering features. The default values for the optional <cluster-config> elements match those of the corresponding properties from the <literal>@Clustered</literal> annotation."
+msgstr "在 bean 配置里，只有 <clustered> 元素是强制的,它指出这个 bean 在群集里运行。<literal><cluster-config></literal> 元素的缺省值映射 <literal>@Clustered</literal> 注解里对应的属性。"
#. Tag: title
#, no-c-format
@@ -190,19 +117,9 @@
msgstr "EJB 3.0 里的 Stateful Session Bean "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Clustering stateful session beans is more complex than clustering their "
-"stateless counterparts since JBoss needs to manage the state information. "
-"The state of all stateful session beans are replicated and synchronized "
-"across the cluster each time the state of a bean changes."
-msgstr ""
-"既然 JBoss 需要管理状态信息，群集 stateful session beans 就比群集 stateles "
-"ssession beans 更为复杂。当 stateful session beans 的状态改变时，所有状态在群"
-"集中复制和同步。JBoss AS 使用 <literal>HASessionState</literal> MBean 来为群"
-"集的 EJB 2.x stateful session beans 管理分布式的会话状态。在这部分内容里，我"
-"们将介绍 session bean 的配置和 <literal>HASessionState</literal> MBean 的配"
-"置。"
+#, no-c-format
+msgid "Clustering stateful session beans is more complex than clustering their stateless counterparts since JBoss needs to manage the state information. The state of all stateful session beans are replicated and synchronized across the cluster each time the state of a bean changes."
+msgstr "既然 JBoss 需要管理状态信息，群集 stateful session beans 就比群集 stateles ssession beans 更为复杂。当 stateful session beans 的状态改变时，所有状态在群集中复制和同步。"
#. Tag: title
#, no-c-format
@@ -210,96 +127,49 @@
msgstr "EJB 应用程序配置"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"To cluster stateful session beans in EJB 3.0, you need to tag the bean "
-"implementation class with the <literal>@Clustered</literal> annotation, just "
-"as we did with the EJB 3.0 stateless session bean earlier. In contrast to "
-"stateless session beans, stateful session bean method invocations are load "
-"balanced using <literal>org.jboss.ha.client.loadbalance.aop.FirstAvailable</"
-"literal> policy, by default. Using this policy, methods invocations will "
-"stick to a randomly chosen node."
-msgstr ""
-"为了在 EJB 3.0 里群集 stateful session bean，你需要用 <literal>@Cluster</"
-"literal> 注解来标记 bean 实现类，就和我们之前对 EJB 3.0 stateless session "
-"bean 做的一样。@org.jboss.ejb3.annotation.cache.tree.CacheConfig 注解也可以用"
-"来指定缓存行为。下面是 @CacheConfig 注解的定义："
+#, no-c-format
+msgid "To cluster stateful session beans in EJB 3.0, you need to tag the bean implementation class with the <literal>@Clustered</literal> annotation, just as we did with the EJB 3.0 stateless session bean earlier. In contrast to stateless session beans, stateful session bean method invocations are load balanced using <literal>org.jboss.ha.client.loadbalance.aop.FirstAvailable</literal> policy, by default. Using this policy, methods invocations will stick to a randomly chosen node."
+msgstr "为了在 EJB 3.0 里群集 stateful session bean，你需要用 <literal>@Clustered</literal> 注解来标记 bean 实现类，就和我们之前对 EJB 3.0 stateless session bean 做的一样。和 stateless session bean 相反，在缺省情况下，stateful session bean 的方法调用使用 <literal>org.jboss.ha.client.loadbalance.aop.FirstAvailable</literal> 进行负载平衡。在这策略下，方法调用将应用随机选取的节点。"
#. Tag: para
#, no-c-format
-msgid ""
-"The <literal>@org.jboss.ejb3.annotation.CacheConfig</literal> annotation can "
-"also be applied to the bean to override the default caching behavior. Below "
-"is the definition of the <literal>@CacheConfig</literal> annotation:"
-msgstr ""
+msgid "The <literal>@org.jboss.ejb3.annotation.CacheConfig</literal> annotation can also be applied to the bean to override the default caching behavior. Below is the definition of the <literal>@CacheConfig</literal> annotation:"
+msgstr "<literal>@org.jboss.ejb3.annotation.CacheConfig</literal> 注解也可以应用到 bean 里以覆盖缺省的缓存行为。下面是 <literal>@CacheConfig</literal> 注解的定义："
#. Tag: para
#, no-c-format
-msgid ""
-"<literal>name</literal> specifies the name of a cache configuration "
-"registered with the <literal>CacheManager</literal> service discussed in "
-"<xref linkend=\"sfsb-jbc-cachemanager\" />. By default, the <literal>sfsb-"
-"cache</literal> configuration will be used."
-msgstr ""
+msgid "<literal>name</literal> specifies the name of a cache configuration registered with the <literal>CacheManager</literal> service discussed in <xref linkend=\"sfsb-jbc-cachemanager\" />. By default, the <literal>sfsb-cache</literal> configuration will be used."
+msgstr "<literal>name</literal> 指定在 <xref linkend=\"sfsb-jbc-cachemanager\" /> 讨论的 <literal>CacheManager</literal> 服务中注册的缓存配置的名称。在缺省情况下将使用 <literal>sfsb-cache</literal> 配置。"
#. Tag: para
#, no-c-format
-msgid ""
-"<literal>maxSize</literal> specifies the maximum number of beans that can "
-"cached before the cache should start passivating beans, using an LRU "
-"algorithm."
-msgstr ""
-"<literal>maxSize</literal> 指定缓存在用 LRU 算法钝化 bean 之前，可以缓存的 "
-"bean 的最大数目。"
+msgid "<literal>maxSize</literal> specifies the maximum number of beans that can cached before the cache should start passivating beans, using an LRU algorithm."
+msgstr "<literal>maxSize</literal> 指定缓存在用 LRU 算法钝化 bean 之前，可以缓存的 bean 的最大数目。"
#. Tag: para
#, no-c-format
-msgid ""
-"<literal>idleTimeoutSeconds</literal> specifies the max period of time a "
-"bean can go unused before the cache should passivate it (irregardless of "
-"whether maxSize beans are cached.)"
-msgstr ""
-"<literal>idleTimeoutSeconds</literal> 指定缓存在钝化 bean 之前（不管是否已经"
-"缓存了 maxSize 个 bean），这个 bean 可以空闲的最长时间。"
+msgid "<literal>idleTimeoutSeconds</literal> specifies the max period of time a bean can go unused before the cache should passivate it (irregardless of whether maxSize beans are cached.)"
+msgstr "<literal>idleTimeoutSeconds</literal> 指定缓存在钝化 bean 之前（不管是否已经缓存了 maxSize 个 bean），这个 bean 可以空闲的最长时间。"
#. Tag: para
#, no-c-format
-msgid ""
-"<literal>removalTimeoutSeconds</literal> specifies the max period of time a "
-"bean can go unused before the cache should remove it altogether."
-msgstr ""
-"<literal>removalTimeoutSeconds</literal> 指定缓存在删除 bean 之前，这个 bean "
-"可以空闲的最长时间。"
+msgid "<literal>removalTimeoutSeconds</literal> specifies the max period of time a bean can go unused before the cache should remove it altogether."
+msgstr "<literal>removalTimeoutSeconds</literal> 指定缓存在删除 bean 之前，这个 bean 可以空闲的最长时间。"
#. Tag: para
#, no-c-format
-msgid ""
-"<literal>replicationIsPassivation</literal> specifies whether the cache "
-"should consider a replication as being equivalent to a passivation, and "
-"invoke any @PrePassivate and @PostActivate callbacks on the bean. By default "
-"true, since replication involves serializing the bean, and preparing for and "
-"recovering from serialization is a common reason for implementing the "
-"callback methods."
-msgstr ""
-"<literal>replicationIsPassivation</literal> 指定缓存是否应该考虑复制，并调用"
-"这个 bean 的回调函数 @PrePassivate 和 @PostActivate。既然复制调用了 bean 的序"
-"列化，且准备从序列化中恢复是实现回调方法的共同原因，它缺省为 true。"
+msgid "<literal>replicationIsPassivation</literal> specifies whether the cache should consider a replication as being equivalent to a passivation, and invoke any @PrePassivate and @PostActivate callbacks on the bean. By default true, since replication involves serializing the bean, and preparing for and recovering from serialization is a common reason for implementing the callback methods."
+msgstr "<literal>replicationIsPassivation</literal> 指定缓存是否应该考虑复制，并调用这个 bean 的回调函数 @PrePassivate 和 @PostActivate。既然复制调用了 bean 的序列化，且准备从序列化中恢复是实现回调方法的共同原因，它缺省为 true。"
#. Tag: para
#, no-c-format
-msgid ""
-"Here is an example of a clustered EJB 3.0 stateful session bean "
-"implementation."
+msgid "Here is an example of a clustered EJB 3.0 stateful session bean implementation."
msgstr "这里是一个群集的 EJB 3.0 stateless session bean 实现的例子。 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"As with stateless beans, the @Clustered annotation can alternatively be "
-"omitted and the clustering configuration instead applied to jboss.xml:"
-msgstr ""
-"对于 stateless bean 来说，@Clustered 注解也可以忽略而使用 jboss.xml 里的群集"
-"配置。请参考上面的例子。"
+#, no-c-format
+msgid "As with stateless beans, the @Clustered annotation can alternatively be omitted and the clustering configuration instead applied to jboss.xml:"
+msgstr "对于 stateless bean 来说，@Clustered 注解也可以忽略而使用 jboss.xml 里的群集配置："
#. Tag: title
#, no-c-format
@@ -307,132 +177,69 @@
msgstr "优化状态复制"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"As the replication process is a costly operation, you can optimise this "
-"behaviour by optionally implementing the org.jboss.ejb3.cache.Optimized "
-"interface in your bean class:"
-msgstr ""
-"因为复制过程是很消耗资源的，为了优化这个过程，你可以选择性地在你的 bean 类里"
-"实现有下面的签名的方法："
+#, no-c-format
+msgid "As the replication process is a costly operation, you can optimise this behaviour by optionally implementing the org.jboss.ejb3.cache.Optimized interface in your bean class:"
+msgstr "因为复制过程是很消耗资源的，为了优化这个过程，你可以选择性地在你的 bean 类里实现有下面的签名的方法： "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Before replicating your bean, the container will check if your bean "
-"implements the <literal>Optimized</literal> interface. If this is the case, "
-"the container calls the <literal>isModified()</literal> method and will only "
-"replicate the bean when the method returns <literal>true</literal>. If the "
-"bean has not been modified (or not enough to require replication, depending "
-"on your own preferences), you can return <literal>false</literal> and the "
-"replication would not occur."
-msgstr ""
-"在复制你的 bean 之前，容器（container）将检测 bean 是否实现了这个方法。如果"
-"是，容器会调用 <literal>isModified()</literal> 方法并只在方法返回 "
-"<literal>true</literal> 时复制这个 bean。如果 bean 还没被更改(或者还不够来请"
-"求复制，这取决于你的喜好，你可以返回 <literal>false</literal>，这样复制就不会"
-"发生。"
+#, no-c-format
+msgid "Before replicating your bean, the container will check if your bean implements the <literal>Optimized</literal> interface. If this is the case, the container calls the <literal>isModified()</literal> method and will only replicate the bean when the method returns <literal>true</literal>. If the bean has not been modified (or not enough to require replication, depending on your own preferences), you can return <literal>false</literal> and the replication would not occur."
+msgstr "在复制你的 bean 之前，容器（container）将检测 bean 是否实现了这个方法。如果是，容器会调用 <literal>isModified()</literal> 方法并只在方法返回 <literal>true</literal> 时复制这个 bean。如果 bean 还没被更改(或者还不够来请求复制，这取决于你的喜好，你可以返回 <literal>false</literal>，这样复制就不会发生。 "
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "CacheManager service configuration"
-msgstr "HASessionState 服务配置"
+msgstr "CacheManager 服务配置"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"JBoss Cache provides the session state replication service for EJB 3.0 "
-"stateful session beans. The <literal>CacheManager</literal> service, "
-"described in <xref linkend=\"clustering-blocks-jbc-cachemanager\" /> is both "
-"a factory and registry of JBoss Cache instances. By default, stateful "
-"session beans use the <literal>sfsb-cache</literal> configuration from the "
-"<literal>CacheManager</literal>, defined as follows:"
-msgstr ""
-"JBoss Cache 为 EJB 3.0 stateful session beans 提供会话状态复制服务（session "
-"state replication service）。<literal>deploy</literal> 目录下 <literal>ejb3-"
-"clustered-sfsbcache-service.xml</literal> 文件定义了相关的 MBean 服务。文件的"
-"内容如下："
+#, no-c-format
+msgid "JBoss Cache provides the session state replication service for EJB 3.0 stateful session beans. The <literal>CacheManager</literal> service, described in <xref linkend=\"clustering-blocks-jbc-cachemanager\" /> is both a factory and registry of JBoss Cache instances. By default, stateful session beans use the <literal>sfsb-cache</literal> configuration from the <literal>CacheManager</literal>, defined as follows:"
+msgstr "JBoss Cache 为 EJB 3.0 stateful session beans 提供会话状态复制服务（session state replication service）。<xref linkend=\"clustering-blocks-jbc-cachemanager\" /> 里描述的 <literal>CacheManager</literal> 服务是 JBoss Cache 实例的工厂和注册表。在缺省情况下，stateful session bean 使用 <literal>CacheManager</literal> 里的 <literal>sfsb-cache</literal> 配置："
#. Tag: title
#, no-c-format
msgid "Eviction"
-msgstr ""
+msgstr "Eviction"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The default SFSB cache is configured to support eviction. The EJB3 SFSB "
-"container uses the JBoss Cache eviction mechanism to manage SFSB "
-"passivation. When beans are deployed, the EJB container will programatically "
-"add eviction regions to the cache, one region per bean type."
-msgstr ""
-"缓存的配置是支持逐出（Eviction）的。EJB3 SFSB 容器使用 JBoss Cache 的逐出机制"
-"来管理 SFSB 钝化。当 bean 被部署时，EJB 容器将通过程序在缓存里添加逐出 "
-"region，每个 bean 类型对应一个 region。"
+#, no-c-format
+msgid "The default SFSB cache is configured to support eviction. The EJB3 SFSB container uses the JBoss Cache eviction mechanism to manage SFSB passivation. When beans are deployed, the EJB container will programatically add eviction regions to the cache, one region per bean type."
+msgstr "缓存的配置是支持逐出（Eviction）的。EJB3 SFSB 容器使用 JBoss Cache 的逐出机制来管理 SFSB 钝化。当 bean 被部署时，EJB 容器将通过程序在缓存里添加逐出 region，每个 bean 类型对应一个 region。 "
#. Tag: title
#, no-c-format
msgid "CacheLoader"
-msgstr ""
+msgstr "CacheLoader"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"A JBoss Cache CacheLoader is also configured; again to support SFSB "
-"passivation. When beans are evicted from the cache, the cache loader "
-"passivates them to a persistent store; in this case to the filesystem in the "
-"$JBOSS_HOME/server/all/data/sfsb directory. JBoss Cache supports a variety "
-"of different CacheLoader implementations that know how to store data to "
-"different persistent store types; see the JBoss Cache documentation for "
-"details. However, if you change the CacheLoaderConfiguration, be sure that "
-"you do not use a shared store, e.g. a single schema in a shared database. "
-"Each node in the cluster must have its own persistent store, otherwise as "
-"nodes independently passivate and activate clustered beans, they will "
-"corrupt each other's data."
-msgstr ""
-"JBoss Cache 的 CacheLoader 也被配置；它也支持 SFSB 钝化。当 bean 从缓存里逐出"
-"时，缓存加载器将其钝化到持久性存储；如果使用文件系统则是 $JBOSS_HOME/server/"
-"all/data/sfsb 目录。JBoss Cache 支持懂得如何把数据存储到到不同的持久性存储类"
-"型里的不同的 CacheLoader 实现，相关细节请参考 JBoss Cache 文档。然而，如果你"
-"修改了 CacheLoader 的配置，请确保你没有使用共享的存储（如共享数据库里的单个 "
-"schema）。群集里的每个节点都必须有自己的持久性存储，否则当节点独立地钝化和激"
-"活群集 bean 时，它们将损坏其他节点的数据。"
+#, no-c-format
+msgid "A JBoss Cache CacheLoader is also configured; again to support SFSB passivation. When beans are evicted from the cache, the cache loader passivates them to a persistent store; in this case to the filesystem in the $JBOSS_HOME/server/all/data/sfsb directory. JBoss Cache supports a variety of different CacheLoader implementations that know how to store data to different persistent store types; see the JBoss Cache documentation for details. However, if you change the CacheLoaderConfiguration, be sure that you do not use a shared store, e.g. a single schema in a shared database. Each node in the cluster must have its own persistent store, otherwise as nodes independently passivate and activate clustered beans, they will corrupt each other's data."
+msgstr "JBoss Cache 的 CacheLoader 也被配置；它也支持 SFSB 钝化。当 bean 从缓存里逐出时，缓存加载器将其钝化到持久性存储；如果使用文件系统则是 $JBOSS_HOME/server/all/data/sfsb 目录。JBoss Cache 支持懂得如何把数据存储到到不同的持久性存储类型里的不同的 CacheLoader 实现，相关细节请参考 JBoss Cache 文档。然而，如果你修改了 CacheLoader 的配置，请确保你没有使用共享的存储（如共享数据库里的单个 schema）。群集里的每个节点都必须有自己的持久性存储，否则当节点独立地钝化和激活群集 bean 时，它们将损坏其他节点的数据。 "
#. Tag: title
#, no-c-format
msgid "Buddy Replication"
-msgstr ""
+msgstr "Buddy Replication"
#. Tag: para
#, no-c-format
-msgid ""
-"Using buddy replication, state is replicated to a configurable number of "
-"backup servers in the cluster (aka buddies), rather than to all servers in "
-"the cluster. To enable buddy replication, adjust the following properties in "
-"the <literal>buddyReplicationConfig</literal> property bean:"
-msgstr ""
+msgid "Using buddy replication, state is replicated to a configurable number of backup servers in the cluster (aka buddies), rather than to all servers in the cluster. To enable buddy replication, adjust the following properties in the <literal>buddyReplicationConfig</literal> property bean:"
+msgstr "使用 buddy replication，状态被复制到可配置书目的备份服务器（也就是 buddy）而不是群集中所有服务器上。要启用 buddy replication，可以调整 <literal>buddyReplicationConfig</literal> Property Bean 里的如下属性："
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Set <literal>enabled</literal> to <literal>true</literal>."
-msgstr ""
-"<literal>Principal</literal> (<literal>java.security.Principal</literal>)"
+msgstr "把 <literal>enabled</literal> 设置未 <literal>true</literal>。"
#. Tag: para
#, no-c-format
-msgid ""
-"Use the <literal>buddyPoolName</literal> to form logical subgroups of nodes "
-"within the cluster. If possible, buddies will be chosen from nodes in the "
-"same buddy pool."
-msgstr ""
+msgid "Use the <literal>buddyPoolName</literal> to form logical subgroups of nodes within the cluster. If possible, buddies will be chosen from nodes in the same buddy pool."
+msgstr "使用 <literal>buddyPoolName</literal> 来构建群集里节点的逻辑子组。如果可能，buddy 将从相同的 buddy 池里进行选取。"
#. Tag: para
#, no-c-format
-msgid ""
-"Adjust the <literal>buddyLocatorConfig.numBuddies</literal> property to "
-"reflect the number of backup nodes to which each node should replicate its "
-"state."
-msgstr ""
+msgid "Adjust the <literal>buddyLocatorConfig.numBuddies</literal> property to reflect the number of backup nodes to which each node should replicate its state."
+msgstr "调整 <literal>buddyLocatorConfig.numBuddies</literal> 属性来反映每个节点应该复制状态至备份节点的个数。"
#. Tag: title
#, no-c-format
@@ -440,51 +247,24 @@
msgstr "EJB 2.x 里的 Stateless Session Bean"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"To make an EJB 2.x bean clustered, you need to modify its <literal>jboss."
-"xml</literal> descriptor to contain a <literal><clustered></literal> "
-"tag."
-msgstr ""
-"在 EJB 应用程序里，你需要为每个 stateful session bean 修改 <literal>jboss."
-"xml</literal> 描述符文件并加入 <literal><clustered></literal> 标签。"
+#, no-c-format
+msgid "To make an EJB 2.x bean clustered, you need to modify its <literal>jboss.xml</literal> descriptor to contain a <literal><clustered></literal> tag."
+msgstr "要群集 EJB 2.x Bean，你需要为每个 stateful session bean 修改 <literal>jboss.xml</literal> 描述符文件并加入 <literal><clustered></literal> 标签。"
#. Tag: para
#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">partition-name</emphasis> specifies the name of the "
-"cluster the bean participates in. The default value is "
-"<literal>DefaultPartition</literal>. The default partition name can also be "
-"set system-wide using the <literal>jboss.partition.name</literal> system "
-"property."
-msgstr ""
-"<emphasis role=\"bold\">partition-name</emphasis> 指定 bean 所参与的群集名。"
-"它的缺省值是 <literal>DefaultPartition</literal>。缺省的分区名也可以用 "
-"<literal>jboss.partition.name</literal> 系统属性跨系统地被指定。"
+msgid "<emphasis role=\"bold\">partition-name</emphasis> specifies the name of the cluster the bean participates in. The default value is <literal>DefaultPartition</literal>. The default partition name can also be set system-wide using the <literal>jboss.partition.name</literal> system property."
+msgstr "<emphasis role=\"bold\">partition-name</emphasis> 指定 bean 所参与的群集名。它的缺省值是 <literal>DefaultPartition</literal>。缺省的分区名也可以用 <literal>jboss.partition.name</literal> 系统属性跨系统地被指定。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">home-load-balance-policy</emphasis> indicates the "
-"class to be used by the home stub to balance calls made on the nodes of the "
-"cluster. By default, the proxy will load-balance calls in a "
-"<literal>RoundRobin</literal> fashion."
-msgstr ""
-"<emphasis role=\"bold\">bean-load-balance-policy</emphasis>指出 home stub 所"
-"使用的平衡节点上的调用的类。对于 <literal>home-load-balance-policy</literal> "
-"属性的注释也同样适用。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">home-load-balance-policy</emphasis> indicates the class to be used by the home stub to balance calls made on the nodes of the cluster. By default, the proxy will load-balance calls in a <literal>RoundRobin</literal> fashion."
+msgstr "<emphasis role=\"bold\">home-load-balance-policy</emphasis>指出 home stub 所使用的平衡节点上的调用的类。代理缺省将使用 <literal>RoundRobin</literal> 策略。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">bean-load-balance-policy</emphasis> Indicates the "
-"class to be used by the bean stub to balance calls made on the nodes of the "
-"cluster. By default, the proxy will load-balance calls in a "
-"<literal>RoundRobin</literal> fashion."
-msgstr ""
-"<emphasis role=\"bold\">bean-load-balance-policy</emphasis>指出 home stub 所"
-"使用的平衡节点上的调用的类。对于 <literal>home-load-balance-policy</literal> "
-"属性的注释也同样适用。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">bean-load-balance-policy</emphasis> Indicates the class to be used by the bean stub to balance calls made on the nodes of the cluster. By default, the proxy will load-balance calls in a <literal>RoundRobin</literal> fashion."
+msgstr "<emphasis role=\"bold\">bean-load-balance-policy</emphasis>指出 home stub 所使用的平衡节点上的调用的类。对于 <literal>home-load-balance-policy</literal> 属性的注释也同样适用。在缺省情况下，代理将使用 <literal>RoundRobin</literal> 的负载平衡策略。"
#. Tag: title
#, no-c-format
@@ -492,163 +272,69 @@
msgstr "EJB 2.x 里的 Stateful Session Bean"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Clustering stateful session beans is more complex than clustering their "
-"stateless counterparts since JBoss needs to manage the state information. "
-"The state of all stateful session beans are replicated and synchronized "
-"across the cluster each time the state of a bean changes. The JBoss "
-"Enterprise Application Platform uses the <literal>HASessionStateService</"
-"literal> bean to manage distributed session states for clustered EJB 2.x "
-"stateful session beans. In this section, we cover both the session bean "
-"configuration and the <literal>HASessionStateService</literal> bean "
-"configuration."
-msgstr ""
-"既然 JBoss 需要管理状态信息，群集 stateful session beans 就比群集 stateles "
-"ssession beans 更为复杂。当 stateful session beans 的状态改变时，所有状态在群"
-"集中复制和同步。JBoss AS 使用 <literal>HASessionState</literal> MBean 来为群"
-"集的 EJB 2.x stateful session beans 管理分布式的会话状态。在这部分内容里，我"
-"们将介绍 session bean 的配置和 <literal>HASessionState</literal> MBean 的配"
-"置。"
+#, no-c-format
+msgid "Clustering stateful session beans is more complex than clustering their stateless counterparts since JBoss needs to manage the state information. The state of all stateful session beans are replicated and synchronized across the cluster each time the state of a bean changes. The JBoss Enterprise Application Platform uses the <literal>HASessionStateService</literal> bean to manage distributed session states for clustered EJB 2.x stateful session beans. In this section, we cover both the session bean configuration and the <literal>HASessionStateService</literal> bean configuration."
+msgstr "既然 JBoss 需要管理状态信息，群集 stateful session beans 就比群集 stateles ssession beans 更为复杂。当 stateful session beans 的状态改变时，所有状态在群集中复制和同步。JBoss AS 使用 <literal>HASessionStateService</literal> MBean 来为群集的 EJB 2.x stateful session beans 管理分布式的会话状态。在这部分内容里，我们将介绍 session bean 的配置和 <literal>HASessionStateService</literal> MBean 的配置。"
#. Tag: para
#, no-c-format
-msgid ""
-"In the EJB application, you need to modify the <literal>jboss.xml</literal> "
-"descriptor file for each stateful session bean and add the <literal><"
-"clustered></literal> tag."
-msgstr ""
-"在 EJB 应用程序里，你需要为每个 stateful session bean 修改 <literal>jboss."
-"xml</literal> 描述符文件并加入 <literal><clustered></literal> 标签。"
+msgid "In the EJB application, you need to modify the <literal>jboss.xml</literal> descriptor file for each stateful session bean and add the <literal><clustered></literal> tag."
+msgstr "在 EJB 应用程序里，你需要为每个 stateful session bean 修改 <literal>jboss.xml</literal> 描述符文件并加入 <literal><clustered></literal> 标签。"
#. Tag: para
#, no-c-format
-msgid ""
-"In the bean configuration, only the <literal><clustered></literal> tag "
-"is mandatory to indicate that the bean works in a cluster. The <literal><"
-"cluster-config></literal> element is optional and its default attribute "
-"values are indicated in the sample configuration above."
-msgstr ""
-"在 bean 的配置文件里，只有 <literal><clustered></literal> 标签是强制"
-"的，它指出 bean 处在群集系统里。<literal><cluster-config></literal> 元"
-"素是可选的，我们在上面的配置文件样本里指出了它的缺省属性值。"
+msgid "In the bean configuration, only the <literal><clustered></literal> tag is mandatory to indicate that the bean works in a cluster. The <literal><cluster-config></literal> element is optional and its default attribute values are indicated in the sample configuration above."
+msgstr "在 bean 的配置文件里，只有 <literal><clustered></literal> 标签是强制的，它指出 bean 处在群集系统里。<literal><cluster-config></literal> 元素是可选的，我们在上面的配置文件样本里指出了它的缺省属性值。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The <literal><session-state-manager-jndi-name></literal> tag is used "
-"to give the JNDI name of the <literal>HASessionStateService</literal> to be "
-"used by this bean."
-msgstr ""
-"<literal><session-state-manager-jndi-name></literal> 标签用来说明这个 "
-"bean 所用的 <literal>HASessionState</literal> 服务的名字。"
+#, no-c-format
+msgid "The <literal><session-state-manager-jndi-name></literal> tag is used to give the JNDI name of the <literal>HASessionStateService</literal> to be used by this bean."
+msgstr "<literal><session-state-manager-jndi-name></literal> 标签用来说明这个 bean 所用的 <literal>HASessionStateService</literal> 服务的名字。"
#. Tag: para
#, no-c-format
-msgid ""
-"The description of the remaining tags is identical to the one for stateless "
-"session bean. Actions on the clustered stateful session bean's home "
-"interface are by default load-balanced, round-robin. Once the bean's remote "
-"stub is available to the client, calls will not be load-balanced round-robin "
-"any more and will stay \"sticky\" to the first node in the list."
-msgstr ""
-"余下的标签的描述和 stateless session bean 的描述是一样的。群集的 stateful "
-"session bean 的主接口上的动作缺省是基于 round-robin 负载平衡策略的。一旦 "
-"bean 的 remote stub 对于客户可用时，调用将不会再进行负载平衡而\"粘"
-"\"（sticky）在列表里的第一个节点上。"
+msgid "The description of the remaining tags is identical to the one for stateless session bean. Actions on the clustered stateful session bean's home interface are by default load-balanced, round-robin. Once the bean's remote stub is available to the client, calls will not be load-balanced round-robin any more and will stay \"sticky\" to the first node in the list."
+msgstr "余下的标签的描述和 stateless session bean 的描述是一样的。群集的 stateful session bean 的主接口上的动作缺省是基于 round-robin 负载平衡策略的。一旦 bean 的 remote stub 对于客户可用时，调用将不会再进行负载平衡而\"粘\"（sticky）在列表里的第一个节点上。"
#. Tag: para
#, no-c-format
-msgid ""
-"As the replication process is a costly operation, you can optimise this "
-"behaviour by optionally implementing in your bean class a method with the "
-"following signature:"
-msgstr ""
-"因为复制过程是很消耗资源的，为了优化这个过程，你可以选择性地在你的 bean 类里"
-"实现有下面的签名的方法："
+msgid "As the replication process is a costly operation, you can optimise this behaviour by optionally implementing in your bean class a method with the following signature:"
+msgstr "因为复制过程是很消耗资源的，为了优化这个过程，你可以选择性地在你的 bean 类里实现有下面的签名的方法："
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Before replicating your bean, the container will detect if your bean "
-"implements this method. If your bean does, the container calls the "
-"<literal>isModified()</literal> method and it only replicates the bean when "
-"the method returns <literal>true</literal>. If the bean has not been "
-"modified (or not enough to require replication, depending on your own "
-"preferences), you can return <literal>false</literal> and the replication "
-"would not occur. This feature is available on JBoss Enterprise Application "
-"Platform 3.0.1+ only."
-msgstr ""
-"在复制你的 bean 之前，容器（container）将检测 bean 是否实现了这个方法。如果"
-"是，容器会调用 <literal>isModified()</literal> 方法并只在方法返回 "
-"<literal>true</literal> 时复制这个 bean。如果 bean 还没被更改(或者还不够来请"
-"求复制，这取决于你的喜好，你可以返回 <literal>false</literal>，这样复制就不会"
-"发生。"
+#, no-c-format
+msgid "Before replicating your bean, the container will detect if your bean implements this method. If your bean does, the container calls the <literal>isModified()</literal> method and it only replicates the bean when the method returns <literal>true</literal>. If the bean has not been modified (or not enough to require replication, depending on your own preferences), you can return <literal>false</literal> and the replication would not occur. This feature is available on JBoss Enterprise Application Platform 3.0.1+ only."
+msgstr "在复制你的 bean 之前，容器（container）将检测 bean 是否实现了这个方法。如果是，容器会调用 <literal>isModified()</literal> 方法并只在方法返回 <literal>true</literal> 时复制这个 bean。如果 bean 还没被更改（或者还不够来请求复制，这取决于你的喜好），你可以返回 <literal>false</literal>，这样复制就不会发生。这个功能只存在于 JBoss 企业级应用程序平台 3.0.1 以上的版本里。"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The HASessionStateService configuration"
-msgstr "HASessionState 服务配置"
+msgstr "HASessionStateService 配置"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>HASessionStateService</literal> bean is defined in the "
-"<code>all/deploy/cluster/ha-legacy-jboss-beans.xml</code> file."
-msgstr ""
-"<code>all/deploy/cluster-service.xml</code> 文件定义了 "
-"<literal>HASessionState</literal> 服务 MBean。"
+#, no-c-format
+msgid "The <literal>HASessionStateService</literal> bean is defined in the <code>all/deploy/cluster/ha-legacy-jboss-beans.xml</code> file."
+msgstr "<code>all/deploy/cluster/ha-legacy-jboss-beans.xml</code> 文件定义了 <literal>HASessionStateService</literal> 服务 MBean。 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The configuration attributes in the <literal>HASessionStateService</literal> "
-"bean are listed below."
-msgstr "<literal>HASessionState</literal> MBean 里的配置属性如下所示："
+#, no-c-format
+msgid "The configuration attributes in the <literal>HASessionStateService</literal> bean are listed below."
+msgstr "<literal>HASessionState</literal> MBean 里的配置属性如下所示： "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">HAPartition</emphasis> is a required attribute to "
-"inject the HAPartition service that HA-JNDI uses for intra-cluster "
-"communication."
-msgstr ""
-"<emphasis role=\"bold\">ClusterPartition</emphasis> 是一个注入 HA-JNDI 用于群"
-"集内通信的 HAPartition 服务的必需属性。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">HAPartition</emphasis> is a required attribute to inject the HAPartition service that HA-JNDI uses for intra-cluster communication."
+msgstr "<emphasis role=\"bold\">HAPartition</emphasis> 是一个注入 HA-JNDI 用于群集内通信的 HAPartition 服务的必需属性。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">jndiName</emphasis> is an optional attribute to "
-"specify the JNDI name under which this <literal>HASessionStateService</"
-"literal> bean is bound. The default value is <literal>/HAPartition/Default</"
-"literal>."
-msgstr ""
-"<emphasis role=\"bold\">JndiName</emphasis> 是一个可选属性，它指定这个 "
-"<literal>HASessionState</literal> 服务被绑定的 JNDI 名。它的缺省值是 "
-"<literal>/HAPartition/Default</literal>。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">jndiName</emphasis> is an optional attribute to specify the JNDI name under which this <literal>HASessionStateService</literal> bean is bound. The default value is <literal>/HAPartition/Default</literal>."
+msgstr "<emphasis role=\"bold\">JndiName</emphasis> 是一个可选属性，它指定这个 <literal>HASessionState</literal> 服务被绑定的 JNDI 名。它的缺省值是 <literal>/HAPartition/Default</literal>。 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis role=\"bold\">beanCleaningDelay</emphasis> is an optional "
-"attribute to specify the number of miliseconds after which the "
-"<literal>HASessionStateService</literal> can clean a state that has not been "
-"modified. If a node, owning a bean, crashes, its brother node will take "
-"ownership of this bean. Nevertheless, the container cache of the brother "
-"node will not know about it (because it has never seen it before) and will "
-"never delete according to the cleaning settings of the bean. That is why the "
-"<literal>HASessionStateService</literal> needs to do this cleanup sometimes. "
-"The default value is <literal>30*60*1000</literal> milliseconds (i.e., 30 "
-"minutes)."
-msgstr ""
-"<emphasis role=\"bold\">BeanCleaningDelay</emphasis> 是一个可选属性，它指定了"
-"一个状态在多久没有变化后 <literal>HASessionState</literal> 服务就可以清除它，"
-"它的单位是毫秒。例如，如果拥有某一 bean 的节点崩溃了，它的兄弟节点将接管这个 "
-"bean。但是，这个兄弟节点的容器缓存并不会知道这个信息（因为之前并没有这个信"
-"息），也永远不会按照这个 bean 的清除设置来删除它。这就是为什么 "
-"<literal>HASessionState</literal> 服务需要来做这个清除工作。它的缺省值是 "
-"<literal>30*60*1000</literal> 毫秒（也就是 30 分钟）。"
+#, no-c-format
+msgid "<emphasis role=\"bold\">beanCleaningDelay</emphasis> is an optional attribute to specify the number of miliseconds after which the <literal>HASessionStateService</literal> can clean a state that has not been modified. If a node, owning a bean, crashes, its brother node will take ownership of this bean. Nevertheless, the container cache of the brother node will not know about it (because it has never seen it before) and will never delete according to the cleaning settings of the bean. That is why the <literal>HASessionStateService</literal> needs to do this cleanup sometimes. The default value is <literal>30*60*1000</literal> milliseconds (i.e., 30 minutes)."
+msgstr "<emphasis role=\"bold\">BeanCleaningDelay</emphasis> 是一个可选属性，它指定了一个状态在多久没有变化后 <literal>HASessionState</literal> 服务就可以清除它，它的单位是毫秒。例如，如果拥有某一 bean 的节点崩溃了，它的兄弟节点将接管这个 bean。但是，这个兄弟节点的容器缓存并不会知道这个信息（因为之前并没有这个信息），也永远不会按照这个 bean 的清除设置来删除它。这就是为什么 <literal>HASessionState</literal> 服务需要来做这个清除工作。它的缺省值是 <literal>30*60*1000</literal> 毫秒（也就是 30 分钟）。 "
#. Tag: title
#, no-c-format
@@ -657,34 +343,13 @@
#. Tag: para
#, no-c-format
-msgid ""
-"We have covered the HA smart client architecture in the section called "
-"“Client-side interceptor architecture”. The default HA smart proxy client "
-"can only failover as long as one node in the cluster exists. If there is a "
-"complete cluster shutdown, the proxy becomes orphaned and loses knowledge of "
-"the available nodes in the cluster. There is no way for the proxy to recover "
-"from this. The proxy needs to look up a fresh set of targets out of JNDI/"
-"HAJNDI when the nodes are restarted."
-msgstr ""
-"我们已经在“客户端拦截器架构”章节介绍了 HA 智能客户端架构。缺省的 HA 智能代理"
-"客户端只能在群集里一个节点故障时进行失效切换（failover）。如果整个群集都关闭"
-"了，代理（proxy）将失去所有群集里可用节点的信息。在这种情况下，代理没有什么办"
-"法来恢复系统。当节点重启时，需要在 JNDI/HAJNDI 之外查找一系列全新的目标。"
+msgid "We have covered the HA smart client architecture in the section called “Client-side interceptor architecture”. The default HA smart proxy client can only failover as long as one node in the cluster exists. If there is a complete cluster shutdown, the proxy becomes orphaned and loses knowledge of the available nodes in the cluster. There is no way for the proxy to recover from this. The proxy needs to look up a fresh set of targets out of JNDI/HAJNDI when the nodes are restarted."
+msgstr "我们已经在“客户端拦截器架构”章节介绍了 HA 智能客户端架构。缺省的 HA 智能代理客户端只能在群集里一个节点故障时进行失效切换（failover）。如果整个群集都关闭了，代理（proxy）将失去所有群集里可用节点的信息。在这种情况下，代理没有什么办法来恢复系统。当节点重启时，需要在 JNDI/HAJNDI 之外查找一系列全新的目标。"
#. Tag: para
#, no-c-format
-msgid ""
-"The 3.2.7+/4.0.2+ releases contain a RetryInterceptor that can be added to "
-"the proxy client side interceptor stack to allow for a transparent recovery "
-"from such a restart failure. To enable it for an EJB, setup an invoker-proxy-"
-"binding that includes the RetryInterceptor. Below is an example jboss.xml "
-"configuration."
-msgstr ""
-"3.2.7+/4.0.2+ 版本包含了 <literal>RetryInterceptor</literal>，它可以加入到代"
-"理客户端拦截器栈里，允许在这样的重启故障后进行透明恢复（transparent "
-"recovery）。为了启用这个机制，你可以设立包含 <literal>RetryInterceptor</"
-"literal> 的 <literal>invoker-proxy-binding</literal>。下面是 <literal>jboss."
-"xml</literal> 配置的一个示例。 "
+msgid "The 3.2.7+/4.0.2+ releases contain a RetryInterceptor that can be added to the proxy client side interceptor stack to allow for a transparent recovery from such a restart failure. To enable it for an EJB, setup an invoker-proxy-binding that includes the RetryInterceptor. Below is an example jboss.xml configuration."
+msgstr "3.2.7+/4.0.2+ 版本包含了 <literal>RetryInterceptor</literal>，它可以加入到代理客户端拦截器栈里，允许在这样的重启故障后进行透明恢复（transparent recovery）。为了启用这个机制，你可以设立包含 <literal>RetryInterceptor</literal> 的 <literal>invoker-proxy-binding</literal>。下面是 <literal>jboss.xml</literal> 配置的一个示例。 "
#. Tag: title
#, no-c-format
@@ -693,68 +358,23 @@
#. Tag: para
#, no-c-format
-msgid ""
-"In order to recover the HA proxy, the RetryInterceptor does a lookup in "
-"JNDI. This means that internally it creates a new InitialContext and does a "
-"JNDI lookup. But, for that lookup to succeed, the InitialContext needs to be "
-"configured properly to find your naming server. The RetryInterceptor will go "
-"through the following steps in attempting to determine the proper naming "
-"environment properties:"
-msgstr ""
-"为了恢复 HA 代理，RetryInterceptor 将查找 JNDI。这意味着它会在内部创建一个新"
-"的 InitialContext 并进行 JNDI 查找。但是，为了使查找成功，你需要正确配置 "
-"InitialContext 才能找到命名服务器。RetryInterceptor 将执行下列步骤来决定正确"
-"的命名环境属性："
+msgid "In order to recover the HA proxy, the RetryInterceptor does a lookup in JNDI. This means that internally it creates a new InitialContext and does a JNDI lookup. But, for that lookup to succeed, the InitialContext needs to be configured properly to find your naming server. The RetryInterceptor will go through the following steps in attempting to determine the proper naming environment properties:"
+msgstr "为了恢复 HA 代理，RetryInterceptor 将查找 JNDI。这意味着它会在内部创建一个新的 InitialContext 并进行 JNDI 查找。但是，为了使查找成功，你需要正确配置 InitialContext 才能找到命名服务器。RetryInterceptor 将执行下列步骤来决定正确的命名环境属性："
#. Tag: para
#, no-c-format
-msgid ""
-"It will check its own static retryEnv field. This field can be set by client "
-"code via a call to RetryInterceptor.setRetryEnv(Properties). This approach "
-"to configuration has two downsides: first, it reduces portability by "
-"introducing JBoss-specific calls to the client code; and second, since a "
-"static field is used only a single configuration per JVM is possible."
-msgstr ""
-"它将检查自己的静态 retryEnv 字段。这个字段可以通过调用 RetryInterceptor."
-"setRetryEnv(Properties) 的客户端代码来设置。这个方法有两个缺点：首先，它在代"
-"码里引入了 JBoss 专有的调用，降低了可移植性；其次，既然使用了静态字段，那么每"
-"个 JVM 都只能有一个配置。"
+msgid "It will check its own static retryEnv field. This field can be set by client code via a call to RetryInterceptor.setRetryEnv(Properties). This approach to configuration has two downsides: first, it reduces portability by introducing JBoss-specific calls to the client code; and second, since a static field is used only a single configuration per JVM is possible."
+msgstr "它将检查自己的静态 retryEnv 字段。这个字段可以通过调用 RetryInterceptor.setRetryEnv(Properties) 的客户端代码来设置。这个方法有两个缺点：首先，它在代码里引入了 JBoss 专有的调用，降低了可移植性；其次，既然使用了静态字段，那么每个 JVM 都只能有一个配置。"
#. Tag: para
#, no-c-format
-msgid ""
-"If the retryEnv field is null, it will check for any environment properties "
-"bound to a ThreadLocal by the org.jboss.naming.NamingContextFactory class. "
-"To use this class as your naming context factory, in your jndi.properties "
-"set property java.naming.factory.initial=org.jboss.naming."
-"NamingContextFactory. The advantage of this approach is use of org.jboss."
-"naming.NamingContextFactory is simply a configuration option in your jndi."
-"properties file, and thus your java code is unaffected. The downside is the "
-"naming properties are stored in a ThreadLocal and thus are only visible to "
-"the thread that originally created an InitialContext."
-msgstr ""
-"如果 retryEnv 字段为空，它将检查任何通过 org.jboss.naming."
-"NamingContextFactory 类绑定到 ThreadLocal 的环境属性。要把这个类作为命名上下"
-"文工厂使用，你要在 jndi.properties 里设置属性 java.naming.factory."
-"initial=org.jboss.naming.NamingContextFactory。这个方法的优点是对 org.jboss."
-"naming.NamingContextFactory 的使用仅需要对 jndi.properties 文件进行配置，从而"
-"不会影响到你的 Java 代码。缺点是命名属性存储在 ThreadLocal 里，因此只对于原来"
-"创建 InitialContext 的线程可见。"
+msgid "If the retryEnv field is null, it will check for any environment properties bound to a ThreadLocal by the org.jboss.naming.NamingContextFactory class. To use this class as your naming context factory, in your jndi.properties set property java.naming.factory.initial=org.jboss.naming.NamingContextFactory. The advantage of this approach is use of org.jboss.naming.NamingContextFactory is simply a configuration option in your jndi.properties file, and thus your java code is unaffected. The downside is the naming properties are stored in a ThreadLocal and thus are only visible to the thread that originally created an InitialContext."
+msgstr "如果 retryEnv 字段为空，它将检查任何通过 org.jboss.naming.NamingContextFactory 类绑定到 ThreadLocal 的环境属性。要把这个类作为命名上下文工厂使用，你要在 jndi.properties 里设置属性 java.naming.factory.initial=org.jboss.naming.NamingContextFactory。这个方法的优点是对 org.jboss.naming.NamingContextFactory 的使用仅需要对 jndi.properties 文件进行配置，从而不会影响到你的 Java 代码。缺点是命名属性存储在 ThreadLocal 里，因此只对于原来创建 InitialContext 的线程可见。"
#. Tag: para
#, no-c-format
-msgid ""
-"If neither of the above approaches yield a set of naming environment "
-"properties, a default InitialContext is used. If the attempt to contact a "
-"naming server is unsuccessful, by default the InitialContext will attempt to "
-"fall back on multicast discovery to find an HA-JNDI naming server. See the "
-"section on “ClusteredJNDI Services” for more on multicast discovery of HA-"
-"JNDI."
-msgstr ""
-"如果上述两种都没给出一系列命名环境属性，缺省的 InitialContext 将被使用。如果"
-"连接命名服务器没有成功，InitialContext 缺省将通过多点传送发现（multicast "
-"discovery）来寻找 HA-JNDI 命名服务器。关于 HA-JNDI 的多点传送发现的更多信息，"
-"请参考“群集的 JNDI 服务”章节。"
+msgid "If neither of the above approaches yield a set of naming environment properties, a default InitialContext is used. If the attempt to contact a naming server is unsuccessful, by default the InitialContext will attempt to fall back on multicast discovery to find an HA-JNDI naming server. See the section on “ClusteredJNDI Services” for more on multicast discovery of HA-JNDI."
+msgstr "如果上述两种都没给出一系列命名环境属性，缺省的 InitialContext 将被使用。如果连接命名服务器没有成功，InitialContext 缺省将通过多点传送发现（multicast discovery）来寻找 HA-JNDI 命名服务器。关于 HA-JNDI 的多点传送发现的更多信息，请参考“群集的 JNDI 服务”章节。"
#. Tag: title
#, no-c-format
@@ -763,43 +383,16 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The RetryInterceptor is useful in many use cases, but a disadvantage it has "
-"is that it will continue attempting to re-lookup the HA proxy in JNDI until "
-"it succeeds. If for some reason it cannot succeed, this process could go on "
-"forever, and thus the EJB call that triggered the RetryInterceptor will "
-"never return. For many client applications, this possibility is "
-"unacceptable. As a result, JBoss doesn't make the RetryInterceptor part of "
-"its default client interceptor stacks for clustered EJBs."
-msgstr ""
-"在很多情况下 RetryInterceptor 都很有用，但缺点是它会持续地在 JNDI 里重新查找 "
-"HA 代理直到成功。如果由于某种原因不能成功，这个过程将一直进行，因此触发 "
-"RetryInterceptor 的 EJB 调用将永远无法返回。对于多数客户端应用程序来说，这样"
-"的情形是无法被接受的。因此，JBoss 没有把 RetryInterceptor 作为其群集 EJB 的客"
-"户端连接器栈的一部分。"
+msgid "The RetryInterceptor is useful in many use cases, but a disadvantage it has is that it will continue attempting to re-lookup the HA proxy in JNDI until it succeeds. If for some reason it cannot succeed, this process could go on forever, and thus the EJB call that triggered the RetryInterceptor will never return. For many client applications, this possibility is unacceptable. As a result, JBoss doesn't make the RetryInterceptor part of its default client interceptor stacks for clustered EJBs."
+msgstr "在很多情况下 RetryInterceptor 都很有用，但缺点是它会持续地在 JNDI 里重新查找 HA 代理直到成功。如果由于某种原因不能成功，这个过程将一直进行，因此触发 RetryInterceptor 的 EJB 调用将永远无法返回。对于多数客户端应用程序来说，这样的情形是无法被接受的。因此，JBoss 没有把 RetryInterceptor 作为其群集 EJB 的客户端连接器栈的一部分。"
#. Tag: para
#, no-c-format
-msgid ""
-"In the 4.0.4.RC1 release, a new flavor of retry interceptor was introduced, "
-"the org.jboss.proxy.ejb.SingleRetryInterceptor. This version works like the "
-"RetryInterceptor, but only makes a single attempt to re-lookup the HA proxy "
-"in JNDI. If this attempt fails, the EJB call will fail just as if no retry "
-"interceptor was used. Beginning with 4.0.4.CR2, the SingleRetryInterceptor "
-"is part of the default client interceptor stacks for clustered EJBs."
-msgstr ""
-"在 4.0.4.RC1 版本里引入了新的重试拦截器：org.jboss.proxy.ejb."
-"SingleRetryInterceptor。这个版本和RetryInterceptor 类似，但在 JNDI 里对 HA 代"
-"理的重新查找只进行一次。如果这次失败了，EJB 调用就会失败，就好像没有使用重试"
-"拦截器一样。从 4.0.4.CR2 开始，SingleRetryInterceptor 已经是群集 EJB 的客户端"
-"连接器栈的一部分了。"
+msgid "In the 4.0.4.RC1 release, a new flavor of retry interceptor was introduced, the org.jboss.proxy.ejb.SingleRetryInterceptor. This version works like the RetryInterceptor, but only makes a single attempt to re-lookup the HA proxy in JNDI. If this attempt fails, the EJB call will fail just as if no retry interceptor was used. Beginning with 4.0.4.CR2, the SingleRetryInterceptor is part of the default client interceptor stacks for clustered EJBs."
+msgstr "在 4.0.4.RC1 版本里引入了新的重试拦截器：org.jboss.proxy.ejb.SingleRetryInterceptor。这个版本和RetryInterceptor 类似，但在 JNDI 里对 HA 代理的重新查找只进行一次。如果这次失败了，EJB 调用就会失败，就好像没有使用重试拦截器一样。从 4.0.4.CR2 开始，SingleRetryInterceptor 已经是群集 EJB 的客户端连接器栈的一部分了。"
#. Tag: para
#, no-c-format
-msgid ""
-"The downside of the SingleRetryInterceptor is that if the retry attempt is "
-"made during a portion of a cluster restart where no servers are available, "
-"the retry will fail and no further attempts will be made."
-msgstr ""
-"SingleRetryInterceptor 的缺点是如果重试是在群集重启的过程中进行，因为此时没有"
-"可用的服务器，这个重试将失败且不会进行再次尝试。"
+msgid "The downside of the SingleRetryInterceptor is that if the retry attempt is made during a portion of a cluster restart where no servers are available, the retry will fail and no further attempts will be made."
+msgstr "SingleRetryInterceptor 的缺点是如果重试是在群集重启的过程中进行，因为此时没有可用的服务器，这个重试将失败且不会进行再次尝试。"
+
More information about the jboss-cvs-commits
mailing list