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

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Mon Apr 6 00:34:54 EDT 2009 

Author: xhuang at jboss.com
Date: 2009-04-06 00:34:54 -0400 (Mon, 06 Apr 2009)
New Revision: 86829

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-06 03:00:59 UTC (rev 86828)
+++ projects/docs/enterprise/4.2.6/readme/zh-CN/Release_Notes_CP06.po	2009-04-06 04:34:54 UTC (rev 86829)
@@ -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-03-31 14:20+1000\n"
-"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"PO-Revision-Date: 2009-04-06 14:34+1000\n"
+"Last-Translator: Xi HUANG\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -761,7 +761,7 @@
 "classloading was enabled, leading to conflicts if the class was available "
 "locally before. The code has been corrected to check locally first before "
 "looking remotely."
-msgstr ""
+msgstr "Remoting 组件如果启用了远程类加载，RemotingClassLoader 总是首先通过网络加载类，如果本地也有这个类就会导致冲突。我们已经修复了代码，使其在远程查找前首先在本地进行检查。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:410
@@ -777,10 +777,13 @@
 "issue the call to the <methodname>BlockingCallbackStore.add()</methodname> "
 "method has been removed as it was an unnecessary step."
 msgstr ""
+"在锁定带有 <methodname>persistCallback()</methodname> 方法响应的 callback 字段后调用 <methodname>BlockingCallbackStore.add()</"
+"methodname> 方法时，<classname>ServerInvokerCallbackHandler</classname> 类会处于不响应状态。这是因为<methodname>BlockingCallbackStore.getNext()</methodname> 需要控制 callback 字段的锁，但由于等待时间而无法实现。要修复这个问题，对 <methodname>BlockingCallbackStore.add()</methodname> 方法的调用已经被删除，因为它不是必需的步骤。"
 
 #. 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 "
@@ -794,7 +797,7 @@
 "existence of the <methodname>http.proxyHost</methodname> option and if it "
 "detects its use, creates a <methodname>Proxy-Authorization</methodname> "
 "request header."
-msgstr ""
+msgstr "<classname>HTTPClientInvoker</classname> 不支持"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:420
@@ -941,16 +944,16 @@
 
 #. Tag: para
 #: Release_Notes_CP06.xml:474
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1334\">JBPAPP-1334</"
 "ulink>: The JBoss Web component of the Enterprise Application Platform has "
 "been upgraded to version 2.0.0-6.CP09. 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-1334\">JBPAPP-1334</"
+"ulink>：EAP 的 JBoss Web 组件升级为 2.0.0-6.CP09。这个升级修复了的程序"
+"错误如下： "
 
 #. Tag: para
 #: Release_Notes_CP06.xml:479
@@ -965,25 +968,28 @@
 "<filename>WebAppClassLoader.java</filename> has been updated to ensure the "
 "correct parser is used."
 msgstr ""
+"如果某个 WAR 部署在 <filename>WEB-INF/lib</"
+"filename> 里包含了自己的 <filename>xalan.jar</"
+"filename> 和 <filename>xercesImpl.jar</filename>，JBossWeb servlet 容器类加载器从 <methodname>SAXParserFactory.newInstance().newSAXParser()</methodname> 返回 JBoss 所提供的 <literal>SAXParser</literal> 而不是该 WAR 部署带有的版本。为了修复这个错误，我们更新了 <filename>WebAppClassLoader.java</filename>。"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:489
 #, no-c-format
 msgid "JBoss Web Services"
-msgstr ""
+msgstr "JBoss Web Services"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:493
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-734\">JBPAPP-734</"
 "ulink>: The JBoss Web Services component of the Enterprise Application "
 "Platform has been upgraded to version 1.2.1.GA_CP04. 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-734\">JBPAPP-734</"
+"ulink>：EAP 的 JBoss Web Services  组件升级为 1.2.1.GA_CP04。这个升级修复的程序"
+"错误如下： "
 
 #. Tag: para
 #: Release_Notes_CP06.xml:498
@@ -1010,12 +1016,14 @@
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1565\">JBPAPP-1565</"
 "ulink>, discussed in the Security Issue section."
 msgstr ""
+"如安全性问题部分所讨论的，JBoss Web Services 的 1.2.1.GA_CP04 版本也包括了安全性修复 <ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1565\">JBPAPP-1565</"
+"ulink>。"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:513
 #, no-c-format
 msgid "JBoss Seam"
