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

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Tue Mar 31 01:01:50 EDT 2009 

Author: xhuang at jboss.com
Date: 2009-03-31 01:01:50 -0400 (Tue, 31 Mar 2009)
New Revision: 86505

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-03-31 04:36:52 UTC (rev 86504)
+++ projects/docs/enterprise/4.2.6/readme/zh-CN/Release_Notes_CP06.po	2009-03-31 05:01:50 UTC (rev 86505)
@@ -1,3 +1,4 @@
+# translation of Release_Notes_CP06.po to
 # translation of Release_Notes_CP04.po to
 # translation of readme.po to
 # Language zh-CN translations for readme package.
@@ -3,12 +4,12 @@
 #
 # Automatically generated, 2008.
-# Xi HUANG <xhuang at redhat.com>, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008, 2009.
 msgid ""
 msgstr ""
-"Project-Id-Version: Release_Notes_CP04\n"
+"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: 2008-10-08 10:17+1000\n"
-"Last-Translator: \n"
+"PO-Revision-Date: 2009-03-31 14:20+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -95,7 +96,7 @@
 #: Release_Notes_CP06.xml:47
 #, no-c-format
 msgid "Component Versions"
-msgstr ""
+msgstr "组件版本"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:48
@@ -104,97 +105,97 @@
 "This section details the versions of the components which create the "
 "Enterprise Application Platform 4.3 that can be found in this Cumulative "
 "Patch release."
-msgstr ""
+msgstr "这一节详述了本 Cumulative Patch 版本里组成企业版应用程序平台的组件。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:53
 #, no-c-format
 msgid "JBoss Application Server 4.2.z"
-msgstr ""
+msgstr "JBoss 应用服务器 4.2.z"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:58
 #, no-c-format
 msgid "Hibernate Core 3.2.4.SP1.CP07"
-msgstr ""
+msgstr "Hibernate Core 3.2.4.SP1.CP07"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:63
 #, no-c-format
 msgid "Hibernate Annotations 3.2.1.GA.CP03"
-msgstr ""
+msgstr "Hibernate Annotations 3.2.1.GA.CP03"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:68
 #, no-c-format
 msgid "Hibernate Entity Manager 3.2.1.GA_CP04"
-msgstr ""
+msgstr "Hibernate Entity Manager 3.2.1.GA_CP04"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:73
 #, no-c-format
 msgid "JAF 1.2_10"
-msgstr ""
+msgstr "JAF 1.2_10"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:78
 #, no-c-format
 msgid "JBoss Cache 1.4.1.SP11"
-msgstr ""
+msgstr "JBoss Cache 1.4.1.SP11"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:83
 #, no-c-format
 msgid "JBoss JAXR 1.2.0.SP2"
-msgstr ""
+msgstr "JBoss JAXR 1.2.0.SP2"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:88
 #, no-c-format
 msgid "JBoss Remoting 2.2.2.SP11"
-msgstr ""
+msgstr "JBoss Remoting 2.2.2.SP11"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:93
 #, no-c-format
 msgid "JBoss Transactions 4.2.3.SP5.CP04"
-msgstr ""
+msgstr "JBoss Transactions 4.2.3.SP5.CP04"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:98
 #, no-c-format
 msgid "JBoss Web 2.0.0-6.CP09"
-msgstr ""
+msgstr "JBoss Web 2.0.0-6.CP09"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:103
 #, no-c-format
 msgid "JBoss Web Services 1.2.1.GA_CP04"
-msgstr ""
+msgstr "JBoss Web Services 1.2.1.GA_CP04"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:108
 #, no-c-format
 msgid "JGroups 2.4.5"
-msgstr ""
+msgstr "JGroups 2.4.5"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:113
 #, no-c-format
 msgid "JSF 1.2_10"
-msgstr ""
+msgstr "JSF 1.2_10"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:118
 #, no-c-format
 msgid "Seam 1.2.1.AP"
-msgstr ""
+msgstr "Seam 1.2.1.AP"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:123
 #, no-c-format
 msgid "Xalan 2.7.0.patch02"
