[jboss-cvs] JBossAS SVN: r100788 - 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 Feb 10 00:57:31 EST 2010
Author: xhuang at jboss.com
Date: 2010-02-10 00:57:31 -0500 (Wed, 10 Feb 2010)
New Revision: 100788
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Administration_And_Configuration_Guide.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po
Log:
update
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po 2010-02-10 05:31:06 UTC (rev 100787)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po 2010-02-10 05:57:31 UTC (rev 100788)
@@ -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:16\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-02-10 12:20+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,48 +22,29 @@
msgstr "关于开源软件"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The basic idea behind open source is very simple: When programmers can read, "
-"redistribute, and modify the source code for a piece of software, the "
-"software evolves. People improve it, people adapt it, people fix bugs. And "
-"this can happen at a speed that, if one is used to the slow pace of "
-"conventional software development, seems astonishing. Open Source is an "
-"often-misunderstood term relating to free software. The Open Source "
-"Initiative"
-msgstr ""
-"开源软件背后的基本逻辑很简单：当程序员可以读取、分发和修改源代码时，软件就会"
-"进步。人们改进它、采用它并修复错误。对于习惯于传统软件开发的慢节奏的人来说，"
-"开源软件的开发速度可能会让人感到惊奇。开源软件通常被误解为免费软件。Open "
-"Source Initiative (OSI) 网站提供了一些资源以定义开源软件的不同方面，其中包"
-"括：<ulink url=\"http://www.opensource.org/docs/definition.html\">http://www."
-"opensource.org/docs/definition.html</ulink>。OSI 主页上的如下内容很好的总结了"
-"和 JBoss 相关的关键概念："
+#, no-c-format
+msgid "The basic idea behind open source is very simple: When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing. Open Source is an often-misunderstood term relating to free software. The Open Source Initiative"
+msgstr "开源软件背后的基本逻辑很简单：当程序员可以读取、分发和修改源代码时，软件就会进步。人们改进它、采用它并修复错误。对于习惯于传统软件开发的慢节奏的人来说，开源软件的开发速度可能会让人感到惊奇。开源软件通常被误解为免费软件。"
#. Tag: primary
#, no-c-format
msgid "OSI"
-msgstr ""
+msgstr "OSI"
#. Tag: indexterm
#, no-c-format
-msgid ""
-"(OSI) web site provides a number of resources that define the various "
-"aspects of Open Source including an Open Source Definition"
-msgstr ""
+msgid "(OSI) web site provides a number of resources that define the various aspects of Open Source including an Open Source Definition"
+msgstr "(OSI) 网站提供了一些定义不同的开源概念的资源，其终包括 Open Source Definition。"
#. Tag: primary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Open Source Definition"
-msgstr "开源促进会（Open Source Initiative）"
+msgstr "开源软件定义（Open Source Definition）"
#. Tag: indexterm
#, no-c-format
-msgid ""
-"at: <ulink url=\"http://www.opensource.org/docs/definition.html\">http://www."
-"opensource.org/docs/definition.html</ulink>. The following quote from the "
-"OSI home page summarizes the key aspects as they relate to JBoss nicely:"
-msgstr ""
+msgid "at: <ulink url=\"http://www.opensource.org/docs/definition.html\">http://www.opensource.org/docs/definition.html</ulink>. The following quote from the OSI home page summarizes the key aspects as they relate to JBoss nicely:"
+msgstr "它位于 <ulink url=\"http://www.opensource.org/docs/definition.html\">http://www.opensource.org/docs/definition.html</ulink>。OSI 主页里的以下引用很好地总结了和 JBoss 相关的关键性的内容："
#. Tag: title
#, no-c-format
@@ -72,28 +53,16 @@
#. Tag: para
#, no-c-format
-msgid ""
-"We in the open source community have learned that this rapid evolutionary "
-"process produces better software than the traditional closed model, in which "
-"only very few programmers can see the source and everybody else must blindly "
-"use an opaque block of bits."
-msgstr ""
-"我们从开源社区认识到快速改良方式比传统的封闭模式（只有极少的程序员可以看到代"
-"码、而其他人只能盲目的使用一些不透明的模块）能更快的开发软件。"
+msgid "We in the open source community have learned that this rapid evolutionary process produces better software than the traditional closed model, in which only very few programmers can see the source and everybody else must blindly use an opaque block of bits."
+msgstr "我们从开源社区认识到快速改良方式比传统的封闭模式（只有极少的程序员可以看到代码、而其他人只能盲目的使用一些不透明的模块）能更快的开发软件。"
#. Tag: para
#, no-c-format
-msgid ""
-"Open Source Initiative exists to make this case to the commercial world."
+msgid "Open Source Initiative exists to make this case to the commercial world."
msgstr "开源促进会使这种方式进入到商业领域。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Open source software is an idea whose time has finally come. For twenty "
-"years it has been building momentum in the technical cultures that built the "
-"Internet and the World Wide Web. Now it's breaking out into the commercial "
-"world, and that's changing all the rules. Are you ready?"
-msgstr ""
-"开源软件的时代最终来临了。二十多年来，它已经成为了构建互联网和万维网的技术文"
-"化的里程碑。现在它进入了商业领域并将改变所有规则。你准备好了吗？"
+#, no-c-format
+msgid "Open source software is an idea whose time has finally come. For twenty years it has been building momentum in the technical cultures that built the Internet and the World Wide Web. Now it's breaking out into the commercial world, and that's changing all the rules. Are you ready?"
+msgstr "开源软件的时代最终来临了。二十多年来，它已经成为了构建互联网和万维网的技术文化的里程碑。现在它进入了商业领域并将改变所有规则。你准备好了吗？ "
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Administration_And_Configuration_Guide.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Administration_And_Configuration_Guide.po 2010-02-10 05:31:06 UTC (rev 100787)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Administration_And_Configuration_Guide.po 2010-02-10 05:57:31 UTC (rev 100788)
@@ -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:16\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-02-10 12:16+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"
@@ -17,21 +17,22 @@
"X-Generator: KBabel 1.11.4\n"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBoss Enterprise Application Platform Infrastructure"
-msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
+msgstr "JBoss 企业级应用程序平台基础结构"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBoss Enterprise Application Platform 5 Configuration"
-msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
+msgstr "JBoss 企业级应用程序平台 5 的配置"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Clustering Guide"
-msgstr "群集"
+msgstr "群集指南"
#. Tag: title
#, no-c-format
msgid "Performance Tuning"
-msgstr ""
+msgstr "性能调优"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po 2010-02-10 05:31:06 UTC (rev 100787)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po 2010-02-10 05:57:31 UTC (rev 100788)
@@ -8,7 +8,7 @@
"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: 2010-02-09 11:21+1000\n"
+"PO-Revision-Date: 2010-02-10 12:15+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -22,9 +22,9 @@
msgstr "群集的 Entity EJBs"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "In a JBoss Enterprise Application Platform cluster, entity bean instance caches need to be kept in sync across all nodes. If an entity bean provides remote services, the service methods need to be load balanced as well."
-msgstr "在 JBoss AS 群集系统里，entity bean 实例需要在所有节点间保持同步。如果某个 entity bean 提供了远程服务，那么该服务的方法也需要进行负载平衡。"
+msgstr "在 JBoss AS 群集系统里，entity bean 实例需要在所有节点间保持同步。如果某个 entity bean 提供了远程服务，那么该服务的方法也需要进行负载平衡。 "
#. Tag: title
#, no-c-format
@@ -32,9 +32,9 @@
msgstr "EJB 3.0 里的 Entity Bean"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "In EJB 3.0, entity beans primarily serve as a persistence data model. They do not provide remote services. Hence, the entity bean clustering service in EJB 3.0 primarily deals with distributed caching and replication, instead of load balancing."
-msgstr "在 EJB 3.0 里，entity beans 主要以持久化数据模型出现。它们不提供远程服务。因此，EJB 3.0 里的 entity bean 群集服务主要处理分布式缓存和复制，而不是负载平衡。"
+msgstr "在 EJB 3.0 里，entity beans 主要以持久化数据模型出现。它们不提供远程服务。因此，EJB 3.0 里的 entity bean 群集服务主要处理分布式缓存和复制，而不是负载平衡。 "
#. Tag: title
#, no-c-format
@@ -42,24 +42,24 @@
msgstr "配置分布式缓存"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "To avoid round trips to the database, you can use a cache for your entities. JBoss EJB 3.0 entity beans are implemented by Hibernate, which has support for a second-level cache. The second-level cache provides the following functionalities:"
-msgstr "为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能："
+msgstr "为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能： "
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "If you persist a cache-enabled entity bean instance to the database via the entity manager, the entity will be inserted into the cache."
-msgstr "如果你通过 entity manager 来使应用缓存的 entity bean 的实例持久化，这个 entity 会被储存到缓存里。"
+msgstr "如果你通过 entity manager 来使应用缓存的 entity bean 的实例持久化，这个 entity 会被储存到缓存里。 "
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "If you update an entity bean instance, and save the changes to the database via the entity manager, the entity will be updated in the cache."
-msgstr "如果你通过 entity manager 更新 entity bean 实例并把更改保存到数据库里，缓存里的这个 entity 将被更新。"
+msgstr "如果你通过 entity manager 更新 entity bean 实例并把更改保存到数据库里，缓存里的这个 entity 将被更新。 "
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "If you remove an entity bean instance from the database via the entity manager, the entity will be removed from the cache."
-msgstr "如果你通过 entity manager 把 entity bean 实例从数据库里删除，这个 entity 也将从缓存里删除。"
+msgstr "如果你通过 entity manager 把 entity bean 实例从数据库里删除，这个 entity 也将从缓存里删除。 "
#. Tag: para
#, no-c-format
@@ -67,9 +67,9 @@
msgstr "如果你通过 entity manager 从数据库里载入缓存的 entity，而这个这个 entity 并不在缓存里，这个 entity 会被插入到缓存里。"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "As well as a region for caching entities, the second-level cache also contains regions for caching collections, queries, and timestamps. The Hibernate setup used for the JBoss EJB 3.0 implementation uses JBoss Cache as its underlying second-level cache implementation."
-msgstr "为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能："
+msgstr "除了缓存实体的 region，两级缓存也包含缓存集合、查询和时间戳的 region。用于 JBoss EJB 3.0 实现的 Hibernate 使用 JBoss Cache 作为其底层的二级缓存实现。"
#. Tag: para
#, no-c-format
@@ -317,9 +317,9 @@
msgstr "hibernate.cache.region.jbc2.cachefactory"
#. Tag: entry
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JNDI name to which the <literal>CacheManager</literal> instance is bound."
-msgstr "<literal>Scheduler</literal> 将设置为 null 的任何权限定类名。"
+msgstr "<literal>CacheManager</literal> 实例绑定的 JNDI 名称。"
#. Tag: para
#, no-c-format
@@ -332,19 +332,19 @@
msgstr "配置 entity beans 的缓存"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Next we need to configure which entities to cache. The default is to not cache anything, even with the settings shown above. We use the <literal>@org.hibernate.annotations.Cache</literal> annotation to tag entity beans that needs to be cached."
-msgstr "下一步我们需要配置哪些实体被缓存。就像上面所展示的样，缺省是什么都不缓存。我们使用 <literal>@org.hibernate.annotations.Cache</literal> 注解来标记需要缓存的 entity bean。"
+msgstr "下一步我们需要配置哪些实体被缓存。就像上面所展示的样，缺省是什么都不缓存。我们使用 <literal>@org.hibernate.annotations.Cache</literal> 注解来标记需要缓存的 entity bean。 "
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "A very simplified rule of thumb is that you will typically want to do caching for objects that rarely change, and which are frequently read. You can fine tune the cache for each entity bean in the appropriate JBoss Cache configuration file, e.g. jboss-cache-manager-jboss-beans.xml. For instance, you can specify the size of the cache. If there are too many objects in the cache, the cache can evict the oldest or least used objects, depending on configuration, to make room for new objects. Assuming the region_prefix specified in <literal>persistence.xml</literal> was <literal>myprefix</literal>, the default name of the cache region for the <literal>com.mycompany.entities.Account</literal> entity bean would be <literal>/myprefix/com/mycompany/entities/Account</literal>."
-msgstr "一个简单的原则就是，你应该对很少变动和频繁使用的对象进行缓存.你可以在 <literal>ejb3-entity-cache-service.xml</literal> 配置文件里为每个 entity bean 微调缓存设置。例如，你可以指定缓存的大小。如果缓存里的对象太多，缓存有可能挤掉最老的对象（或者最少用的对象，依你的配置而定）来给新对象留出空间。假设 <literal>persistence.xml</literal> 里指定的 region_prefix 是 myprefix，entity bean 的<literal>com.mycompany.entities.Account</literal> 缺省的缓存 region 是 <literal>/myprefix/com/mycompany/entities/Account</literal>。"
+msgstr "一个简单的原则就是，你应该对很少变动和频繁使用的对象进行缓存.你可以在 <literal>ejb3-entity-cache-service.xml</literal> 配置文件里为每个 entity bean 微调缓存设置。例如，你可以指定缓存的大小。如果缓存里的对象太多，缓存有可能挤掉最老的对象（或者最少用的对象，依你的配置而定）来给新对象留出空间。假设 <literal>persistence.xml</literal> 里指定的 region_prefix 是 myprefix，entity bean 的<literal>com.mycompany.entities.Account</literal> 缺省的缓存 region 是 <literal>/myprefix/com/mycompany/entities/Account</literal>。 "
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "If you do not specify a cache region for an entity bean class, all instances of this class will be cached using the <literal>defaultEvictionRegionConfig</literal> as defined above. The @Cache annotation exposes an optional attribute “region” that lets you specify the cache region where an entity is to be stored, rather than having it be automatically be created from the fully-qualified class name of the entity class."
-msgstr "如果你没有为 entity bean 类指定缓存区（cache region），这个类的所有实例将象上面定义的一样缓存在 <literal>/_default</literal> 区里。@Cache 注解开放一个可选的属性“region”，它让你指定实体所存储的缓存区，而不是根据实体类的全限定名自动创建。"
+msgstr "如果你没有为 entity bean 类指定缓存区（cache region），这个类的所有实例将象上面定义的一样缓存在 <literal>defaultEvictionRegionConfig</literal> 区里。@Cache 注解开放一个可选的属性“region”，它让你指定实体所存储的缓存区，而不是根据实体类的全限定名自动创建。"
#. Tag: para
#, no-c-format
@@ -357,9 +357,9 @@
msgstr "查询结果的缓存"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The EJB3 Query API also provides means for you to save the results (i.e., collections of primary keys of entity beans, or collections of scalar values) of specified queries in the second-level cache. Here we show a simple example of annotating a bean with a named query, also providing the Hibernate-specific hints that tells Hibernate to cache the query."
-msgstr "EJB3 Query API 也为你提供了把查询结果（如 entity bean 的主键集合或标量结果的集合）保存在二级缓存里的方法。在这里我们演示了一个简单的例子，它注解了带有命名查询的 bean，且提供 Hibernate 专有的指令来让 Hibernate 缓存这个查询。"
+msgstr "EJB3 Query API 也为你提供了把查询结果（如 entity bean 的主键集合或标量结果的集合）保存在二级缓存里的方法。在这里我们演示了一个简单的例子，它注解了带有命名查询的 bean，且提供 Hibernate 专有的指令来让 Hibernate 缓存这个查询。 "
#. Tag: para
#, no-c-format
@@ -377,9 +377,9 @@
msgstr "@NamedQueries, @NamedQuery and @QueryHint 注解都在 javax.persistence 包里。关于如何使用 EJB3 查询以及缓存查询结果的更多信息，请参考 Hibernate 和 EJB3 的文档。 "
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "By default, Hibernate stores query results in JBoss Cache in a region named {region_prefix}/org/hibernate/cache/StandardQueryCache. Based on this, you can set up separate eviction handling for your query results. So, if the region prefix were set to myprefix in <filename>persistence.xml</filename>, you could, for example, create this sort of eviction handling:"
-msgstr "在缺省情况下，Hibernate 把查询结果存储在 JBoss Cache 的名为 {region_prefix}/org/hibernate/cache/StandardQueryCache 区里。基于此点，你可以为查询结果设立单独的逐出处理过程。所以，如果在 persistence.xml 里把区前缀设置为 myprefix，你可以创建这样的逐出处理过程："
+msgstr "在缺省情况下，Hibernate 把查询结果存储在 JBoss Cache 的名为 {region_prefix}/org/hibernate/cache/StandardQueryCache 区里。基于此点，你可以为查询结果设立单独的逐出处理过程。所以，如果在 <filename>persistence.xml</filename> 里把区前缀设置为 myprefix，你可以创建这样的逐出处理过程："
#. Tag: para
#, no-c-format
@@ -417,9 +417,9 @@
msgstr "为了平衡远程调用的负载，我们群集 EJB 2.x entity beans。所有的 bean 实例都实现同步，具有所有节点上的相同内容。"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "However, clustered EJB 2.x Entity Beans do not have a distributed locking mechanism or a distributed cache. They can only be synchronized by using row-level locking at the database level (see <literal><row-lock></literal> in the CMP specification) or by setting the Transaction Isolation Level of your JDBC driver to be <literal>TRANSACTION_SERIALIZABLE</literal>. Because there is no supported distributed locking mechanism or distributed cache Entity Beans use Commit Option \"B\" by default (See <literal>standardjboss.xml</literal> and the container configurations Clustered CMP 2.x EntityBean, Clustered CMP EntityBean, or Clustered BMP EntityBean). It is not recommended that you use Commit Option \"A\" unless your Entity Bean is read-only. (There are some design patterns that allow you to use Commit Option \"A\" with read-mostly beans. You can also take a look at the Seppuku pattern <ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\" />. JBoss may incorp!
orate this pattern into later versions.)"
-msgstr "然而，群集的 EJB 2.x Entity Beans 没有分布式的锁定机制或是缓存。它们只能用数据库层面的行级锁定（请参考 CMP 规范的<literal><row-lock></literal>）或是把 JDBC 驱动的事务隔离（Transaction Isolation）级别设为 <literal>TRANSACTION_SERIALIZABLE</literal> 来实现同步。因为缺乏分布式的锁定机制或是缓存支持，Entity Beans 缺省使用提交选项 \"B\"（请参考 <literal>standardjboss.xml</literal> 和 the container configurations Clustered CMP 2.x EntityBean，Clustered CMP EntityBean，或 Clustered BMP EntityBean）。我们不推荐你使用提交选项 \"A\"，除非你的 Entity Bean 是只读的。（有些设计模式允许你把提交选项\"A\" 用于 read-mostly beans。你也可以看看 Seppuku 模式：<ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\"></ulink>。JBoss 有可能把这个模式集成到以后的版本里。）"
+msgstr "然而，群集的 EJB 2.x Entity Beans 没有分布式的锁定机制或是缓存。它们只能用数据库层面的行级锁定（请参考 CMP 规范的<literal><row-lock></literal>）或是把 JDBC 驱动的事务隔离（Transaction Isolation）级别设为 <literal>TRANSACTION_SERIALIZABLE</literal> 来实现同步。因为缺乏分布式的锁定机制或是缓存支持，Entity Beans 缺省使用提交选项 \"B\"（请参考 <literal>standardjboss.xml</literal> 和 the container configurations Clustered CMP 2.x EntityBean，Clustered CMP EntityBean，或 Clustered BMP EntityBean）。我们不推荐你使用提交选项 \"A\"，除非你的 Entity Bean 是只读的。（有些设计模式允许你把提交选项\"A\" 用于 read-mostly beans。你也可以看看 Seppuku 模式：<ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\"></ulink>。JBoss 有可能把这个模式集成到以后的版本里。） "
#. Tag: para
#, no-c-format
More information about the jboss-cvs-commits
mailing list