-msgstr ""
+msgstr "JBoss Seam"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:517
@@ -1058,20 +1066,20 @@
 #: Release_Notes_CP06.xml:535
 #, no-c-format
 msgid "JBoss Hibernate"
-msgstr ""
+msgstr "JBoss Hibernate"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:539
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1580\">JBPAPP-1580</"
 "ulink>: The JBoss Hibernate Core component of the Enterprise Application "
 "Platform has been upgraded to version 3.2.4.SP1.CP07. 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-1580\">JBPAPP-1580</"
+"ulink>：EAP 的 JBoss Hibernate Core 组件升级为 3.2.4.SP1.CP07。这个升级修复的程序"
+"错误如下： "
 
 #. Tag: para
 #: Release_Notes_CP06.xml:544
@@ -1488,16 +1496,16 @@
 
 #. Tag: para
 #: Release_Notes_CP06.xml:760
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1670\">JBPAPP-1670</"
 "ulink>: The JacORB component of the Enterprise Application Platform has been "
 "upgraded to version 2.3.0jboss.patch6-brew. 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-1670\">JBPAPP-1670</"
+"ulink>：EAP 的 JacORB 组件升级为 2.3.0jboss.patch6-brew。这个升级修复的程序"
+"错误如下："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:765
@@ -1513,19 +1521,19 @@
 #: Release_Notes_CP06.xml:768
 #, no-c-format
 msgid "throw new org.omg.CORBA.OBJECT_NOT_EXIST();"
-msgstr ""
+msgstr "throw new org.omg.CORBA.OBJECT_NOT_EXIST();"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:769
 #, no-c-format
 msgid "the following is now executed:"
-msgstr ""
+msgstr "下面的语句将被执行："
 
 #. Tag: programlisting
 #: Release_Notes_CP06.xml:772
 #, no-c-format
 msgid "throw new ObjectNotActive();"
-msgstr ""
+msgstr "throw new ObjectNotActive();"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:777
@@ -1550,7 +1558,7 @@
 msgid ""
 "This bug only affected third party adapters running within the JBoss "
 "Application Server."
-msgstr ""
+msgstr "这个程序错误只影响在 JBoss 应用服务器内部运行的第三方适配器。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:787
@@ -1562,6 +1570,8 @@
 "(connection closed) now able to be handled. These enhancements have been "
 "applied to the <filename>OracleExceptionSorter.java</filename> file."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1635\">JBPAPP-1635</"
+"ulink>：本版本加强了 <classname>OracleExceptionSorter</classname>，添加了对错误代码 17002（连接重置）和 17008（连接关闭）的处理。<filename>OracleExceptionSorter.java</filename> 文件里应用了这些改进。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:792
@@ -1621,6 +1631,8 @@
 "Proble Client now uses 224.0.75.75 instead of 224.0.0.75 which allows the "
 "client and the listener to work together correctly."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1538\">JBPAPP-1538</"
+"ulink>：Probe Client 没有象 Probe Listener 一样更新，它应该使用相同的地址 224.0.75.75。现在已经将其从 224.0.0.75 改为了 224.0.75.75，这使得 Client 和 Listener 可以一起正常运行。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:812
@@ -1635,6 +1647,8 @@
 "updated to store the new state using the <varname>in_stream</varname> value "
 "as long as there is space available."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1535\">JBPAPP-1535</"
+"ulink>：JDBCExtCacheLoader 没有正确处理持久性状态转移，因为 <methodname>storeState</methodname> 方法将使用<classname>MarshalledValueInputStream</classname> 而不是 <classname>ByteArrayInputStream</classname> 上的可用空间。为了改正 stream 的用法，我们更新了 <filename>JDBCExtendedCacheLoader.java</filename>，只要有可用的空间，就让它用 <varname>in_stream</varname> 值存储新的状态。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:817
@@ -1649,19 +1663,21 @@
 "that null values are set as <varname>LONGVARBINARY</varname> rather than "
 "<varname>BLOB</varname>."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1534\">JBPAPP-1534</"
+"ulink>：和 Sybase 一起使用时，JDBCCacheLoader 不能设置 Sybase 所不支持的空的 <varname>BLOB</varname> (Binary Large OBject) 字段。为了改正这个问题，我们更新了 <filename>JDBCCacheLoader.java</"
+"filename> 和 <filename>AdjListJDBCCacheLoader.java</filename> 文件，在使用 Sybase 时选择 Sybase 驱动，这样就可以确保空值可以设置为 <varname>LONGVARBINARY</varname> 而非 <varname>BLOB</varname>。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:822
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1532\">JBPAPP-1532</"
 "ulink>: The JGroups clustering component of the Enterprise Application "
 "Platform has been upgraded to version 2.4.5. 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-1532\">JBPAPP-1532</"