-msgstr ""
+msgstr "Xalan 2.7.0.patch02"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:129
@@ -203,7 +204,7 @@
 "The Enterprise Application Platform Server has been redefined for the "
 "enterprise market to a level where direct association to a community release "
 "can no longer be drawn."
-msgstr ""
+msgstr "企业级应用程序平台服务器为企业级市场进行了优化，它不再和社区版本有直接的关联。"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:135
@@ -256,9 +257,9 @@
 
 #. Tag: title
 #: Release_Notes_CP06.xml:146
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "Upgrading from JBoss Enterprise Application Platform 4.2.0.CP05"
-msgstr "从 JBoss 企业级应用程序平台版本 4.2.0.CP03 升级"
+msgstr "从 JBoss 企业级应用程序平台版本 4.2.0.CP05 升级"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:148
@@ -268,15 +269,15 @@
 
 #. Tag: para
 #: Release_Notes_CP06.xml:149
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "Refer to <ulink url=\"https://network.jboss.com/confluence/display/JON2/"
 "Applying+JBoss+Patches\">https://network.jboss.com/confluence/display/DOC/"
 "Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch."
 msgstr ""
-"关于安装 Cumulative Patch 的说明，请参考 <ulink url=\"https://network.jboss."
-"com/confluence/display/DOC/Installing+a+Patch\">https://network.jboss.com/"
-"confluence/display/DOC/Installing+a+Patch</ulink>。 "
+"关于安装 Cumulative Patch 的说明，请参考 <ulink url=\"https://network.jboss.com/confluence/display/JON2/"
+"Applying+JBoss+Patches\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink>。 "
 
 #. Tag: title
 #: Release_Notes_CP06.xml:161
@@ -400,25 +401,20 @@
 #. Tag: ulink
 #: Release_Notes_CP06.xml:205
 #, no-c-format
-msgid ""
-"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
-msgstr ""
-"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: Release_Notes_CP06.xml:209
 #, no-c-format
-msgid ""
-"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
-msgstr ""
-"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: Release_Notes_CP06.xml:213
 #, no-c-format
 msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
-msgstr ""
-"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:220
@@ -428,13 +424,13 @@
 
 #. Tag: ulink
 #: Release_Notes_CP06.xml:225
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-"
 "CP06.zip"
 msgstr ""
 "ftp://ftp.redhat.com/pub/redhat/jbeap/4.2.0/en/source/jboss-eap-src-4.2.0-"
-"CP04.zip"
+"CP06.zip"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:234
@@ -572,7 +568,7 @@
 
 #. Tag: para
 #: Release_Notes_CP06.xml:323
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<filename>Installation Guide</filename> explains how to install and verify "
 "the installation of JBoss Enterprise Application Platform using different "
@@ -601,8 +597,7 @@
 msgid ""
 "<filename>Server Configuration Guide</filename> explains all administrative "
 "and configuration functions in detail."
-msgstr ""
-"<filename>《服务器配置指南》</filename>详细解释了所有的管理和配置功能。"
+msgstr "<filename>《服务器配置指南》</filename>详细解释了所有的管理和配置功能。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:339
@@ -650,20 +645,20 @@
 #: Release_Notes_CP06.xml:362
 #, no-c-format
 msgid "JBoss Cache"
-msgstr ""
+msgstr "JBoss Cache"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:366
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1533\">JBPAPP-1533</"
 "ulink>: The JBoss Cache component of the Enterprise Application Platform has "
 "been upgraded to version 1.4.1.SP11. A list of the included fixes is as "
 "follows:"
 msgstr ""
-"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
-"ulink>：EAP 的 JBoss Remoting 组件升级为 2.2.2.SP9。这个升级修复了大量的程序"
-"错误。 "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1533\">JBPAPP-1533</"
+"ulink>：EAP 的 JBoss Cache 组件升级为 1.4.1.SP11。下面是所修复的程序"
+"错误："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:371
@@ -676,6 +671,8 @@
 "<varname>LONGVARBINARY</varname> value, allowing the "
 "<classname>JDBCCacheLoader</classname> implementation to work correctly."
 msgstr ""
