[jboss-cvs] JBossAS SVN: r90981 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jul 9 00:08:39 EDT 2009
Author: xhuang at jboss.com
Date: 2009-07-09 00:08:39 -0400 (Thu, 09 Jul 2009)
New Revision: 90981
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2009-07-09 03:49:21 UTC (rev 90980)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2009-07-09 04:08:39 UTC (rev 90981)
@@ -9,13 +9,13 @@
"Project-Id-Version: J2EE_EJBs_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-07-08 16:03+1000\n"
-"Last-Translator: \n"
-"Language-Team: en_US <kde-i18n-doc at kde.org>\n"
+"PO-Revision-Date: 2009-07-09 14:08+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"
"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: Lokalize 0.3\n"
+"X-Generator: KBabel 1.11.4\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
@@ -4000,7 +4000,7 @@
#: J2EE_EJBs_On_JBOSS.xml:1168
#, no-c-format
msgid "Entity Bean Locking and Deadlock Detection"
-msgstr ""
+msgstr "Entity Bean 锁和死锁检测"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1169
@@ -4012,13 +4012,13 @@
"how to combat these issues. Deadlocking is formally defined and examined. "
"And, finally, we walk you through how to fine tune your system in terms of "
"entity bean locking."
-msgstr ""
+msgstr "本节提供关于 Entity Bean 锁以及在 JBoss 里如何访问和锁定 Entity Bean 的信息。本节也描述你可能遇到的问题以及如何解决。本节还对死锁进行正式的定义和讨论。最后，我们将带领你根据 Entity Bean 锁对系统进行调优。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1173
#, no-c-format
msgid "Why JBoss Needs Locking"
-msgstr ""
+msgstr "JBoss 为什么需要锁"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1174
@@ -4030,7 +4030,7 @@
"so that data is not corrupted by concurrent reads and writes. Databases "
"traditionally provide this sort of functionality with transactional scopes "
"and table and row locking facilities."
-msgstr ""
+msgstr "锁的目的是保护数据的完整性。有时候你需要确保在某个时间只有一个用户可以更改关键数据；有时候，对敏感性数据的访问需要进行序列化以防止并行读和写导致的数据损坏。数据库通常通过事务、表和记录锁来提供这种功能。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1177
@@ -4043,13 +4043,13 @@
"with caching, data integrity is a problem, so some form of application "
"server level locking is needed for entity beans to provide the transaction "
"isolation properties that you are used to with traditional databases."
-msgstr ""
+msgstr "Entity bean 为关系型数据提供了一个不错的面向对象的接口。除此以外，它们通过缓存和延迟更新以使数据库效率最高，从而减轻数据库负载以提高性能。但是，如果使用缓存，数据的完整性是个问题，Entity Bean 需要某种应用程序级别的锁来提供传统数据库要求的事务隔离属性。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1183
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Entity Bean Lifecycle"
-msgstr "EJB 2.x 里的 Entity Bean"
+msgstr "Entity Bean 的生命周期"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1184
@@ -4059,7 +4059,7 @@
"a given entity bean in memory at one time. This applies for every cache "
"configuration and every type of <literal>commit-option</literal>. The "
"lifecycle for this instance is different for every commit-option though."
-msgstr ""
+msgstr "根据 JBoss 的缺省配置，Entity Bean 在指定时刻只能存在一个活动的实例。这适用于每个缓存配置和每种 <literal>commit-option</literal> 类型。但这个实例的生命周期对于每个提交选项（commit-option）都不一样。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1189
@@ -4067,7 +4067,7 @@
msgid ""
"For commit option <emphasis>A</emphasis>, this instance is cached and used "
"between transactions."
-msgstr ""
+msgstr "对于提交选项 <emphasis>A</emphasis>，这个实例被缓存并在事务间使用。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1194
@@ -4077,7 +4077,7 @@
"between transactions, but is marked as dirty at the end of a transaction. "
"This means that at the start of a new transaction <literal>ejbLoad</literal> "
"must be called."
-msgstr ""
+msgstr "对于提交选项 <emphasis>B</emphasis>，这个实例被缓存并在事务间使用，但在事务结束时标记为 dirty。这表示在新事务启动时，<literal>ejbLoad</literal> 必须被调用。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1199
@@ -4086,7 +4086,7 @@
"For commit option <emphasis>C</emphasis>, this instance is marked as dirty, "
"released from the cache, and marked for passivation at the end of a "
"transaction."
-msgstr ""
+msgstr "对于提交选项 <emphasis>C</emphasis>，这个实例被标记为 dirty，从缓存里释放，并在事务结束时表示为钝化（passivation）。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1204
@@ -4097,6 +4097,8 @@
"cache. Otherwise, this option works in the same way as <emphasis>A</"
"emphasis>."
msgstr ""
+"对于提交选项 <emphasis>D</emphasis>，后台刷新线程定期地调用缓存里处于钝化状态的 Bean 的 <literal>ejbLoad</literal>。除此以外，这个选项和 <emphasis>A</"
+"emphasis> 相同。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1209
@@ -4107,7 +4109,7 @@
"passivates beans that have been placed in the passivation queue. A bean is "
"pulled out of the passivation queue and reused if the application requests "
"access to a bean of the same primary key."
-msgstr ""
+msgstr "当 Bean 被标记为钝化时，这个 Bean 被放入钝化队列里。每个 Entity Bean 容器都有一个钝化线程（passivation thread），它定期对钝化队列里的 Bean 进行钝化。如果应用程序请求访问具有相同主键的 Bean，这个 Bean 将从钝化队列里被提出。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1212
@@ -4117,13 +4119,13 @@
"out of cache entirely. It is not put into the passivation queue and is not "
"reused by an instance pool. Except for the passivation queue, there is no "
"entity bean instance pooling."
-msgstr ""
+msgstr "在出现异常或事务回滚时，这个 Entity Bean 实例将完全从缓存里剔除。它不会被放入钝化队列或者被任何实例池重用。除了钝化队列，不存在其他 Entity Bean 实例池。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1218
#, no-c-format
msgid "Default Locking Behavior"
-msgstr ""
+msgstr "缺省的锁行为"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1219
@@ -4134,7 +4136,7 @@
"Because there is only one allowed instance of a given entity bean active at "
"one time, JBoss employs two types of locks to ensure data integrity and to "
"conform to the EJB spec."
-msgstr ""
+msgstr "Entity bean 锁和 entity bean 实例是完全分离的。锁的逻辑是完全隔离的且由单独的锁对象进行管理。因为在某一时刻某个 Entity Bean 只能有一个活动实例，JBoss 使用两种类型的锁来保证数据的完整性而且符合 EJB 规格。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1224
@@ -4143,7 +4145,7 @@
"<emphasis role=\"bold\">Method Lock</emphasis>: The method lock ensures that "
"only one thread of execution at a time can invoke on a given Entity Bean. "
"This is required by the EJB spec."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Method Lock</emphasis>：方法锁确保在某一时刻只能有一个线程可以调用给定的 Entity Bean。这是 EJB 规格所要求的。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1229
@@ -4159,13 +4161,13 @@
"if any method at all is invoked on an entity bean within a transaction, no "
"other transaction can have access to this bean until the holding transaction "
"commits or is rolled back."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Transaction Lock</emphasis>：事务锁确保在某一时刻只有一个事务可以访问给定的 Entity Bean。这确保了应用程序级别的事务的 ACID 属性。既然在缺省情况下，给定 Entity Bean 在某一时刻只能有一个活动实例，JBoss 必须保护这个实例不被脏读或脏写（dirty write）。所以，缺省的 Entity Bean 锁的行为将锁定 Entity Bean 直至事务结束。这意味着如果在事务里调用了某一 Entity Bean 的任何方法，其他事务只有在该事务提交或回滚后才能访问这个 Bean。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1237
#, no-c-format
msgid "Pluggable Interceptors and Locking Policy"
-msgstr ""
+msgstr "可插拔拦截器和锁策略"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1238
@@ -4176,7 +4178,7 @@
"descriptor. Let's look at the <literal>container-interceptors</literal> "
"definition for the <emphasis>Standard CMP 2.x EntityBean</emphasis> "
"configuration."
-msgstr ""
+msgstr "我们可以看到 <literal>standardjboss.xml</literal> 描述符里的容器配置部分定义了 Entity Bean 的基本的生命周期和行为。让我们看看 <emphasis>Standard CMP 2.x EntityBean</emphasis> 的 <literal>container-interceptors</literal> 定义。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1241
@@ -4211,6 +4213,34 @@
"JDBCRelationInterceptor</interceptor>\n"
"</container-interceptors>"
msgstr ""
+"<container-interceptors>\n"
+" <interceptor>org.jboss.ejb.plugins."
+"ProxyFactoryFinderInterceptor</interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.LogInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</"
+"interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</"
+"interceptor>\n"
+" <interceptor metricsEnabled=\"true\">org.jboss.ejb.plugins."
+"MetricsInterceptor</interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.resource.connectionmanager."
+"CachedConnectionInterceptor</interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins."
+"EntitySynchronizationInterceptor</interceptor>\n"
+" <interceptor>org.jboss.ejb.plugins.cmp.jdbc."
+"JDBCRelationInterceptor</interceptor>\n"
+"</container-interceptors>"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1242
@@ -4219,7 +4249,7 @@
"The interceptors shown above define most of the behavior of the entity bean. "
"Below is an explanation of the interceptors that are relevant to this "
"section."
-msgstr ""
+msgstr "这个拦截器展示了 Entity Bean 的多数行为的定义。下面是对和这些内容相关的拦截器的解释。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1247
@@ -4229,7 +4259,7 @@
"interceptor's role is to schedule any locks that must be acquired before "
"the invocation is allowed to proceed. This interceptor is very lightweight "
"and delegates all locking behavior to a pluggable locking policy."
-msgstr ""
+msgstr "<emphasis role=\"bold\">EntityLockInterceptor</emphasis>：这个拦截器的任务是调度任何处理调用前所要求的锁。这个拦截器是非常轻量级的，它把所有锁行为都委托给了可插拔的锁策略。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1252
@@ -4239,7 +4269,7 @@
"this interceptor is to find the entity bean within the cache or create a new "
"one. This interceptor also ensures that there is only one active instance of "
"a bean in memory at one time."
-msgstr ""
+msgstr "<emphasis role=\"bold\">EntityInstanceInterceptor</emphasis>：这个拦截器的任务是找到缓存里的 Entity Bean 或者创建一个新的。这个拦截器也要确保在某一时刻内存里某个 Entity Bean 只有一个活动实例。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1257
@@ -4257,12 +4287,15 @@
"specification are taken care of here as well as the JBoss specific commit-"
"option <emphasis>D</emphasis>."
msgstr ""
+"<emphasis role=\"bold\">EntitySynchronizationInterceptor</emphasis>：这个拦截器的作用是将缓存状态和底层存储同步。它使用 EJB 规格的 <literal>ejbLoad</literal> 和 "
+"<literal>ejbStore</literal> 模式来完成。使用事务时用事务限界来触发。它通过 JTA 接口向底层事务监控程序注册一个回调方法。如果不涉及事务，这个策略会在调用返回时存储状态。这里介绍了 Synchronization 策略 <emphasis>A</"
+"emphasis>、<emphasis>B</emphasis> 和 <emphasis>C</emphasis>，以及 JBoss 专有的提交选项 <emphasis>D</emphasis>。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1265
#, no-c-format
msgid "Deadlock"
-msgstr ""
+msgstr "死锁"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1266
@@ -4282,12 +4315,16 @@
"are deadlocked waiting for access to the resource already locked by the "
"other thread."
msgstr ""
+"本节的主题是找到死锁问题并解决它们。我们将描述什么是死锁的 MBean，你怎样删除它们并解决死锁。当两个或以上的线程都锁定共享资源时，死锁就可能发生。<xref linkend=\"Deadlock_-"
+"Deadlock_definition_example\"/> 演示了一个简单的死锁情形。在这里，<literal>Thread 1</literal> 具有 <literal>Bean A</"
+"literal> 的锁，而 <literal>Thread 2</literal> 有对 <literal>Bean B</"
+"literal> 的锁。然后，<literal>Thread 1</literal> 试图锁住 <literal>Bean B</literal> 却堵塞了，因为 <literal>Thread 2</literal> 已经锁定了它。类似地，当 <literal>Thread 2</literal> 试图锁住 A 时也会堵塞，因为 <literal>Thread 1</literal> 已经锁定了它。此时，这两个线程都处于死锁状态，都在等待对已经被对方锁定的资源的访问。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1270
#, no-c-format
msgid "Deadlock definition example"
-msgstr ""
+msgstr "死锁定义的示例"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1277
@@ -4300,13 +4337,13 @@
"not careful about ordering the access to them. Various techniques and "
"advanced configurations can be used to avoid deadlocking problems. They are "
"discussed later in this section."
-msgstr ""
+msgstr "JBoss 的缺省锁策略是当调用发生在事务的上下文里时锁住 Entity Bean，直到事务完成为止。由此，如果存在长期运行的、却又访问许多 Entity Bean 的事务，或者你没有注意到访问顺序时，死锁就非常容易发生。你可以使用不同的技术和高级配置来避免死锁问题。本节将在后面讨论这些技术和配置。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1281
#, no-c-format
msgid "Deadlock Detection"
-msgstr ""
+msgstr "死锁的检测"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1282
@@ -4320,48 +4357,50 @@
"graph may look like is given in <xref linkend=\"Deadlock_Detection-"
"An_example_blocked_transaction_table\"/>."
msgstr ""
+"幸运的是，JBoss 能够执行死锁检测。JBoss 有一个全局的关于处于等待或阻塞状态的事务的内部图。当一个线程决定它不能获取 Entity Bean 锁时，它会知道哪个事务正锁住这个 Bean 并把自己添加到阻塞事务图里。<xref linkend=\"Deadlock_Detection-"
+"An_example_blocked_transaction_table\"/> 是这种图的一个例子。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1286
#, no-c-format
msgid "An example blocked transaction table"
-msgstr ""
+msgstr "阻塞事务表示例"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1290
#, no-c-format
msgid "Blocking TX"
-msgstr ""
+msgstr "阻塞的事务"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1293
#, no-c-format
msgid "Tx that holds needed lock"
-msgstr ""
+msgstr "持有所需锁的事务"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1300 J2EE_EJBs_On_JBOSS.xml:1319
#, no-c-format
msgid "<entry>Tx1</entry>"
-msgstr ""
+msgstr "<entry>Tx1</entry>"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1303
#, no-c-format
msgid "<entry>Tx2</entry>"
-msgstr ""
+msgstr "<entry>Tx2</entry>"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1308
#, no-c-format
msgid "<entry>Tx3</entry>"
-msgstr ""
+msgstr "<entry>Tx3</entry>"
#. Tag: entry
#: J2EE_EJBs_On_JBOSS.xml:1311 J2EE_EJBs_On_JBOSS.xml:1316
#, no-c-format
msgid "<entry>Tx4</entry>"
-msgstr ""
+msgstr "<entry>Tx4</entry>"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1326
@@ -4374,7 +4413,7 @@
"deadlock and will throw an <literal>ApplicationDeadlockException</literal>. "
"This exception will cause a transaction rollback which will cause all locks "
"that transaction holds to be released."
-msgstr ""
+msgstr "在线程实际阻塞前，它会试图检查是否存在死锁。它通过检索阻塞事务图表来决定。当它扫描图表时，它会记住那些事务正在阻塞。如果它看到一个阻塞的节点在这个图里出现多于一次，它就知道有死锁出现并抛出 <literal>ApplicationDeadlockException</literal>。这个异常将导致事务回滚，从而使得这个事务持有的所有锁都被释放。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:1332
@@ -4741,7 +4780,7 @@
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1443
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<jboss>\n"
" <enterprise-beans>\n"
@@ -4762,25 +4801,22 @@
" </enterprise-beans>\n"
"</jboss>"
msgstr ""
-"<jboss> \n"
-" <enterprise-beans> \n"
-" <session> \n"
-" <ejb-name>nextgen.StatelessSession</ejb-"
-"name> \n"
-" <jndi-name>nextgen.StatelessSession</jndi-"
-"name> \n"
-" <clustered>True</clustered> \n"
-" <cluster-config> \n"
-" <partition-name>DefaultPartition</partition-"
-"name> \n"
-" <home-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin \n"
-" </home-load-balance-policy> \n"
-" <bean-load-balance-policy> \n"
-" org.jboss.ha.framework.interfaces.RoundRobin\n"
-" </bean-load-balance-policy>\n"
-" </cluster-config>\n"
-" </session>\n"
+"<jboss>\n"
+" <enterprise-beans>\n"
+" <entity>\n"
+" <ejb-name>MyCMP2Bean</ejb-name>\n"
+" <jndi-name>MyCMP2</jndi-name>\n"
+" <configuration-name>\n"
+" Instance Per Transaction CMP 2.x EntityBean\n"
+" </configuration-name>\n"
+" </entity>\n"
+" <entity>\n"
+" <ejb-name>MyBMPBean</ejb-name>\n"
+" <jndi-name>MyBMP</jndi-name>\n"
+" <configuration-name>\n"
+" Instance Per Transaction BMP EntityBean\n"
+" </configuration-name>\n"
+" </entity>\n"
" </enterprise-beans>\n"
"</jboss>"
@@ -5071,11 +5107,11 @@
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1555
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Most applications that use timers will want timers to be persisted. For that "
"the <literal>DatabasePersitencePolicy</literal> MBean should be used."
-msgstr "是"
+msgstr "大多数使用定时器的应用程序都希望持久化定时器，由此应该使用 <literal>DatabasePersitencePolicy</literal> MBean。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:1558
@@ -5092,16 +5128,24 @@
"txtimer.GeneralPurposeDatabasePersistencePlugin</attribute>\n"
"</mbean>"
msgstr ""
+"<mbean code=\"org.jboss.ejb.txtimer.DatabasePersistencePolicy\" \n"
+" name=\"jboss.ejb:service=EJBTimerService,persistencePolicy=database"
+"\">\n"
+" <!-- DataSource JNDI name -->\n"
+" <depends optional-attribute-name=\"DataSource\">jboss.jca:"
+"service=DataSourceBinding,name=DefaultDS</depends>\n"
+" <!-- The plugin that handles database persistence -->\n"
+" <attribute name=\"DatabasePersistencePlugin\">org.jboss.ejb."
+"txtimer.GeneralPurposeDatabasePersistencePlugin</attribute>\n"
+"</mbean>"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1561
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">DataSource</emphasis>: This is the MBean for the "
"DataSource that timer data will be written to."
-msgstr ""
-"<emphasis role=\"bold\">directory</emphasis>：这是建立访问日志文件的目录路"
-"径。"
+msgstr "<emphasis role=\"bold\">DataSource</emphasis>：用于定时器数据将写入的数据源的 MBean。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:1566
@@ -5112,5 +5156,6 @@
"<literal>org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin</"
"literal>."
msgstr ""
+"<emphasis role=\"bold\">DatabasePersistencePlugin</emphasis>：实现持久化策略（persistence strategy）的类的名称。它应该是 <literal>org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin</"
+"literal>。"
-
More information about the jboss-cvs-commits
mailing list