+"ulink>：EAP 的 JGroups 组件升级为  2.4.5。这个升级修复了下面的错误："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:827
@@ -1845,16 +1861,15 @@
 
 #. Tag: para
 #: Release_Notes_CP06.xml:897
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1289\">JBPAPP-1289</"
 "ulink>: The JBoss JAXR component of the Enterprise Application Platform has "
 "been upgraded to version 1.2.0.SP2. 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-1289\">JBPAPP-1289</"
+"ulink>：EAP 的 JBoss JAXR 组件升级为 1.2.0.SP2。下面是所修复的错误列表："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:902
@@ -1867,6 +1882,9 @@
 "stack. The namespace value should instead be null and this has been applied "
 "for this JAXR update."
 msgstr ""
+"在 <filename>org.jboss.jaxr.juddi.JUDDIServlet</filename> 和 "
+"<filename>org.jboss.jaxr.juddi.transport.SaajTransport</filename> 文件里，<varname>xml:lang</varname> 的命名空间值包括 <literal>http://"
+"www.w3.org/TR/REC-xml/</literal>，这会导致内存栈的异常。命名空间值应该为空且已应用在本 JAXR 版本里。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:909
@@ -1878,6 +1896,8 @@
 "circumstance where an application which heavily used Xalan within large "
 "multi-threaded environments would encounter blocking situations."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1275\">JBPAPP-1275</"
+"ulink>：EAP 的 Xalan 部分已经从 2.7.0 升级到 2.7.0.patch02。这次升级解决了在多线程环境里频繁使用 Xalan 时遇到的阻塞问题。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:914
@@ -1890,18 +1910,19 @@
 "<classname>UserTransaction</classname> deployable with transaction sticky "
 "load balance policies."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1267\">JBPAPP-1267</"
+"ulink>：<classname>UserTransaction</classname> (UT) 不能够用支持 Sticky 事务的群集代理进行部署。通过修改大量的文件，使 <classname>UserTransaction</classname> 可和事务的 Sticky 负载平衡策略一起部署。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:919
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1249\">JBPAPP-1249</"
 "ulink>: The JSF component of the Enterprise Application Platform has been "
 "upgraded to version 1.2_10. 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-1249\">JBPAPP-1249</"
+"ulink>：EAP 的 JSF 组件升级为 1.2_10。下面是已修复问题的列表："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:924
@@ -1912,6 +1933,9 @@
 "updated with the removal of <code>ELUtils.getScope(this.expressionString, "
 "segment);</code> in order to fix this issue."
 msgstr ""
+"以字符结尾的混合 EL 表达式不能解析为 managed "
+"bean 属性的值。我们删除了 <filename>BeanBuilder.java</filename> 文件里的 <code>ELUtils.getScope(this.expressionString, "
+"segment);</code> 来修复这个问题。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:929
@@ -1958,7 +1982,7 @@
 "correctly. To correct the issue so that no information is hidden from the "
 "user, the <exceptionname>ManagedBeanCreationException</exceptionname> has "
 "been updated to provide more information about the cause of the exception."
-msgstr ""
+msgstr "用户无法获知 <classname>BeanBuilder</classname> 里抛出 <classname>PostConstruct</classname> 异常的原因。为了改正这个问题，不对用户隐藏任何信息，我么更新了 <exceptionname>ManagedBeanCreationException</exceptionname> 以提供导致这个异常的更多信息。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:949
@@ -2178,14 +2202,14 @@
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1026
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-996\">JBPAPP-996</"
 "ulink>: Discrepancies existed between the port schemes within the "
 "<filename>sample-bindings.xml</filename> file. These include:"
 msgstr ""
-"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-961\">JBPAPP-961</"
-"ulink>：JBoss Web 已经升级为 2.0.0.GA CP06。 "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-996\">JBPAPP-996</"
+"ulink>：<filename>sample-bindings.xml</filename> 文件里的端口模式存在差异。它们包括："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1031
@@ -2194,7 +2218,7 @@
 "The remoting connectors were inserted in different places within the ports "
 "definition sections, making the comparison of the sections more difficult "
 "than was necessary."