+"<classname>JDBCCacheLoader</classname> 实现不能用于 Sybase，因为它会试图设置一个空的 <varname>BLOB</varname> 字段，而 Sybase 不支持。为了改正这个错误，<filename>JDBCCacheLoader."
+"java</filename> 文件进行了升级，Sybase 驱动设置为空的 <varname>LONGVARBINARY</varname> 值，这样 <classname>JDBCCacheLoader</classname> 就可以正常工作了。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:376
@@ -692,25 +689,28 @@
 "java</filename> file has been modified so that it specifies to check for "
 "available space on the <classname>ByteArrayInputStream</classname>."
 msgstr ""
+"<classname>JDBCExtCacheLoader</classname> 不能正确处理持久性状态转移，因为在存储持久性状态时，<methodname>JDBCExtCacheLoader.storeState"
+"()</methodname> 方法将使用 <classname>MarshalledValueInputStream</classname> 而不是 <classname>ByteArrayInputStream</classname> 里的可用字节。以前这是一个问题，因为 <classname>MarshalledValueInputStream</"
+"classname> 总是返回空值，表示持久性状态未被写入。我们修改了 <filename>JDBCExtendedCacheLoader."
+"java</filename> 文件，它会检查 <classname>ByteArrayInputStream</classname> 上的可用空间，这样就可以解决这个问题。"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:386
 #, no-c-format
 msgid "JBoss Remoting"
-msgstr ""
+msgstr "JBoss Remoting"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:390
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1531\">JBPAPP-1531</"
 "ulink>: The JBoss Remoting component of the Enterprise Application Platform "
 "has been upgraded to version 2.2.2.SP11. A list of the included fixes is as "
 "follows:"
 msgstr ""
-"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
-"ulink>：EAP 的 JBoss Remoting 组件升级为 2.2.2.SP9。这个升级修复了大量的程序"
-"错误。 "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1531\">JBPAPP-1531</"
+"ulink>：EAP 的 JBoss Remoting 组件升级为 2.2.2.SP11。这个升级修复的程序错误如下："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:395
@@ -729,6 +729,10 @@
 "methodname> should not be called directly but "
 "<methodname>addConnectionListener()</methodname> should be used instead."
 msgstr ""
+"在 private 方法 <methodname>ConnectionValidator.start()</methodname> 被调用之前，用户可以调用 <methodname>ConnectionValidator.run()</methodname> 方法，导致 <varname>clientInvoker</varname> 和 <varname>timer</varname> 字段被设置为空并抛出 <exceptionname>NullPointerException</"
+"exceptionname>。在 <filename>ConnectionValidator.java</filename> 文件里，在执行 <methodname>ConnectionValidator.run()</methodname>  方法后，这些字段将被检查是否为空，如果有的话将显示 <exceptionname>IllegalStateException</exceptionname>，表示不应该直接调用"
+" <methodname>ConnectionValidator.run()</"
+"methodname> 而应该使用 <methodname>addConnectionListener()</methodname>。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:400
@@ -744,6 +748,9 @@
 "been rectified with this Remoting update, allowing remote classloading to "
 "function correctly."
 msgstr ""
