[jboss-cvs] JBossAS SVN: r71774 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Apr 8 01:21:42 EDT 2008
Author: xhuang at jboss.com
Date: 2008-04-08 01:21:41 -0400 (Tue, 08 Apr 2008)
New Revision: 71774
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po
Log:
update
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2008-04-08 02:17:06 UTC (rev 71773)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2008-04-08 05:21:41 UTC (rev 71774)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_EJBs_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-12-03 00:52+0000\n"
-"PO-Revision-Date: 2008-04-07 13:50+1000\n"
+"PO-Revision-Date: 2008-04-08 15:07+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -2360,7 +2360,7 @@
msgstr ""
"在 EJB 定义里包括 <literal>container-configuration</literal> 元素，你可以为每个 EJB 的类指定一个容器配置。虽然定义全新的容器配置是被支持的，但我们通常不这么做。在 <literal>jboss.xml</literal> 级别定义 <literal>container-configuration</"
"literal> 的典型做法是覆盖一个或多个取值于 <literal>standardjboss.xml</literal> 的 <literal>container-"
-"configuration</literal>。"
+"configuration</literal>。这可以通过指定"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:573
@@ -2425,7 +2425,7 @@
"<literal>configuration-name</literal> element for every type of EJB, and the "
"mappings from the EJB type to default container configuration name are as "
"follows:"
-msgstr ""
+msgstr "如果 EJB 不在 EJB JAR 的部署单元里提供容器配置，容器工厂将从基于 EJB 类型的 <literal>standardjboss.xml</literal> 描述符里选择一个容器配置。所以，实际上对于每个类型的 EJB 都有一个隐形的 <literal>configuration-name</literal> 元素，下面是从 EJB 类型到缺省的容器配置名的对应关系："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:579
@@ -2453,19 +2453,19 @@
#: J2EE_EJBs_On_JBOSS.xml:594
#, no-c-format
msgid "stateless session = Standard Stateless SessionBean"
-msgstr ""
+msgstr "stateless session = Standard Stateless SessionBean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:599
#, no-c-format
msgid "stateful session = Standard Stateful SessionBean"
-msgstr ""
+msgstr "stateful session = Standard Stateful SessionBean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:604
#, no-c-format
msgid "message driven = Standard Message Driven Bean"
-msgstr ""
+msgstr "message driven = Standard Message Driven Bean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:609
@@ -2476,7 +2476,7 @@
"provides for a more self-contained descriptor to include the "
"<literal>configuration-name</literal> element, but this is purely a matter "
"of style."
-msgstr ""
+msgstr "如果要使用基于 Bean 类型的缺省容器配置，你不需要指定该 EJB 使用的容器配置。你也可以提供一个含有 <literal>configuration-name</literal> 的自包含的（self-contained）描述符，但这纯粹是使用风格的不同罢了。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:612
@@ -2489,7 +2489,7 @@
"implementations whose configuration is affected by other elements, so before "
"starting in on the configuration elements you need to understand the "
"<literal>org.jboss.metadata.XmlLoadable</literal> interface."
-msgstr ""
+msgstr "现在你已经知道如何指定 EJB 使用的容器配置，也懂得怎样定义部署单元级别的覆盖了，在下面的章节里我们将来看看 <literal>container-configuration</literal> 子元素。许多元素指定的接口的类实现的配置都受其他元素影响，所以在开始配置元素之前，你需要先理解 <literal>org.jboss.metadata.XmlLoadable</literal> 接口。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:615
@@ -2497,7 +2497,7 @@
msgid ""
"The <literal>XmlLoadable</literal> interface is a simple interface that "
"consists of a single method. The interface definition is:"
-msgstr ""
+msgstr "<literal>XmlLoadable</literal> 接口是一个由单一方法组成的简单接口。其接口定义是："
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:618
@@ -2526,13 +2526,13 @@
"fragment is what would be passed to the <literal>importXml</literal> method. "
"You will see a few examples of this as the container configuration elements "
"are described in the following sections."
-msgstr ""
+msgstr "实现这个接口的类的配置可以通过 XML 文档来指定。这个文档的根元素将被传递给 <literal>importXml</literal> 方法。在后面的章节里讲述容器配置元素时，你将看到一些这样的例子。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:623
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The container-name element"
-msgstr "Engine 元素"
+msgstr "container-name 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:624
@@ -2542,13 +2542,13 @@
"given configuration. EJBs link to a particular container configuration by "
"setting their <literal>configuration-name</literal> element to the value of "
"the <literal>container-name</literal> for the container configuration."
-msgstr ""
+msgstr "<literal>container-name</literal> 元素指定给定配置的唯一名称。EJB 通过将其 <literal>configuration-name</literal> 元素设置为 <literal>container-name</literal> 的值来链接特定的容器配置。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:630
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The call-logging element"
-msgstr "Engine 元素"
+msgstr "call-logging 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:631
@@ -2559,12 +2559,14 @@
"literal> should log method calls to a container. This is somewhat obsolete "
"with the change to log4j, which provides a fine-grained logging API."
msgstr ""
+"<literal>call-logging</literal> 元素的值为布尔值（true 或 false），它指定 <literal>LogInterceptor</"
+"literal> 是否应该为对容器的调用记录日志。这多少有点过时，因为 log4j 提供了细颗粒度的 API。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:637
#, no-c-format
msgid "The invoker-proxy-binding-name element"
-msgstr ""
+msgstr "invoker-proxy-binding-name 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:638
@@ -2577,12 +2579,14 @@
"binding-name</literal> element value will be used to create home and remote "
"proxies."
msgstr ""
+"<literal>invoker-proxy-binding-name</literal> 元素指定所使用的缺省调用者的名称。在缺乏 bean 级别的 <literal>invoker-bindings</literal> 规格时，其名称符合 <literal>invoker-proxy-"
+"binding-name</literal> 元素的值的 <literal>invoker-proxy-binding</literal> 将用来创建 home 和 remote 代理。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:644
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The sync-on-commit-only element"
-msgstr "Connector 元素"
+msgstr "sync-on-commit-only 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:645
@@ -2592,13 +2596,13 @@
"to be synchronized with the database only at commit time. Normally the state "
"of all the beans in a transaction would need to be synchronized when an "
"finder method is called or when an remove method is called, for example."
-msgstr ""
+msgstr "这是关于性能优化的配置，它使 Entity Bean 的状态仅在提交时才和数据库进行同步。而通常当 finder 方法或 remove 方法被调用时，事务里的所有 Bean 的状态都需要进行同步，例如："
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:651
#, no-c-format
msgid "insert-after-ejb-post-create"
-msgstr ""
+msgstr "insert-after-ejb-post-create"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:652
@@ -2610,13 +2614,13 @@
"fields as well as CMR fields to be set in a single insert, instead of the "
"default insert followed by an update, which allows removes the requirement "
"for relation ship fields to allow null values."
-msgstr ""
+msgstr "这是对 Entity Bean 的另外一种优化，它使新的 Enity Bean 大的数据库 insert 命令直到 <literal>ejbPostCreate</literal> 被调用时才执行。这允许在单个 insert 命令设置普通的 CMP 以及 CMR 字段，并取消了对相关字段允许空值的要求。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:658
#, no-c-format
msgid "call-ejb-store-on-clean"
-msgstr ""
+msgstr "call-ejb-store-on-clean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:659
@@ -2627,12 +2631,14 @@
"the instance was not modified in the transaction. Setting this to false will "
"cause JBoss to only call <literal>ejbStore</literal> for dirty objects."
msgstr ""
+"这个参数要求容器在提交事务时调用 Entity Bean 实例的 <literal>ejbStore</"
+"literal> 方法，即使该实例在事务里并没有改变。把它设置为 false 将使 JBoss 只对 dirty 对象调用 <literal>ejbStore</literal>。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:665
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The container-interceptors Element"
-msgstr "Connector 元素"
+msgstr "container-interceptors 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:666
@@ -2653,12 +2659,14 @@
"contract regarding security, transactions, persistence, and thread safety "
"derive from the interceptors."
msgstr ""
+"<literal>container-interceptors</literal> 元素指定一个或多个配置为容器的方法拦截器链的拦截器。拦截器元素的值是 <literal>org.jboss.ejb.Interceptor</literal> 接口实现的全限定类名。容器拦截器组成了一个允许 EJB 方法调用的 <literal>linked-list</literal> 结构。当 <literal>MBeanServer</"
+"literal> 往容器传递一个方法调用时，这个链里的第一个拦截器被启用。最后一个拦截器调用 Bean 上的商业方法。在本章的后面谈及容器插件框架时，我们将讨论 <literal>Interceptor</literal> 接口。通常，修改现有的标准 EJB 拦截器配置时你得小心行事，因为 EJB 是涉及安全性、事务、持久性和源于拦截器的线程安全的规格。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:672
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The instance-pool element"
-msgstr "Engine 元素"
+msgstr "instance-pool 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:673
@@ -2669,13 +2677,13 @@
"implementation to use as the container <literal>InstancePool</literal>. We "
"will discuss the InstancePool interface in detail latter in this chapter "
"when we talk about the container plugin framework."
-msgstr ""
+msgstr "<literal>instance-pool</literal> 元素指定了用作容器的 <literal>InstancePool</literal> 的 <literal>org.jboss.ejb.InstancePool</literal> 接口实现的全限定类名。在本章后面谈及容器插件框架时，我们将讨论 InstancePool 接口的细节。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:679
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The container-pool-conf element"
-msgstr "Connector 元素"
+msgstr "container-pool-conf 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:680
@@ -2690,12 +2698,15 @@
"support for elements shown in <xref linkend="
"\"The_container_pool_conf_element-The_container_pool_conf_element_DTD\"/>."
msgstr ""
+"如果 <literal>instance-pool</literal> 元素指定的 <literal>InstancePool</literal> 实现类也实现了 <literal>XmlLoadable</literal> 接口，<literal>container-pool-conf</literal> 将被传递给它。目前所有的 JBoss <literal>InstancePool</literal> 实现都源于 <literal>org."
+"jboss.ejb.plugins.AbstractInstancePool</literal>，它提供对 <xref linkend="
+"\"The_container_pool_conf_element-The_container_pool_conf_element_DTD\"/> 里出现的元素的支持。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:684
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The container-pool-conf element DTD"
-msgstr "Connector 元素"
+msgstr "container-pool-conf 元素 DTD"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:693
@@ -2706,6 +2717,8 @@
"although JBoss does not currently seed an <literal>InstancePool</literal> to "
"the <literal>MinimumSize</literal> value."
msgstr ""
+"<emphasis role=\"bold\">MinimumSize</emphasis>：<literal>MinimumSize</"
+"literal> 元素指定保留在实例池里的实例的最小数目。但 JBoss 目前并不把 <literal>InstancePool</literal> 的大小设置为 <literal>MinimumSize</literal>。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:698
@@ -2719,6 +2732,8 @@
"if the number of concurrent requests exceeds the <literal>MaximumSize</"
"literal> value."
msgstr ""
+"<emphasis role=\"bold\">MaximumSize</emphasis>：<literal>MaximumSize</"
+"literal> 指定了实例池里允许的实例的最大数目。对 <literal>MaximumSize</literal> 的缺省使用可能并非你所期望的。<literal>MaximumSize</literal> 是可用的 EJB 实例的最大数目，但如果当前的并行请求超过了 <literal>MaximumSize</literal> 的值，其他实例还会被创建。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:703
@@ -2733,6 +2748,8 @@
"will be blocked until an instance is freed back to the pool. The default "
"value for <literal>strictMaximumSize</literal> is false."
msgstr ""
+"<emphasis role=\"bold\">strictMaximumSize</emphasis>：如果你想限制实例池里的 EJB 的最大并行数目为 <literal>MaximumSize</"
+"literal>，你需要设置 <literal>strictMaximumSize</literal> 元素为 true。当 <literal>strictMaximumSize</literal> 元素为 true 时，活动的 EJB 实例的最大数目为 <literal>MaximumSize</literal>。当已经有 <literal>MaximumSize</literal> 个活动实例时，任何后来的请求都将被阻塞，直至有实例被释放。<literal>strictMaximumSize</literal> 的缺省值为 false。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:708
@@ -2750,12 +2767,15 @@
"9,223,372,036,854,775,807 or about 292,471,208 years, and this is the "
"default value."
msgstr ""
+"<emphasis role=\"bold\">strictTimeout</emphasis>：<literal>strictTimeout</literal> 元素控制请求等待实例池里的空闲对象所阻塞的时间。<literal>strictTimeout</"
+"literal> 定义在有 <literal>MaximumSize</literal> 个活动实例时，等待实例返回实例池的时间（毫秒）。小于或等于 0 的值表示不进行等待。当请求超时时将产生一个 <literal>java.rmi."
+"ServerException</literal> 实例并终止调用。它的类型为 <literal>Long</literal>，所以最大可能的等待时间是 9,223,372,036,854,775,807 或 292,471,208 年，且这是缺省值。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:716
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The instance-cache element"
-msgstr "Engine 元素"
+msgstr "instance-cache 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:717
@@ -2768,13 +2788,13 @@
"identity. We will discuss the <literal>InstanceCache</literal> interface in "
"detail latter in this chapter when we talk about the container plugin "
"framework."
-msgstr ""
+msgstr "<literal>instance-cache</literal> 元素指定 <literal>org.jboss.ejb.InstanceCache</literal> 实例接口的全限定名。这个元素仅对于 Entity 和 Stateful Session Bean 有意义，因为这种 EJB 类型才有相关联的标识。在本章后面谈及容器插件框架时我们将详细讨论 <literal>InstanceCache</literal> 接口。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:723
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The container-cache-conf element"
-msgstr "Connector 元素"
+msgstr "container-cache-conf 元素"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:724
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po 2008-04-08 02:17:06 UTC (rev 71773)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po 2008-04-08 05:21:41 UTC (rev 71774)
@@ -1,4 +1,3 @@
-# translation of J2EE_Security_On_JBOSS.po to Simplified Chinese
# translation of J2EE_Security_On_JBOSS.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
# Copyright (C) 2007, 2008 Free Software Foundation, Inc.
@@ -10,9 +9,9 @@
"Project-Id-Version: J2EE_Security_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-11-05 06:04+0000\n"
-"PO-Revision-Date: 2008-03-17 14:17+1000\n"
+"PO-Revision-Date: 2008-04-08 15:11+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: Simplified Chinese <en at li.org>\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"
@@ -1927,6 +1926,11 @@
"\"/>, and the full source code is available in the <literal>src/main/org/"
"jboss/book/security/ex1</literal> directory of the book examples."
msgstr ""
+"让我们来看看一个普通的 stateless session bean 上下文里的自定义 <literal>SecurityProxy</literal> 的简单例子。自定义的 <literal>SecurityProxy</literal> 控制无人可以用 4 个字符作为参数来调用这个 Bean 的 <literal>echo</literal> 方法。这对于基于角色的安全性控制来说是不可能的：你不可能定义一个 <literal>FourLetterEchoInvoker</literal> 角色，因为安全性上下文是方法参数，而不是调用者的属性。<xref linkend="
+"\"Enabling_Declarative_Security_in_JBoss_Revisited-"
+"The_example_1_custom_EchoSecurityProxy_implementation_that_enforces_the_echo_argument_based_security_constraint."
+"\"/> 里给出了自定义 <literal>SecurityProxy</literal> 的代码，你可以在 book 例程的 <literal>src/main/org/"
+"jboss/book/security/ex1</literal> 目录下找到完整的代码。"
#. Tag: title
#: J2EE_Security_On_JBOSS.xml:472
More information about the jboss-cvs-commits
mailing list