-msgstr ""
+msgstr "远程连接器被插入到端口定义部分的不同地方，使得更难比较这些部分。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1036
@@ -2204,6 +2228,8 @@
 "remoting connector</literal> and the <literal>remoting connector</literal> "
 "sections."
 msgstr ""
+"<literal>ports-03</literal> 部分漏掉了 <literal>EJB "
+"remoting connector</literal> 和 <literal>remoting connector</literal> 部分。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1041
@@ -2211,7 +2237,7 @@
 msgid ""
 "<literal>mq</literal> was used in the name property of the "
 "<varname>HAJNDIJMSProvider</varname> instead of <literal>jms</literal>."
-msgstr ""
+msgstr "<literal>mq</literal> 而不是 <literal>jms</literal> 用在 <varname>HAJNDIJMSProvider</varname> 的 name 属性里。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1046
@@ -2220,13 +2246,13 @@
 "The <literal>ports-01</literal>, <literal>ports-02</literal>, and "
 "<literal>ports-03</literal> schemes defined the <varname>timeout</varname> "
 "attribute twice in the <literal>JBoss Messaging</literal> section:"
-msgstr ""
+msgstr "<literal>ports-01</literal>、<literal>ports-02</literal> 和 <literal>ports-03</literal> 模式两次定义了 <literal>JBoss Messaging</literal> 部分里的 <varname>timeout</varname> 属性："
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1052
 #, no-c-format
 msgid "The above issues have been fixed appropriately in this update."
-msgstr ""
+msgstr "本更新版本里已经修复上面的问题。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1057
@@ -2238,6 +2264,9 @@
 "Platform now uses <filename>beanutils 1.8.0</filename> which fixes this "
 "<errorname>OutOfMemoryError</errorname>."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-713\">JBPAPP-713</"
+"ulink>：类加载器溢出，导致 <errorname>OutOfMemoryError: "
+"PermGen</errorname> 错误。要解决这个问题，EAP 现在使用修复了 <errorname>OutOfMemoryError</errorname> 的<filename>beanutils 1.8.0</filename>。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1062
@@ -2250,6 +2279,9 @@
 "created and is now displayed whenever a <exceptionname>HTTP Status 500</"
 "exceptionname> exception occurs."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
+"ulink>：当出现 <exceptionname>HTTP Status 500</exceptionname> 异常时，JMX 源代码将被显示。为了解决这个问题，我们创建了一个错误页面 <filename>genericError.jsp</filename>，每当遇到 <exceptionname>HTTP Status 500</"
+"exceptionname> 异常时它就会显示。"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:1071
@@ -2267,7 +2299,7 @@
 #: Release_Notes_CP06.xml:1078
 #, no-c-format
 msgid "General Known Issues"
-msgstr ""
+msgstr "普通的已知问题"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1082
@@ -2281,12 +2313,14 @@
 "automatically generated as a footnote and places a number beside that of the "
 "JIRA, referencing a footnote that does not appear."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1286\">JBPAPP-1286</"
+"ulink>：PDF 里的表和列表没有显示脚注。这个问题存在于 FOP 里且目前没有解决办法。在这种情况下，我们只能尽可能地不使用脚注，然而在发行注记等文档里，其 JIRA 地址是自动生成为脚注的，而且在地址前还有一个数字，引用没有出现的脚注。"
 
 #. Tag: title
 #: Release_Notes_CP06.xml:1090
 #, no-c-format
 msgid "Hibernate Known Issues"
-msgstr ""
+msgstr "Hibernate 里的已知问题"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1094
@@ -2302,16 +2336,15 @@
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1099
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1555\">JBPAPP-1555</"
 "ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it "
 "should be set up to use image and text. Tests attaining to this currently "
 "fail with the message:"
 msgstr ""
-"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
-"ulink>：允许用子软件包的方式在同一台机器上设立多个实例。本发行版本里的 -bin "
-"文>件带有这个功能。 "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1555\">JBPAPP-1555</"
+"ulink>：目前在 Hibernate 里，SybaseDialect 把 Blob 和 Clob 用于图像和文本。获取它们的测试不能运行，并产生如下信息："
 
 #. Tag: screen
 #: Release_Notes_CP06.xml:1102
