[jboss-cvs] JBossAS SVN: r87400 - projects/docs/enterprise/4.2.6/readme/zh-CN.

[jboss-cvs-commits at lists.jboss.org]

Author: xhuang at jboss.com
Date: 2009-04-16 02:09:17 -0400 (Thu, 16 Apr 2009)
New Revision: 87400

Modified:
   projects/docs/enterprise/4.2.6/readme/zh-CN/Release_Notes_CP06.po
Log:
update

Modified: projects/docs/enterprise/4.2.6/readme/zh-CN/Release_Notes_CP06.po
===================================================================
--- projects/docs/enterprise/4.2.6/readme/zh-CN/Release_Notes_CP06.po	2009-04-16 05:22:31 UTC (rev 87399)
+++ projects/docs/enterprise/4.2.6/readme/zh-CN/Release_Notes_CP06.po	2009-04-16 06:09:17 UTC (rev 87400)
@@ -10,8 +10,8 @@
 "Project-Id-Version: Release_Notes_CP06\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2009-03-31 00:04+0000\n"
-"PO-Revision-Date: 2009-04-14 17:14+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2009-04-16 14:07+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"
@@ -783,7 +783,6 @@
 #. Tag: para
 #: Release_Notes_CP06.xml:415
 #, no-c-format
-#, fuzzy
 msgid ""
 "The <classname>HTTPClientInvoker</classname> did not support Beginner's All-"
 "purpose Symbolic Instruction Code (BASIC) authentication for proxies when "
@@ -799,7 +798,8 @@
 "request header."
 msgstr ""
 "当代理配置了系统属性 <methodname>http."
-"proxyHost</methodname> 和 <methodname>http.proxyPort</methodname>，<classname>HTTPClientInvoker</classname> 不支持"
+"proxyHost</methodname> 和 <methodname>http.proxyPort</methodname> 时，<classname>HTTPClientInvoker</classname> 不支持 Beginner's All-"
+"purpose Symbolic Instruction Code (BASIC)。这个问题之所以存在是因为 <classname>HTTPClientInvoker</classname> 不会检查这些选项的存在，所以它不会创建正常操作所必需的 <methodname>Proxy-Authorization</methodname> 请求的头部信息。为了修复这个问题，我们修改了 <classname>HTTPClientInvoker</classname>，使其检查 <methodname>http.proxyHost</methodname> 选项，如果设置了该选项，它就创建一个 <methodname>Proxy-Authorization</methodname> 请求的头部信息。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:420
@@ -822,7 +822,6 @@
 #. Tag: para
 #: Release_Notes_CP06.xml:425
 #, no-c-format
-#, fuzzy
 msgid ""
 "Within the <classname>InvokerRegistry</classname> an error existed "
 "associated with the sequencing of events and <classname>serverLocators</"
@@ -835,7 +834,12 @@
 "classname>, <classname>serverLocators</classname>, and "
 "<classname>registeredLocators</classname> are governed by "
 "<classname>serverLock</classname>."
-msgstr "<classname>InvokerRegistry</classname> 里，"
+msgstr ""
+"<classname>InvokerRegistry</classname> 里存在一个和事件序列相关的错误，<classname>serverLocators</"
+"classname> 有时将返回一个空值。要改正这个问题，<classname>InvokerRegistry</classname> 里的事件序列已经被重新排列，<classname>clientLock</"
+"classname> 控制对 <classname>transportClientFactoryClasses</classname> 和 "
+"<classname>clientLocators</classname> 的引用，而 <classname>serverLock</classname> 控制对 <classname>transportServerFactoryClasses</"
+"classname>、<classname>serverLocators</classname> 和 <classname>registeredLocators</classname> 的引用。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:430
@@ -852,6 +856,9 @@
 "<varname>VALIDATOR_PING_PERIOD</varname> within the client's configuration "
 "map has not been set."
 msgstr ""
+"当重载的 <methodname>org.jboss.remoting.Client</methodname> 方法被调用且 <varname>DEFAULT_PING_PERIOD</varname> 变量被放入传递给 <classname>ConnectionValidator</"
+"classname> 的于元数据映射时，<classname>ConnectionValidator</classname> 的客户端配置映射里的值将被忽略。通过更新 <classname>org.jboss."
+"remoting.Client.addConnectionListener</classname>，使当客户的配置映射里的 <varname>VALIDATOR_PING_PERIOD</varname> 没有设置时只传递 <varname>DEFAULT_PING_PERIOD</varname>，我们解决了这个问题。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:435
@@ -867,6 +874,12 @@
 "methodname> can. The synchronization on the <varname>lock</varname> variable "
 "has been modified to avoid this issue to enable correct operation."
 msgstr ""
+"<classname>ConnectionValidator</classname> 可能不能响应，然后 <methodname>run()</methodname> 被执行并使用 <varname>lock</varname> 变量。<methodname>run()</"
+"methodname> 方法里的方法将会超时，这样在发生网络故障时 <varname>lock</varname> 变量就会为"
+" <methodname>notifyListeners()</"
+"methodname> 所用。然而，<methodname>run()</"
+"methodname> 可能在 <methodname>notifyListeners()</"
+"methodname> 之前再次执行。对 <varname>lock</varname> 变量的同步已经被修改以避免这个问题。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:440
@@ -877,7 +890,7 @@
 "<methodname>ConnectorValidator.run()</methodname> method because further "
 "synchronization on the <varname>lock</varname> variable was necessary. This "
 "issue was fixed during the rectification of the above problem."
-msgstr ""
+msgstr "在服务器的负载很重时，<methodname>ConnectorValidator.run()</methodname> 方法里可能出现 <exceptionname>IllegalStateException</exceptionname>，因为 <varname>lock</varname> 变量需要进一步同步。在修复上一个问题时我们已经解决了这个问题。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:445
@@ -890,7 +903,7 @@
 "also applied to unmarshallers. The error has been fixed by updating the "
 "<filename>jboss-remoting.jar</filename> file to include synchronized static "
 "Maps within the <classname>MarshalFactory</classname>."
-msgstr ""
+msgstr "<classname>MarshalFactory</classname> 里有一个同步错误，它允许子系统在 EJB3 试图解开时添加 marshaller，导致用户遇到 <exceptionname>InvalidMarshallingResource</exceptionname> 异常；这也适用于 unmarshaller。通过更新 <filename>jboss-remoting.jar</filename> 文件，使其包括 <classname>MarshalFactory</classname> 里的同步静态映射，我们已经改正了这个错误。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:450