+"<methodname>org.jboss.remoting.marshal."
+"MarshallerLoaderHandler.loadClassBytes()</methodname> 方法里有两个程序错误，它禁止了被隔离的 EAR 的远程类加载。第一个错误是 while 循环需要加一个跳出循环语句，第二个错误是对 <methodname>org.jboss.mx.loading.LoaderRepository.getCachedClass()</"
+"methodname> 方法的调用应该是一个对 <methodname>LoaderRepository.loadClass()</methodname> 的普通调用。这次升级解决了这两个问题，远程类加载可以正常进行了。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:405
@@ -2528,384 +2535,3 @@
 "迭代顺序进行了修改。然而，这意味着 union 子句和 union 子类里的列顺序会改变，"
 "从而对组件的性能有着轻微的影响。 "
 
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1004\">JBPAPP-1004</"
-#~ "ulink>: Previous versions of the EAP contained an incorrect "
-#~ "<property>serialVersionUID</property> number, which interfered with "
-#~ "backwards compatability. The correct <property>serialVersionUID</"
-#~ "property> number is included with this release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1004\">JBPAPP-1004</"
-#~ "ulink>：之前的 EAP 版本包含了错误的 <property>serialVersionUID</property> "
-#~ "号码，它妨碍了向后的兼容性。本版本正确的 <property>serialVersionUID</"
-#~ "property> 号码。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-972\">JBPAPP-972</"
-#~ "ulink>: JBoss Aspect-Oriented Programming (AOP) has been upgraded to "
-#~ "version 1.5.GA_CP02."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-972\">JBPAPP-972</"
-#~ "ulink>：JBoss Aspect-Oriented Programming (AOP) 已经升级到了 1.5."
-#~ "GA_CP02。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-971\">JBPAPP-971</"
-#~ "ulink>: Javassist has been upgraded to version 3.8.0.GA, fixing numerious "
-#~ "issues related to this class library."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-971\">JBPAPP-971</"
-#~ "ulink>：Javassist 已经升级为 3.8.0.GA，它修复了大量和类库相关的问题。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-944\">JBPAPP-944</"
-#~ "ulink>: <classname>ClusteredSession</classname> included logic that would "
-#~ "skip session metadata replication if the only change was the timestamp. "
-#~ "This issue was corrected by changing the default maximum interval between "
-#~ "requests. The default interval is now 60 seconds and the value is now "
-#~ "configurable. This attribute can be changed by adding an atribute to the "
-#~ "<filename>jboss-service.xml</filename> file that resembles "
-#~ "<programlisting>&lt;attribute name=\"MaxUnreplicatedInterval\"&gt;30&lt;/"
-#~ "attribute&gt;</programlisting>."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-944\">JBPAPP-944</"
-#~ "ulink>：<classname>ClusteredSession</classname> 包含了如果只有时间戳有改动"
-#~ "将跳过会话元数据复制的逻辑。通过修改请求间缺省的最大间隔可以更正这个问题。"
-#~ "缺省的间隔是 60 秒，这个值是可配置的。这个属性可以通过添加一个属性到 "
-#~ "<filename>jboss-service.xml</filename> 文件里来修改：<programlisting>&lt;"
-#~ "attribute name=\"MaxUnreplicatedInterval\"&gt;30&lt;/attribute&gt;</"
-#~ "programlisting>。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-938\">JBPAPP-938</"
-#~ "ulink>: An unchanged parent entity would incorrectly have its version "
-#~ "value incremented when part of a one to many relationship. This error has "
-#~ "been rectified with this latest CP release by correcting an issue in the "
-#~ "<filename>CollectionType.java</filename> file and adding the a new method "
-#~ "called "
-#~ "<methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection()</"
-#~ "methodname> to <filename>MergeTest.java</filename>."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-938\">JBPAPP-938</"
-#~ "ulink>：在一对多关系里，未改动的父 entity 会错误地增加它的版本号。最新的 "
-#~ "CP 版本通过 <filename>CollectionType.java</filename> 并把新的 "
-#~ "<methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection()</"
-#~ "methodname> 方法添加到 <filename>MergeTest.java</filename> 修正了这个错"
-#~ "误。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-936\">JBPAPP-936</"
-#~ "ulink>: The <methodname>AnnotationBinder.mustBeSkipped</methodname> "
-#~ "method had an incorrect hardcoded String-Reference to the <classname>org."
-#~ "hibernate.tool.instrument.javassist.FieldHandler</classname> class. This "
-#~ "error has meant that the <emphasis>junitinstrument</emphasis> test was "
-#~ "not running correctly. This issue has been fixed, with the correct "
-#~ "package location of the class being referenced with the class name "
-#~ "<classname>org.hibernate.bytecode.javassist.FieldHandler</classname> and "
-#~ "the <emphasis>junitinstrument</emphasis> test now runs successfully."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-936\">JBPAPP-936</"
-#~ "ulink>：<methodname>AnnotationBinder.mustBeSkipped</methodname> 方法有一个"
-#~ "错误的对 <classname>org.hibernate.tool.instrument.javassist.FieldHandler</"
-#~ "classname> 类的硬编码字符串引用。这个错误意味着 "
-#~ "<emphasis>junitinstrument</emphasis> 测试没有正确运行。这个问题已经被解"
-#~ "决，引用了正确的 <classname>org.hibernate.bytecode.javassist."
-#~ "FieldHandler</classname> 类的软件包位置，且 <emphasis>junitinstrument</"
-#~ "emphasis> 测试现在运行正常。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-926\">JBPAPP-926</"
-#~ "ulink>: A section in the Server Configuration Guide called "
-#~ "<emphasis>Existing Entity Commands</emphasis> specified the wrong "
-#~ "packages for some classes. This updated version of the Server "
-#~ "Configuration Guide included with this CP, contains the correct package "
-#~ "information for the classes affected."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-926\">JBPAPP-926</"
-#~ "ulink>《服务器配置指南》里称为 <emphasis>Existing Entity Commands</"
-#~ "emphasis> 的部分为某些类指定了错的软件包。本 CP 版本包含了更新的《服务器配"
-#~ "置指南》，更正了相关的软件包信息。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-915\">JBPAPP-915</"
-#~ "ulink>: A merge operation would fail when there was a transient entity "
-#~ "that was reachable by multiple paths and at least one of these paths did "
-#~ "not cascade when undertaking a merge. This issue is fixed with the EAP "
-#~ "4.3 now supporting JDK 6."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-915\">JBPAPP-915</"
-#~ "ulink>：当多个路径可以访问临时的条目，且在执行合并时，如果这些路径里至少有"
-#~ "一个没有层叠合并，那么操作会不成功:。这个问题在支持 JDK 6 的 EAP 4.3 里得"
-#~ "到了解决。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-908\">JBPAPP-908</"
-#~ "ulink>: Hibernate proxy serialization was broken because the "
-#~ "<classname>AbstractLazyInitializer</classname> class was not "
-#~ "Serializable. This is now corrected within this CP release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-908\">JBPAPP-908</"
-#~ "ulink>：因为 <classname>AbstractLazyInitializer</classname> 类不是可串行化"
-#~ "的，Hibernate proxy 串行化失败。本 CP 版本里已经修正了这个问题。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-907\">JBPAPP-907</"
-#~ "ulink>: There was an issue where a deserialization bottleneck would occur "
-#~ "in arrays for JDK 1.6. In order to rectify this issue, the following has "
-#~ "been added to the <filename>run.conf</filename> file: <programlisting>-"
-#~ "Dsun.lang.ClassLoader.allowArraySyntax=true</programlisting>."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-907\">JBPAPP-907</"
-#~ "ulink>：JDK 1.6 的数组会发生反序列化（deserialization）的瓶颈问题。为了修"
-#~ "正这个问题，下面的参数添加到了 <filename>run.conf</filename> 文件里："
-#~ "<programlisting>-Dsun.lang.ClassLoader.allowArraySyntax=true</"
-#~ "programlisting>。"
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-899\">JBPAPP-899</"
-#~ "ulink>: There was an error within the entity manager where the methods "
-#~ "<methodname>getSingleResult()</methodname> and <methodname>fetch()</"
-#~ "methodname> would return a <code>NonUniqueResultException</code> because "
-#~ "elements were now unique. This issue has been corrected with this CP "
-#~ "release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-899\">JBPAPP-899</"
-#~ "ulink>：当 <methodname>getSingleResult()</methodname> 和 <methodname>fetch"
-#~ "()</methodname> 方法返回 <code>NonUniqueResultException</code> 时，entity "
-#~ "manager 会出现问题，这是因为现在元素都是唯一的。本 CP 版本已经解决了这个问"
-#~ "题。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-897\">JBPAPP-897</"
-#~ "ulink>: JBoss Transaction Services has been upgraded to version 4.2.3 SP5 "
-#~ "CP02."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-897\">JBPAPP-897</"
-#~ "ulink>：JBoss Transaction Services 已经升级为 4.2.3 SP5 CP02。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-895\">JBPAPP-895</"
-#~ "ulink>: The Java Messaging Service (JMS) connections needed to be "
-#~ "consistently closed in reference to the J2EE Connector Architecture "
-#~ "(JCA). These connections are now always closed to restrict exceptions."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-895\">JBPAPP-895</"
-#~ "ulink>：Java 消息服务（JMS）连接需要按照 J2EE Connector Architecture "
-#~ "(JCA) 一致地进行关闭。现在这些连接可以被关闭了。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-891\">JBPAPP-891</"
-#~ "ulink>: The monitoring tool <emphasis>Twiddle</emphasis> did not print "
-#~ "out <code>invoke</code> results, even with the absense of a property "
-#~ "editor for the returned object. Corrected within this CP release, "
-#~ "<emphasis>Twiddle</emphasis> now calls the <methodname>toString()</"
-#~ "methodname> method on returned objects when there is no property editor "
-#~ "found."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-891\">JBPAPP-891</"
-#~ "ulink>：监控工具 <emphasis>Twiddle</emphasis> 没有输出 <code>invoke</"
-#~ "code> 结果，甚至在没有用于返回对象的属性编辑器时也是这样。本 CP 发行版本修"
-#~ "复了这个问题，当没有找到属性编辑器时，<emphasis>Twiddle</emphasis> 现在调"
-#~ "用返回对象的 <methodname>toString()</methodname> 方法。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-887\">JBPAPP-887</"
-#~ "ulink>: JBoss Java API for XML Redistries (JAXR) has been upgraded to "
-#~ "version 1.2.0.SP1 which addresses various bugs."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-887\">JBPAPP-887</"
-#~ "ulink>：用于 XML Redistries (JAXR) 的 JBoss Java API 已经升级为 1.2.0."
-#~ "SP1，它修复了不同的程序错误。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-877\">JBPAPP-877</"
-#~ "ulink>: JBoss Serialization version 1.0.3GA would encounter "
-#~ "<code>ClassCastExceptions</code> when being used. This update corrects "
-#~ "this issue so that serialization functions correctly."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-877\">JBPAPP-877</"
-#~ "ulink>：JBoss Serialization 版本 1.0.3GA 在使用时会遇到 "
-#~ "<code>ClassCastExceptions</code>。本版本已经修复了这个问题，序列化已经正常"
-#~ "了。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-867\">JBPAPP-867</"
-#~ "ulink>: An <interfacename>ExceptionSorter</interfacename> interface "
-#~ "implementation should be provided for users of the IBM DB2 Data Server. "
-#~ "This enhancement to the EAP is included within this CP release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-867\">JBPAPP-867</"
-#~ "ulink>：<interfacename>ExceptionSorter</interfacename> 接口实现应该提供给 "
-#~ "IBM DB2 Data Server 的用户。本 CP 版本里包含了这个实现。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-864\">JBPAPP-864</"
-#~ "ulink>: Clustered proxy factories did not bind home proxies. This issue "
-#~ "has been rectified by now supporting clustered home proxies for EJB3 "
-#~ "beans. However, in order to avoid backwards compatibility issues, the "
-#~ "load balance policy for home proxies has been hard coded to round robin. "
-#~ "This is also the default policy for EJB2 home proxies."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-864\">JBPAPP-864</"
-#~ "ulink>：群集的代理工厂没有绑定 home proxy。这个问题已经被解决，现在支持用"
-#~ "于 EJB3 bean 的群集 home proxy。然而，为了避免向后兼容的问题，home proxy "
-#~ "的负载平衡策略已经改为 round robin。这也是 EJB2 home proxy 的缺省策略。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-859\">JBPAPP-859</"
-#~ "ulink>: The <classname>SchemaUpdate</classname> class has been enhanced "
-#~ "with <option>output file name</option>, <option>delimiter</option>, "
-#~ "<option>halt on error</option>, <option>format</option> options now "
-#~ "avaliable."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-859\">JBPAPP-859</"
-#~ "ulink>：<classname>SchemaUpdate</classname> 类的功能进行了增强，现在可以使"
-#~ "用 <option>output file name</option>、<option>delimiter</option>、"
-#~ "<option>halt on error</option>、<option>format</option> 属性了。 "
-
-#~ msgid ""
-#~ "It is important to note that a regular jbossas installation is required "
-#~ "on the server first before installtion of the -bin. The -bin is for an "
-#~ "additional installation only and cannot be used in place of a regular RPM "
-#~ "jbossas installation. If you only have one version of the AS, it will "
-#~ "have to be the regular RPM installation (or ZIP or installer for older "
-#~ "versions)."
-#~ msgstr ""
-#~ "请注意，安装 -bn 文件之前首先必须进行常规的 jbossas 安装。-bin 方式仅用>于"
-#~ "额外的安装，它不能代替常规的 PRM 安装。如果你只有一个 AS 版本，那就必须使"
-#~ "用常>规的 PRM 安装（也可以是 ZIP 文件方式或旧版本的安装程序）。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-844\">JBPAPP-844</"
-#~ "ulink>: The MSSQL data source example was incompatible with SQL Server "
-#~ "2005. To fix this compatability issue, the <code>driver-class</code> has "
-#~ "been updated from <code>com.microsoft.jdbc.sqlserver.SQLServerDriver</"
-#~ "code> to <code>com.microsoft.sqlserver.jdbc.SQLServerDriver</code> and "
-#~ "the default port for the <code>connection-url</code> has been changed "
-#~ "from 1433 to 3918. With these changes the example now functions correctly "
-#~ "under SQL Server 2005."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-844\">JBPAPP-844</"
-#~ "ulink>：MSSQL 数据源示例和 SQL Server 2005 不兼容。要修复这个兼容性问题，"
-#~ "<code>driver-class</code> 已经从 <code>com.microsoft.jdbc.sqlserver."
-#~ "SQLServerDriver</code> 升级到了 <code>com.microsoft.sqlserver.jdbc."
-#~ "SQLServerDriver</code>，且 <code>connection-url</code> 的缺省端口已经从 "
-#~ "1433 变到了 3918。经过这些修改，例程现在已经可以在 SQL Server 2005 下正常"
-#~ "运行了。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-857\">JBPAPP-857</"
-#~ "ulink>: The .rar file <filename>mail-ra.rar</filename> used within the "
-#~ "application server to recieve email from using the JavaMail API, was "
-#~ "missing from the distribution. This missing file has now been re-included."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-857\">JBPAPP-857</"
-#~ "ulink>：发行版本里漏掉了应用服务器里使用 JavaMail API 邮件的 .rar 文件 "
-#~ "<filename>mail-ra.rar</filename>。本版本包含了这个文件。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-815\">JBPAPP-815</"
-#~ "ulink>: An issue existed where if a DOCTYPE was added to the file "
-#~ "<filename>-ds.xml</filename> and the option to <option>ValidateDTDs</"
-#~ "option> was set to true in <filename>jbossjca-services.xml</filename>, "
-#~ "validation errors would occur. This was found to be because of an issue "
-#~ "with the <property>tx-connection-factory</property> element in "
-#~ "<filename>jms-ds.xml</filename> which has since been fixed."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-815\">JBPAPP-815</"
-#~ "ulink>：如果把 DOCTYPE 添加到文件 <filename>-ds.xml</filename> 且把 "
-#~ "<filename>jbossjca-services.xml</filename> 里的选项 <option>ValidateDTDs</"
-#~ "option> 设置为 true，将发生校验错误。这是因为 <filename>jms-ds.xml</"
-#~ "filename> 里的 <property>tx-connection-factory</property> 元素里的一个问题"
-#~ "引起的，它现在已经被修复。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-813\">JBPAPP-813</"
-#~ "ulink>: The Messaging client included a bug that would make it hang "
-#~ "forever, creating a <code>ClusteredConnectionFactory</code> failover; "
-#~ "steaming from a socket hang. This issue has now been rectified in this "
-#~ "latest EAP release, creating a more stable Messaging component."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-813\">JBPAPP-813</"
-#~ "ulink>：消息客户端的一个程序错误会由于套接字挂起使其无限期挂起并产生 "
-#~ "<code>ClusteredConnectionFactory</code> 失效切换。最新的 EAP 版本已经桥正"
-#~ "了这个问题，它创建了一个新的消息组件。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-805\">JBPAPP-805</"
-#~ "ulink>: There was a missing java file from the first security example "
-#~ "within the server configuration guide, inhibiting the example to be run "
-#~ "successfully. The missing <filename>EchoSecurityProxy.java</filename> "
-#~ "file has now been restored, enabling the example to be run correctly."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-805\">JBPAPP-805</"
-#~ "ulink>：《服务器配置指南》里的第一个安全例程漏掉了一个 java 文件，这阻止了"
-#~ "例程的正确运行。现在，这个 <filename>EchoSecurityProxy.java</filename> 文"
-#~ "件已经恢复，例程也可以正常运行了。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-799\">JBPAPP-799</"
-#~ "ulink>: the seamejb3 example would generate a <code>FaceletException</"
-#~ "code> error. This issue was caused from the inclusion of incorrect .jar "
-#~ "files for the example. This CP update includes the correct .jar files, "
-#~ "correcting the issue and allowing the example to execute correctly."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-799\">JBPAPP-799</"
-#~ "ulink>：seamejb3 例程会产生一个 <code>FaceletException</code> 错误。这个问"
-#~ "题是因为包含了错误的 .jar 文件。本 CP 版本包含了正确的 .jar 文件，使例程可"
-#~ "以正常运行。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-782\">JBPAPP-782</"
-#~ "ulink>: The <classname>MapBinder</classname> class had the ability to "
-#~ "generate SQL statements that would not be supported by the Oracle 10g "
-#~ "database. This was of particular concern for some EJB3 Persistence users "
-#~ "on EAP and Oracle. This issue has now been rectified in this CP release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-782\">JBPAPP-782</"
-#~ "ulink>：<classname>MapBinder</classname> 类具有生成 Oracle 10g 不支持的 "
-#~ "SQL 语句的能力。某些使用 EAP 的 EJB3 持久性和 Oracle 的用户来说尤其关系这"
-#~ "一点。本 CP 版本已经修正了这个问题。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-755\">JBPAPP-755</"
-#~ "ulink>: The Seam source readme.txt file required updated links to "
-#~ "seamframework.org and mention the EAP instead of the JBoss AS. This file "
-#~ "has been updated with the above changes for this release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-755\">JBPAPP-755</"
-#~ "ulink>：Seam 的 readme.txt 文件需要更新到 seamframework.org 的链接并提及 "
-#~ "EAP 而不是 JBoss AS。本版本已经更新了该文件。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-746\">JBPAPP-746</"
-#~ "ulink>: There was a bug within the JavaServer Pages (JSP) compiler "
-#~ "affecting Tomcat where the body of the doTag() method was empty. This "
-#~ "meant that no html would be emitted. This fix for this Tomcat related "
-#~ "issue has been included within this CP release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-746\">JBPAPP-746</"
-#~ "ulink>：JavaServer Pages (JSP) 编译器里的一个程序错误在 doTag() 方法为空时"
-#~ "会影响到 Tomcat。这表示不会输出 html。本 CP 发行版本里已经修复了相关的错"
-#~ "误。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-729\">JBPAPP-729</"
-#~ "ulink>: A wrong character set was being used for the decoding of URL "
-#~ "parameters after a servlet redirect had occurred. Now fixed within this "
-#~ "CP, URLs are decoded correctly after servelt redirects."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-729\">JBPAPP-729</"
-#~ "ulink>：当 servlet 重定向发生时，URL 参数的解码使用了错误的字符集。本 CP "
-#~ "版本修改了这个错误。 "
-
-#~ msgid ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-295\">JBPAPP-295</"
-#~ "ulink>: The replicated Stateful Session Bean (SFSB) required optimization "
-#~ "for use with Buddy Replication. After extensive testing and fixes, the "
-#~ "optimization required is now included within this CP release."
-#~ msgstr ""
-#~ "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-295\">JBPAPP-295</"
-#~ "ulink>：和 Buddy Replication 一起使用的 Replicated Stateful Session Bean "
-#~ "(SFSB) 需要进行优化。经过广泛的测试并修复，本 CP 发行版本里已经包含相关的"
-#~ "优化。"

More information about the jboss-cvs-commits mailing list