@@ -2353,6 +2386,8 @@
 "suggested workaround for this case is to add the following code follwing the "
 "defining of the new stored procedure:"
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1546\">JBPAPP-1546</"
+"ulink>：当使用 Sybase 时，<methodname>SchemaExport</methodname> 不能用于创建 Chained 事务模式的存储过程。我们推荐的办法是在存储过程定义的后面添加下列的代码："
 
 #. Tag: programlisting
 #: Release_Notes_CP06.xml:1116
@@ -2365,19 +2400,24 @@
 "        &lt;drop/&gt;\n"
 "&lt;/database-object&gt;"
 msgstr ""
+"&lt;database-object&gt;\n"
+"        &lt;create&gt;\n"
+"                sp_procxmode paramHandling, 'chained'\n"
+"        &lt;/create&gt;\n"
+"        &lt;drop/&gt;\n"
+"&lt;/database-object&gt;"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1119
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1545\">JBPAPP-1545</"
 "ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase "
 "environment and there are three or more joins where at least one of the "
 "joins involves a union."
 msgstr ""
-"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
-"ulink>：允许用子软件包的方式在同一台机器上设立多个实例。本发行版本里的 -bin "
-"文>件带有这个功能。 "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1545\">JBPAPP-1545</"
+"ulink>：当 Hibernate 在 Sybase 环境里运行且有三个或更多 join 而其中至少一个涉及 union 时，ANSI joins 不能正常运行。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1122
@@ -2449,6 +2489,7 @@
 #. Tag: para
 #: Release_Notes_CP06.xml:1148
 #, no-c-format
+#, fuzzy
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1068\">JBPAPP-1068</"
 "ulink>: When using Microsoft SQL and <code>@Type(type=\"text\")</code> in "
@@ -2464,7 +2505,7 @@
 msgid ""
 "The data types <varname>text</varname> and <varname>varchar</varname> are "
 "incompatible in the equal to operator."
-msgstr ""
+msgstr "数据类型 <varname>text</varname> 和 <varname>varchar</varname> "
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1154
@@ -2475,6 +2516,9 @@
 "measurements when returning database values such as <code>TIME</code> and "
 "<code>TIMESTAMP</code>."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1063\">JBPAPP-1063</"
+"ulink>：对于返回的数据库值如 <code>TIME</code> 和 "
+"<code>TIMESTAMP</code>，目前 MySQL 不支持微秒和毫秒的度量。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1159
@@ -2485,6 +2529,8 @@
 "Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the "
 "Hypersonic database is planned for future releases."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-953\">JBPAPP-953</"
+"ulink>：Hibernate Core 和 Annotations 目前不支持 Hypersonic 1.8.0.8。对 1.8.0.8 版本的支持将放在以后的版本里。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1164
@@ -2496,6 +2542,8 @@
 "in relation to the EJB3 configuration, transaction operations when they are "
 "extended and packaging."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-946\">JBPAPP-946</"
+"ulink>：Hibernate Entity Manager 里和 EJB3 配置和事务操作在扩展和打包时出现三个不同的 <exceptionname>NullPointerExceptions</exceptionname>。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1169
@@ -2509,6 +2557,8 @@
 "thread is forced to undertake all the procedure while the other threads are "
 "left dormant."
 msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-906\">JBPAPP-906</"
+"ulink>：修复了 Hibernate Core 里的一个程序错误，这里使用了不稳定的同步的 Java6 <methodname>ClassLoader.loadClass</methodname> 方法来创建解序列化的字符串。当多个线程加载包含字符串队列的数据库记录时，其中一个线程将被迫承担所有的过程而其他线程则无事可做。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1172
@@ -2518,10 +2568,12 @@
 "ClassLoader.allowArraySyntax=true</code>, which can be a default setting "
 "within the <filename>run.conf</filename> file."
 msgstr ""
+"要解决这个问题，可使用 <code>-Dsun.lang."
+"ClassLoader.allowArraySyntax=true</code>，这可以是 <filename>run.conf</filename> 文件里的缺省设置。"
 
 #. Tag: para
 #: Release_Notes_CP06.xml:1177
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
 "ulink>: Within the Hibernate component of the Enterprise Application "
@@ -2533,5 +2585,5 @@
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
 "ulink>：由于对 JDK 1.6 支持，在 EAP 的 Hibernate 组件里的 HashMap 和 HashSet "
 "迭代顺序进行了修改。然而，这意味着 union 子句和 union 子类里的列顺序会改变，"
-"从而对组件的性能有着轻微的影响。 "
+"从而对组件的性能有着轻微的影响。"

More information about the jboss-cvs-commits mailing list