[jboss-cvs] JBossAS SVN: r71718 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Apr 4 00:58:31 EDT 2008
Author: xhuang at jboss.com
Date: 2008-04-04 00:58:30 -0400 (Fri, 04 Apr 2008)
New Revision: 71718
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_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-04 03:18:58 UTC (rev 71717)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2008-04-04 04:58:30 UTC (rev 71718)
@@ -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-03-30 11:24+1000\n"
+"PO-Revision-Date: 2008-04-04 14:58+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -471,12 +471,14 @@
"in-VM invocations. This is used to force <literal>call-by-value</literal> "
"semantics for method calls."
msgstr ""
+"<emphasis role=\"bold\">org.jboss.invocation.MarshallingInvokerInterceptor</"
+"emphasis>：继承 <literal>InvokerInterceptor</literal> 但不优化 VM 内部的调用。它被用来强制方法的 <literal>call-by-value（值调用）</literal>模式。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:132
#, no-c-format
msgid "Specifying the EJB Proxy Configuration"
-msgstr ""
+msgstr "指定 EJB 代理配置"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:133
@@ -490,31 +492,31 @@
"<literal>standardjboss.xml</literal> descriptor for the various default EJB "
"container configurations and the standard RMI/JRMP and RMI/IIOP transport "
"protocols. The current default proxy configurations are:"
-msgstr ""
+msgstr "要指定 EJB 调用传输和客户代理拦截器栈，你需要在 EJB JAR 的 <literal>META-INF/jboss.xml 或服务器的 <literal>standardjboss.xml</literal> 描述符文件里定义一个 <literal>invoker-proxy-binding</literal>。在不同的缺省 EJB 容器配置以及标准的 RMI/JRMP 和 RMI/IIOP 传输协议的 <literal>standardjboss.xml</literal> 描述符里，定义了几个缺省的 <literal>invoker-proxy-bindings</literal>。目前缺省的代理配置是： "
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:138
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">entity-rmi-invoker</emphasis>: a RMI/JRMP "
"configuration for entity beans"
-msgstr "<emphasis role=\"bold\">description</emphasis>：对attribute的描述"
+msgstr "<emphasis role=\"bold\">entity-rmi-invoker</emphasis>：用于 Enitty Bean 的 RMI/JRMP 配置。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:143
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">clustered-entity-rmi-invoker</emphasis>: a RMI/JRMP "
"configuration for clustered entity beans"
-msgstr "<emphasis role=\"bold\">description</emphasis>：对attribute的描述"
+msgstr "<emphasis role=\"bold\">clustered-entity-rmi-invoker</emphasis>：用于群集 Enitty Bean 的 RMI/JRMP 配置。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:148
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">stateless-rmi-invoker</emphasis>: a RMI/JRMP "
"configuration for stateless session beans"
-msgstr "<emphasis role=\"bold\">description</emphasis>：对attribute的描述"
+msgstr "<emphasis role=\"bold\">stateless-rmi-invoker</emphasis>：:用于 Stateless Session Bean 的 RMI/JRMP 配置。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:153
@@ -522,15 +524,15 @@
msgid ""
"<emphasis role=\"bold\">clustered-stateless-rmi-invoker</emphasis>: a RMI/"
"JRMP configuration for clustered stateless session beans"
-msgstr ""
+msgstr "<emphasis role=\"bold\">clustered-stateless-rmi-invoker</emphasis>：用于群集 Stateless Session Bean 的 RMI/JRMP 配置。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:158
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">stateful-rmi-invoker</emphasis>: a RMI/JRMP "
"configuration for clustered stateful session beans"
-msgstr "<emphasis role=\"bold\">description</emphasis>：对attribute的描述"
+msgstr "<emphasis role=\"bold\">stateful-rmi-invoker</emphasis>：用于 Stateful Session Bean 的 RMI/JRMP 配置。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:163
@@ -538,15 +540,15 @@
msgid ""
"<emphasis role=\"bold\">clustered-stateful-rmi-invoker</emphasis>: a RMI/"
"JRMP configuration for clustered stateful session beans"
-msgstr ""
+msgstr "<emphasis role=\"bold\">clustered-stateful-rmi-invoker</emphasis>：用于群集 Stateful Session Bean 的 RMI/JRMP 配置。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:168
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">message-driven-bean</emphasis>: a JMS invoker for "
"message driven beans"
-msgstr "<emphasis role=\"bold\">read-only</emphasis>：只读。"
+msgstr "<emphasis role=\"bold\">message-driven-bean</emphasis>：用于 Message Driven Bean 的 JMS 调用者。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:173
@@ -554,7 +556,7 @@
msgid ""
"<emphasis role=\"bold\">singleton-message-driven-bean</emphasis>: a JMS "
"invoker for singleton message driven beans"
-msgstr ""
+msgstr "<emphasis role=\"bold\">singleton-message-driven-bean</emphasis>：用于单点登录（Singleton）的 Message Driven Bean 的 JMS 调用者。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:178
@@ -562,7 +564,7 @@
msgid ""
"<emphasis role=\"bold\">message-inflow-driven-bean</emphasis>: a JMS invoker "
"for message inflow driven beans"
-msgstr ""
+msgstr "<emphasis role=\"bold\">message-inflow-driven-bean</emphasis>：用于 Message Inflow Driven Bean 的 JMS 调用者。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:183
@@ -570,15 +572,15 @@
msgid ""
"<emphasis role=\"bold\">jms-message-inflow-driven-bean</emphasis>: a JMS "
"inflow invoker for standard message driven beans"
-msgstr ""
+msgstr "<emphasis role=\"bold\">jms-message-inflow-driven-bean</emphasis>：用于标准 Message Driven Bean 的 JMS Inflow 调用者。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:188
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">iiop</emphasis>: a RMI/IIOP for use with session and "
"entity beans."
-msgstr "<emphasis role=\"bold\">description</emphasis>：对attribute的描述"
+msgstr "<emphasis role=\"bold\">iiop</emphasis>：用于 Session 和 Entity Bean 的 RMI/IIOP。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:193
@@ -591,18 +593,22 @@
"<xref linkend=\"Specifying_the_EJB_Proxy_Configuration-"
"The_invoker_proxy_binding_schema\"/>."
msgstr ""
+"为了引入新的协议綁定、或者自定义代理工厂、或者客户端的拦截器栈，你需要定义一个新的 <literal>invoker-"
+"proxy-binding</literal>。<xref linkend=\"Specifying_the_EJB_Proxy_Configuration-"
+"The_invoker_proxy_binding_schema\"/> 里给出了用于代理配置规格的完整的 <literal>invoker-proxy-binding</literal> "
+"DTD 片段。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:197
#, no-c-format
msgid "The invoker-proxy-binding schema"
-msgstr ""
+msgstr "invoker-proxy-binding 模式"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:204
#, no-c-format
msgid "The <literal>invoker-proxy-binding</literal> child elements are:"
-msgstr ""
+msgstr "<literal>invoker-proxy-binding</literal> 的子元素有："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:209
@@ -615,19 +621,19 @@
"to specify addition proxy bindings. You will see how this is done when we "
"look at the <literal>jboss.xml</literal> elements that control the server "
"side EJB container configuration."
-msgstr ""
+msgstr "<emphasis role=\"bold\">name</emphasis>：<literal>name</literal> 元素为 <literal>invoker-proxy-binding</literal> 赋予一个唯一名称。当设置缺省的代理綁定以及 EJB 部署级别来指定其他代理綁定时，这个名字被用来引用 EJB 容器配置里的綁定。看看 <literal>jboss.xml</literal> 里控制服务器端的 EJB 容器配置的元素的内容，你就知道这是如何实现的。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:214
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">invoker-mbean</emphasis>: The <literal>invoker-"
"mbean</literal> element gives the JMX <literal>ObjectName</literal> string "
"of the detached invoker MBean service the proxy invoker will be associated "
"with."
msgstr ""
-"<emphasis role=\"bold\">PartitionObjectName</emphasis>：与代理关联的群集服务"
-"的 JMX <literal>ObjectName</literal>。"
+"<emphasis role=\"bold\">invoker-mbean</emphasis>：<literal>invoker-"
+"mbean</literal> 元素指定了代理调用者将关联的脱管调用者（detached invoker）MBean 服务的 JMX <literal>ObjectName</literal> 字符串。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:219
@@ -641,14 +647,19 @@
"specific invoker and context. The current JBoss implementations of the "
"<literal>EJBProxyFactory</literal> interface include:"
msgstr ""
+"<emphasis role=\"bold\">proxy-factory</emphasis>：<literal>proxy-"
+"factory</literal> 元素指定代理工厂的全限定类名，这个工厂必须实现 <literal>org.jboss.ejb."
+"EJBProxyFactory</literal> 接口。<literal>EJBProxyFactory</literal> 处理代理的配置以及协议专有的调用者和上下文之间的联系。目前 JBoss 对 <literal>EJBProxyFactory</literal> 接口的实现包括："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:224
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">org.jboss.proxy.ejb.ProxyFactory</emphasis>: The RMI/"
"JRMP specific factory."
-msgstr "<emphasis role=\"bold\">file:/var/opt/apps/</emphasis>扫描指定的目录"
+msgstr ""
+"<emphasis role=\"bold\">org.jboss.proxy.ejb.ProxyFactory</emphasis>：RMI/"
+"JRMP 专有的工厂。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:229
@@ -656,7 +667,7 @@
msgid ""
"<emphasis role=\"bold\">org.jboss.proxy.ejb.ProxyFactoryHA</emphasis>: The "
"cluster RMI/JRMP specific factory."
-msgstr ""
+msgstr "<emphasis role=\"bold\">org.jboss.proxy.ejb.ProxyFactoryHA</emphasis>：群集 RMI/JRMP 专有的工厂。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:234
@@ -665,14 +676,18 @@
"<emphasis role=\"bold\">org.jboss.ejb.plugins.jms.JMSContainerInvoker</"
"emphasis>: The JMS specific factory."
msgstr ""
+"<emphasis role=\"bold\">org.jboss.ejb.plugins.jms.JMSContainerInvoker</"
+"emphasis>：JMS 专有的工厂。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:239
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">org.jboss.proxy.ejb.IORFactory</emphasis>: The RMI/"
"IIOP specific factory."
-msgstr "<emphasis role=\"bold\">file:/var/opt/apps/</emphasis>扫描指定的目录"
+msgstr ""
+"<emphasis role=\"bold\">org.jboss.proxy.ejb.IORFactory</emphasis>：RMI/"
+"IIOP 专有的工厂。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:246
@@ -685,6 +700,8 @@
"apply to each type of proxy factory. The child elements break down into the "
"three invocation protocols: RMI/RJMP, RMI/IIOP and JMS."
msgstr ""
+"<emphasis role=\"bold\">proxy-factory-config</emphasis>：<literal>proxy-"
+"factory-config</literal> 元素指定 <literal>proxy-factory</literal> 实现的其他信息。目前它只是元素的一个非结构化的集合。只有一些元素可以应用于代理工厂的每个类型。子元素根据 3 种调用协议进行划分：RMI/RJMP、RMI/IIOP 和 JMS。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:251
@@ -694,29 +711,29 @@
"ProxyFactory</literal> and <literal>org.jboss.proxy.ejb.ProxyFactoryHA</"
"literal> the following elements apply:"
msgstr ""
+"对于 RMI/JRMP 相关的代理工厂 <literal>org.jboss.proxy.ejb."
+"ProxyFactory</literal> 和 <literal>org.jboss.proxy.ejb.ProxyFactoryHA</"
+"literal>，使用下面的元素："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:256
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">client-interceptors</emphasis>: The <literal>client-"
"interceptors</literal> define the home, remote and optionally the multi-"
"valued proxy interceptor stacks."
msgstr ""
-"<emphasis role=\"bold\">PartitionObjectName</emphasis>：与代理关联的群集服务"
-"的 JMX <literal>ObjectName</literal>。"
+"<emphasis role=\"bold\">client-interceptors</emphasis>：<literal>client-"
+"interceptors</literal> 定义 home、remote 和多值的（multi-valued）代理拦截器栈。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:261 J2EE_EJBs_On_JBOSS.xml:275
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">web-class-loader</emphasis>: The web class loader "
"defines the instance of the <literal>org.jboss.web.WebClassLoader</literal> "
"that should be associated with the proxy for dynamic class loading."
-msgstr ""
-"<emphasis role=\"bold\">LoadBalancePolicy</emphasis>：与代理关联的 "
-"<literal>org.jboss.ha.framework.interfaces.LoadBalancePolicy</literal> 接口实"
-"现的类名。"
+msgstr "<emphasis role=\"bold\">web-class-loader</emphasis>：web 类加载器定义了应该和用于动态类加载的代理相关的 <literal>org.jboss.web.WebClassLoader</literal> 的实例。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:266
@@ -724,7 +741,7 @@
msgid ""
"The following <literal>proxy-factory-config</literal> is for an entity bean "
"accessed over RMI."
-msgstr ""
+msgstr "下面的 <literal>proxy-factory-config</literal> 用于通过 RMI 访问的 Enity Bean。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:269
@@ -837,44 +854,44 @@
"For the RMI/IIOP specific proxy factory, <literal>org.jboss.proxy.ejb."
"IORFactory</literal>, the following elements apply:"
msgstr ""
+"对于 RMI/IIOP 相关的代理工厂 <literal>org.jboss.proxy.ejb."
+"IORFactory</literal>，使用下面的元素："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:280
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">poa</emphasis>: The portable object adapter usage. "
"Valid values are <literal>per-servant</literal> and <literal>shared</"
"literal>."
msgstr ""
-"<emphasis role=\"strong\">例如：</emphasis> 建议在 <literal>0</literal> 到 "
-"<literal>3</literal> 之间取值"
+"<emphasis role=\"bold\">poa</emphasis>：可移植对象适配器（Portable Object Adapter）的用法。 其有效值为 <literal>per-servant</literal> 和 <literal>shared</"
+"literal>。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:285
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">register-ejbs-in-jnp-context</emphasis>: A flag "
"indicating if the EJBs should be register in JNDI."
-msgstr "<emphasis role=\"bold\">write-only</emphasis>：只写。"
+msgstr "<emphasis role=\"bold\">register-ejbs-in-jnp-context</emphasis>：指定 EJB 是否应该在 JNDI 里注册。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:290
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">jnp-context</emphasis>: The JNDI context in which to "
"register EJBs."
-msgstr "<emphasis role=\"bold\">JndiName</emphasis>：代理将被绑定的 JNDI 名。"
+msgstr "<emphasis role=\"bold\">jnp-context</emphasis>：EJB 所注册的 JNDI 上下文。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:295
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">interface-repository-supported</emphasis>: This "
"indicates whether or not a deployed EJB has its own CORBA interface "
"repository."
-msgstr ""
-"<emphasis role=\"bold\">disable_initial_coord</emphasis> 指定是否阻止这个节点"
-"成为群集控制点（cluster coordinator）。"
+msgstr "<emphasis role=\"bold\">interface-repository-supported</emphasis>：这指出部署的 EJB 是否有自己的 CORBA 接口库。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:300
@@ -882,7 +899,7 @@
msgid ""
"The following shows a <literal>proxy-factory-config</literal> for EJBs "
"accessed over IIOP."
-msgstr ""
+msgstr "下面展示了用于通过 IIOP 访问的 EJB 的 <literal>proxy-factory-config</literal>。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:303
@@ -913,27 +930,25 @@
"For the JMS specific proxy factory, <literal>org.jboss.ejb.plugins.jms."
"JMSContainerInvoker</literal>, the following elements apply:"
msgstr ""
+"对于 JMS 相关的代理工厂 <literal>org.jboss.ejb.plugins.jms."
+"JMSContainerInvoker</literal>，使用下面的元素："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:309
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">MinimumSize</emphasis>: This specifies the minimum "
"pool size for MDBs processing . This defaults to 1."
-msgstr ""
-"<emphasis role=\"bold\">MaxPoolSize</emphasis>：处理客户的服务器线程数量。它"
-"的缺省值是 300。"
+msgstr "<emphasis role=\"bold\">MinimumSize</emphasis>：指定 MDB 的最小进程池大小。缺省值为 1。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:314
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">MaximumSize</emphasis>: This specifies the upper "
"limit to the number of concurrent MDBs that will be allowed for the JMS "
"destination. This defaults to 15."
-msgstr ""
-"<emphasis role=\"bold\">MaxPoolSize</emphasis>：处理客户的服务器线程数量。它"
-"的缺省值是 300。"
+msgstr "<emphasis role=\"bold\">MaximumSize</emphasis>：指定 JMS 目的地允许的并行的 MDB 的数量的上限。缺省值为 15。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:319
@@ -950,18 +965,17 @@
"to 1. This value should not be modified from the default unless your JMS "
"provider indicates this is supported."
msgstr ""
+"<emphasis role=\"bold\">MaxMessages</emphasis>：指定 <literal>javax.jms."
+"QueueConnection</literal> 和 <literal>javax.jms.TopicConnection</literal> 接口的 <literal>createConnectionConsumer</literal> 方法的 <literal>maxMessages</literal> 参数的值，以及<literal>javax.jms.TopicConnection</literal> 的 <literal>createDurableConnectionConsumer</literal> 方法的 <literal>maxMessages</literal> 参数的值。这是可一次分配给服务器会话的消息的最大数目。除非你的 JMS 提供者提供支持，否则不要修改它的缺省值。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:324
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">KeepAliveMillis</emphasis>: This specifies the keep "
"alive time interval in milliseconds for sessions in the session pool. The "
"default is 30000 (30 seconds)."
-msgstr ""
-"<emphasis role=\"bold\">SnapshotInterval</emphasis>：它设置在 interval "
-"snapshot 模式下的 snapshot 的时间间隔，单位是毫秒。它的缺省值是 1000 毫秒，也"
-"就是 1 秒。"
+msgstr "<emphasis role=\"bold\">KeepAliveMillis</emphasis>：指定会话池里的会话的 keep alive 时间间隔。缺省值是 30000（30 秒）。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:329
@@ -969,27 +983,23 @@
msgid ""
"<emphasis role=\"bold\">MDBConfig</emphasis>: Configuration for the MDB JMS "
"connection behavior. Among the elements supported are:"
-msgstr ""
+msgstr "<emphasis role=\"bold\">MDBConfig</emphasis>：配置 MDB JMS 连接的行为。被支持的元素有："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:334
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ReconnectIntervalSec</emphasis>: The time to wait "
"(in seconds) before trying to recover the connection to the JMS server."
-msgstr ""
-"<emphasis role=\"bold\">ReplQueueInterval</emphasis> 指定复制复制队列里的元素"
-"所需的时间（毫秒数）。"
+msgstr "<emphasis role=\"bold\">ReconnectIntervalSec</emphasis>：试图恢复和 JMS 服务器的连接前等待的时间（秒）。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:339
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">DeliveryActive</emphasis>: Whether or not the MDB is "
"active at startup. The default is true."
-msgstr ""
-"<emphasis role=\"bold\">jnp.discoveryPort</emphasis>：接收发现查询的端口。缺"
-"省值为 1102。"
+msgstr "<emphasis role=\"bold\">DeliveryActive</emphasis>：指定这个 MDB 是否在启动时就进入活动状态。缺省值为 true。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:344
@@ -997,7 +1007,7 @@
msgid ""
"<emphasis role=\"bold\">DLQConfig</emphasis>: Configuration for an MDB's "
"dead letter queue, used when messages are redelivered too many times."
-msgstr ""
+msgstr "<emphasis role=\"bold\">DLQConfig</emphasis>：配置 MDB 的 dead letter 队列，在消息被重递送太多次数时使用。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:349
@@ -1007,7 +1017,7 @@
"the JMS provider adapter in the <literal>java:/</literal> namespace. This is "
"mandatory for an MDB and must implement <literal>org.jboss.jms.jndi."
"JMSProviderAdapter</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">JMSProviderAdapterJNDI</emphasis>：JMS 提供者适配器在 <literal>java:/</literal> 命名空间里的 JNDI 名称。对于 MDB 这是强制的，且必须实现<literal>org.jboss.jms.jndi.JMSProviderAdapter</literal>。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:354
@@ -1017,7 +1027,7 @@
"name of the session pool in the <literal>java:/</literal> namespace of the "
"JMS provider's session pool factory. This is mandatory for an MDB and "
"must implement <literal>org.jboss.jms.asf.ServerSessionPoolFactory</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ServerSessionPoolFactoryJNDI</emphasis>：JMS 提供者的会话池工厂里的会话池的基于 <literal>java:/</literal> 命名空间的 JNDI 名称。对于 MDB 这是强制的且必须实现 <literal>org.jboss.jms.asf.ServerSessionPoolFactory</literal>。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:361
@@ -1025,13 +1035,13 @@
msgid ""
"gives a sample <literal>proxy-factory-config</literal> fragment taken from "
"the <literal>standardjboss.xml</literal> descriptor."
-msgstr ""
+msgstr "给出了 <literal>standardjboss.xml</literal> 描述符里的一个 <literal>proxy-factory-config</literal> 片段示例。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:364
#, no-c-format
msgid "A sample JMSContainerInvoker proxy-factory-config"
-msgstr ""
+msgstr "JMSContainerInvoker 的 proxy-factory-config 示例"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:365
@@ -1095,7 +1105,7 @@
#: J2EE_EJBs_On_JBOSS.xml:372
#, no-c-format
msgid "The EJB Server Side View"
-msgstr ""
+msgstr "EJB 的服务器端视图"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:373
@@ -1104,13 +1114,13 @@
"Every EJB invocation must end up at a JBoss server hosted EJB container. In "
"this section we will look at how invocations are transported to the JBoss "
"server VM and find their way to the EJB container via the JMX bus."
-msgstr ""
+msgstr "每个 EJB 调用都必须在以 JBoss 服务器为宿主的 EJB 容器里结束。本节我们将看到这些调用是如何传输到 JBoss 服务器 VM 里并通过 JMX 总线进入 EJB 容器里的。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:377
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Detached Invokers - The Transport Middlemen"
-msgstr "脱管调用者引用"
+msgstr "脱管调用者 - 传输中介"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:378
@@ -1123,12 +1133,14 @@
"presented in <xref linkend=\"Detached_Invokers___The_Transport_Middlemen-"
"The_transport_invoker_server_side_architecture\"/>."
msgstr ""
+"在早前开放 MBean 服务的 RMI 兼容接口时，我们讨论了脱管调用者的架构。在这里我们将看看怎样使用脱管调用者来为客户开放 EJB 容器的 home 和 bean 接口。<xref linkend=\"Detached_Invokers___The_Transport_Middlemen-"
+"The_transport_invoker_server_side_architecture\"/> 体现了调用者架构的通用视图。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:382
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The transport invoker server side architecture"
-msgstr "The main components in the detached invoker architecture"
+msgstr "传输调用者的服务器端架构"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:389
@@ -1144,6 +1156,9 @@
"<literal>invoker-bindings</literal> specify one or more invokers to use with "
"the EJB container MBean."
msgstr ""
+"对于每种类型的 home 代理都有一个与调用者的綁定以及相关联的传输协议。容器可能同时有多个活动的调用协议。在 <literal>jboss.xml</literal> 文件里，<literal>invoker-proxy-binding-name</literal> 匹配 <literal>invoker-"
+"proxy-binding/name</literal> 元素。对于 <literal>container-"
+"configuration</literal> 级别而言，这指定了将用于部署在容器里的 EJB 的缺省调用者。从 bean 级别来说，<literal>invoker-bindings</literal> 指定了一个或多个和 EJB 容器 MBean 一起使用的调用者。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:392
@@ -1161,6 +1176,8 @@
"<literal>ejb-ref</literal> to the home proxy binding for <literal>ejb-ref</"
"literal> target EJB home that matches the referencing invoker type."
msgstr ""
+"当为给定的 EJB 部署指定多个调用者时，home 代理必须赋予一个唯一的 JNDI 綁定位置。这是通过 <literal>invoker/jndi-name</literal> 元素指定的。有多个调用者存在时产生的另外一个问题是，如何处理远程 home 接口或 EJB 调用其他 bean 时获得的接口。任何这样的接口都需要使用和调用外部 EJB 相同的调用者来使远程 home 和接口和客户初始化这个调用所用的代理相兼容。<literal>invoker/ejb-ref</"
+"literal> 元素允许你把独立于协议的 ENC <literal>ejb-ref</literal> 映射到符合引用调用者类型的 <literal>ejb-ref</literal> target EJB home 的 home 代理綁定。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:395
@@ -1171,7 +1188,7 @@
"<literal>org.jboss.test.jrmp</literal> package of the testsuite. The "
"following example illustrates the custom <literal>JRMPInvoker</literal> "
"configuration and its mapping to a stateless session bean."
-msgstr ""
+msgstr "在 Testsuite 的 <literal>org.jboss.test.jrmp</literal> 软件包里你可以找到一个使用启用压缩套接字的自定义的 <literal>JRMPInvoker</literal> MBean 的示例。下面的例子演示了自定义的 <literal>JRMPInvoker</literal> 配置及其到一个 stateless session bean 的映射。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:398
@@ -1224,7 +1241,7 @@
"Here the default <literal>JRMPInvoker</literal> has been customized to bind "
"to port 4445 and to use custom socket factories that enable compression at "
"the transport level."
-msgstr ""
+msgstr "缺省的 <literal>JRMPInvoker</literal> 在这里已经自定义为綁定端口 4445 且使用自定义的在传输层启用压缩的套接字工厂。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:402
@@ -1373,6 +1390,10 @@
"compression-invoker</literal> is linked to the custom JRMP invoker we just "
"declared."
msgstr ""
+"<literal>StatelessSession</literal> EJB <literal>invoker-bindings</"
+"literal> 设置指定 <literal>stateless-compression-invoker</"
+"literal> 将和綁定在 JNDI 名称 <literal>jrmp-compressed/StatelessSession</literal> 下的 home 接口一起使用。<literal>stateless-"
+"compression-invoker</literal> 链接至我们刚才声明的自定义 JRMP 调用者。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:406
@@ -1381,7 +1402,7 @@
"The following example, <literal>org.jboss.test.hello</literal> testsuite "
"package, is an example of using the <literal>HttpInvoker</literal> to "
"configure a stateless session bean to use the RMI/HTTP protocol."
-msgstr ""
+msgstr "下面的例子，<literal>org.jboss.test.hello</literal> testsuite 软件包，是一个用 <literal>HttpInvoker</literal> 来配置使用 RMI/HTTP 协议的 stateless session bean 的例子。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:409
@@ -1520,6 +1541,8 @@
"found in the <literal>http-invoker.sar/META-INF/jboss-service.xml</literal> "
"descriptor, and its service descriptor fragment is show here:"
msgstr ""
+"在这里定义了一个名为 <literal>stateless-http-invoker</"
+"literal> 的自定义的 invoker-proxy-binding。它把 <literal>HttpInvoker</literal> MBean 用作脱管调用者。在 <literal>http-invoker.sar/META-INF/jboss-service.xml</literal> 描述符里找到的 <literal>jboss:service=invoker,type=http</literal> 是 <literal>HttpInvoker</literal> MBean 的缺省名称，下面是它的服务描述符片段："
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:413
@@ -1563,14 +1586,12 @@
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:414
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The client proxy posts the EJB invocation content to the "
"<literal>EJBInvokerServlet</literal> URL specified in the "
"<literal>HttpInvoker</literal> service configuration."
-msgstr ""
-"和 JNDI/HTTP 相关的 <literal>InvokerServlet</literal> 的配置是 "
-"<literal>JMXInvokerServlet</literal>，它定义了："
+msgstr "客户代理把 EJB 调用内容发送给 <literal>HttpInvoker</literal> 服务配置里指定的 <literal>EJBInvokerServlet</literal> URL。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:420
@@ -1580,7 +1601,7 @@
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:421
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>org.jboss.invocation.jrmp.server.JRMPInvokerHA</literal> "
"service is an extension of the <literal>JRMPInvoker</literal> that is a "
@@ -1590,12 +1611,7 @@
"available to clustered RMI/JRMP as well. For additional information on the "
"clustering architecture and the implementation of the HA RMI proxies see the "
"JBoss Clustering docs."
-msgstr ""
-"<literal>org.jboss.proxy.generic.ProxyFactoryHA</literal> 服务是 cluster-"
-"aware factory <literal>ProxyFactoryHA</literal> 的一个扩展。"
-"<literal>ProxyFactoryHA</literal> 完全支持 <literal>JRMPProxyFactory</"
-"literal> 的所有属性。这意味着对端口，接口和套接字传输的自定义绑定，对于群集"
-"的 RMI/JRMP 也是可用的。此外，下面的与群集相关的属性也被支持："
+msgstr "<literal>org.jboss.invocation.jrmp.server.JRMPInvokerHA</literal> 服务是可检测群集的 <literal>JRMPInvoker</literal> 的扩展。<literal>JRMPInvokerHA</literal> 完全支持<literal>JRMPInvoker</literal> 的所有属性。这表示自定义的端口綁定、接口和套接字传输都对于群集的 RMI/JRMP 可用。关于群集架构和 HA RMI 代理实现的其他信息，请参考相关的 JBoss 群集的文档。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:427
@@ -1605,17 +1621,15 @@
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:428
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The RMI/HTTP layer allows for software load balancing of the invocations in "
"a clustered environment. An HA capable extension of the HTTP invoker has "
"been added that borrows much of its functionality from the HA-RMI/JRMP "
"clustering."
msgstr ""
-"RMI/HTTP 层允许群集环境里的调用的负载平衡。HTTP 调用者的具备 HA 能力的扩展借"
-"用了 HA-RMI/JRMP 群集里的大部分功能。要启用 HA-RMI/HTTP，你需要配置 EJB 容器"
-"的调用者。这可以通过 <literal>jboss.xml</literal> 描述符或 "
-"<literal>standardjboss.xml</literal> 描述符来完成。"
+"RMI/HTTP 层允许群集环境里的调用的负载平衡。添加的 HTTP 调用者的具备 HA 能力的扩展借"
+"用了 HA-RMI/JRMP 群集里的大部分功能。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:431
@@ -1629,12 +1643,16 @@
"of a stateless session configuration taken from the <literal>org.jboss.test."
"hello</literal> testsuite package."
msgstr ""
+"要启用 HA-RMI/HTTP，你需要配置 EJB 容器的调用者。这可以通过 <literal>jboss.xml</literal> 或 <literal>standardjboss.xml</literal> 描述符来实现。<xref "
+"linkend=\"The_HA_HttpInvoker___Clustered_RMIHTTP_Transport-A_jboss."
+"xml_stateless_session_configuration_for_HA_RMIHTTP\"/> 展示了 <literal>org.jboss.test."
+"hello</literal> testsuite 软件包里的一个 stateless session 配置的例子。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:434
#, no-c-format
msgid "A jboss.xml stateless session configuration for HA-RMI/HTTP"
-msgstr ""
+msgstr "jboss.xml 关于使用 HA-RMI/HTTP 的 stateless session 的配置"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:435
@@ -1759,7 +1777,7 @@
"The <literal>stateless-httpHA-invoker</literal> invoker-proxy-binding "
"references the <literal>jboss:service=invoker,type=httpHA</literal> invoker "
"service. This service would be configured as shown below."
-msgstr ""
+msgstr "<literal>stateless-httpHA-invoker</literal> invoker-proxy-binding 引用 <literal>jboss:service=invoker,type=httpHA</literal> 调用者服务。这个服务将依如下进行配置。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:439
@@ -1811,12 +1829,14 @@
"collection of candidate http URLs that are made available to the client side "
"proxy for failover and/or load balancing."
msgstr ""
+"调用者代理所使用的 URL 是部署在群集节点上的 <literal>EJBInvokerHAServlet</"
+"literal> 映射。跨群集的 <literal>HttpInvokerHA</literal> 实例组成了一个候选 http URL 的集合，可用于客户端代理的失效切换和/或负载平衡。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:448
#, no-c-format
msgid "The EJB Container"
-msgstr ""
+msgstr "EJB 容器"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:449
@@ -1829,12 +1849,15 @@
"literal> and the creation of the container instance is managed by the "
"<literal>EJBDeployer</literal> MBean."
msgstr ""
+"EJB 容器是管理特殊 EJB 类的组件。在 JBoss 里有一个 <literal>org.jboss.ejb.Container</"
+"literal> 实例，它为每个部署的 EJB 的唯一配置而创建。初始化的实际对象是 <literal>Container</"
+"literal> 的子类，<literal>EJBDeployer</literal> MBean 管理对容器实例的创建。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:453
-#, fuzzy, no-c-format
+#, no-c-format
msgid "EJBDeployer MBean"
-msgstr "The SARDeployer MBean"
+msgstr "EJBDeployer MBean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:454
@@ -1845,7 +1868,7 @@
"deployment, the <literal>EJBDeployer</literal> will create and initialize "
"the necessary EJB containers, one for each type of EJB. The configurable "
"attributes of the <literal>EJBDeployer</literal> are:"
-msgstr ""
+msgstr "<literal>org.jboss.ejb.EJBDeployer</literal> MBean 负责 EJB 容器的创建。如果准备部署 EJB JAR，<literal>EJBDeployer</literal> 将为每个 EJB 类型创建并初始化一个必需的 EJB 容器。<literal>EJBDeployer</literal> 的可配置属性是："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:459
@@ -1855,7 +1878,7 @@
"indicating if the EJB verifier should be run. This validates that the EJBs "
"in a deployment unit conform to the EJB 2.1 specification. Setting this to "
"true is useful for ensuring your deployments are valid."
-msgstr ""
+msgstr "<emphasis role=\"bold\">VerifyDeployments</emphasis>：指定是否运行 EJB verifier 的布尔值标记。 这可以检验部署的 EJB 是否符合 EJB 2.1 规格。将其设置为 true 对于保证部署的有效性是很有用的。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:464
@@ -1864,7 +1887,7 @@
"<emphasis role=\"bold\">VerifierVerbose</emphasis>: A boolean that controls "
"the verboseness of any verification failures/warnings that result from the "
"verification process."
-msgstr ""
+msgstr "<emphasis role=\"bold\">VerifierVerbose</emphasis>：这是一个布尔值，它控制验证过程中的任何验证失败/警告信息的冗余模式。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:469
@@ -1873,17 +1896,15 @@
"<emphasis role=\"bold\">StrictVerifier</emphasis>: A boolean that enables/"
"disables strict verification. When strict verification is enable an EJB will "
"deploy only if verifier reports no errors."
-msgstr ""
+msgstr "<emphasis role=\"bold\">StrictVerifier</emphasis>：启用/禁用严格验证（strict verification）的布尔值标记。如启用了严格验证，EJB 只有在 verifier 没有报告错误时才可以部署。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:474
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">CallByValue</emphasis>: a boolean flag that "
"indicates call by value semantics should be used by default."
-msgstr ""
-"<emphasis role=\"bold\">DiscoveryDisabled</emphasis> 是一个布尔值标记，它可用"
-"来取消自动恢复多点传送侦听者（multicast listener）的配置。"
+msgstr "<emphasis role=\"bold\">CallByValue</emphasis>：这是一个布尔值标记，它指出在缺省情况下应该使用值调用（call by value）模式。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:479
@@ -1894,7 +1915,7 @@
"literal> descriptors should be validated against their declared DTDs. "
"Setting this to true is useful for ensuring your deployment descriptors are "
"valid."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ValidateDTDs</emphasis>：这是一个布尔值标记，它指出 <literal>ejb-jar.xml</literal> 和 <literal>jboss.xml</literal> 描述符是否针对其声明的 DTD 进行校验。设置为 true 对于保证部署描述符的有效性很有用处。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:484
@@ -1906,18 +1927,16 @@
"configuration. This allows one to define a container interceptor "
"configuration that includes metrics type interceptors that can be toggled on "
"and off."
-msgstr ""
+msgstr "<emphasis role=\"bold\">MetricsEnabled</emphasis>：这是一个布尔值标记，它控制标记为 <literal>metricsEnabled=true</literal> 的容器拦截器是否应该包括在配置里。这允许你定义一个包括可打开和关闭的 metrice type 拦截器的容器拦截器配置。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:489
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">WebServiceName</emphasis>: The JMX ObjectName string "
"of the web service MBean that provides support for the dynamic class loading "
"of EJB classes."
-msgstr ""
-"<emphasis role=\"bold\">PartitionObjectName</emphasis>：与代理关联的群集服务"
-"的 JMX <literal>ObjectName</literal>。"
+msgstr "<emphasis role=\"bold\">WebServiceName</emphasis>：提供对 EJB 类的动态类加载支持的 web 服务器 MBean 的 JMX ObjectName 字符串。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:494
@@ -1928,6 +1947,8 @@
"attribute named <literal>TransactionManager</literal> that returns that "
"<literal>javax.transaction.TransactionManager</literal> instance."
msgstr ""
+"<emphasis role=\"bold\">TransactionManagerServiceName</emphasis>：JTA 事务管理者服务的 JMX "
+"ObjectName 字符串。它必须有一个名为 <literal>TransactionManager</literal> 且返回<literal>javax.transaction.TransactionManager</literal> 实例的属性。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:499
@@ -1942,7 +1963,7 @@
"JBoss has support for full re-deployment of both implementation and "
"interface classes, and will reload any changed classes. This will allow you "
"to develop and update EJBs without ever stopping a running server."
-msgstr ""
+msgstr "部署这包含两个核心方法：deploy 和 undeploy。deploy 方法使用指向 EJB JAR 或结构和有效 EJB JAR 相同（这便于部署）的目录的 URL。一旦部署已经完成，它可以在同一 URL 上调用 undeploy 进行卸载。对已部署的 URL 调用 deploy 将导致先卸载、然后重新部署这个 URL。JBoss 支持对实现和接口类的完全重部署，并将重新加载任何有改动的类。这允许你开发和更新 EJB 而不需要停止正运行的服务器。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:502
@@ -1953,13 +1974,13 @@
"a container for each unique EJB, initialize the container with the "
"deployment configuration information. We will talk about each function in "
"the following sections."
-msgstr ""
+msgstr "在 EJB JAR 的部署过程中，<literal>EJBDeployer</literal> 及其相关联的类执行 3 个主要功能：验证 EJB、为每个唯一的 EJB 类型创建容器、用部署配置信息初始化容器。我们将在后续章节里讨论这些功能。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:506
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Verifying EJB deployments"
-msgstr "Farming 部署"
+msgstr "验证 EJB 部署"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:507
@@ -1977,7 +1998,7 @@
"to construct a proper EJB JAR, and it is easy to make a mistake. The "
"verification stage attempts to catch any errors and fail the deployment with "
"an error that indicates what needs to be corrected."
-msgstr ""
+msgstr "当 <literal>EJBDeployer</literal> 的 <literal>VerifyDeployments</literal> 属性为 true 时，部署这将执行对 EJB 的验证。这种验证将检查 EJB 是否符合 EJB 规格。它验证 EBJB 部署单元是否包含必需的 home 和 remote、local home 和 local 接口。它也将检查出现在这些接口里的对象的类型是否正确、在实现类里是否具有必需的方法。既然 EJB 开发者和部署者必须正确执行许多步骤来构建正确的 EJB JAR 文件，而且容器出错，这种验证就是很有用的行为，缺省将被启用。验证阶段试图捕获任何错误、停止部署过程并指出需要修改的地方。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:510
@@ -1992,13 +2013,13 @@
"interfaces, deployment descriptors and related objects. See the XDoclet home "
"page, <ulink url=\"http://sourceforge.net/projects/xdoclet\"></ulink> for "
"additional details."
-msgstr ""
+msgstr "可能编写 EJB 最容器出现问题的是 bean 实现及其 remote 和 home 接口、以及部署描述符的脱节。这些独立的元素不同步很容易出现。XDoclet 是帮助消除这些问题的工具。它允许你在 EJB Bean 实现类里使用自定义的类似 JavaDoc 风格的标记来产生相关的 bean 接口、部署描述符和相关的对象。更多细节请参考 XDoclet 的主页：<ulink url=\"http://sourceforge.net/projects/xdoclet\"></ulink>。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:516
#, no-c-format
msgid "Deploying EJBs Into Containers"
-msgstr ""
+msgstr "在容器里部署 EJB"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:517
@@ -2010,7 +2031,7 @@
"JAR, and extracting the bean classes and their metadata as described by the "
"<literal>ejb-jar.xml</literal> and <literal>jboss.xml</literal> deployment "
"descriptors. For each EJB in the EJB JAR, the following steps are performed:"
-msgstr ""
+msgstr "<literal>EJBDeployer</literal> 所扮演的最重要的角色是创建 EJB 容器并把 EJB 部署在容器里。部署阶段由在 EJB JAR 里迭代 EJB 和根据 <literal>ejb-jar.xml</literal> 和 <literal>jboss.xml</literal>描述符抽取 bean 类及其元数据组成。对于 EJB JAR 里的每一个 EJB，都会执行下面的步骤："
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:522
@@ -2023,6 +2044,8 @@
"<literal>ClassLoader</literal> is also used to isolate the standard "
"<literal>java:comp</literal> JNDI namespace from other J2EE components."
msgstr ""
+"按照 EJB 的类型（stateless、stateful、BMP entity、CMP entity 或 message "
+"driven）创建 <literal>org.jboss.ejb.Container</literal> 的子类。容器被分配一个唯一的可加载本地资源的 <literal>ClassLoader</literal>。<literal>ClassLoader</literal> 的唯一性也被用来区别标准的 <literal>java:comp</literal> JNDI 命名空间和其他 J2EE 组件。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:527
@@ -2031,12 +2054,14 @@
"Set all container configurable attributes from a merge of the <literal>jboss."
"xml</literal> and <literal>standardjboss.xml</literal> descriptors."
msgstr ""
+"在 <literal>jboss."
+"xml</literal> 和 <literal>standardjboss.xml</literal> 描述符里设置容器的所有可配置属性。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:532
#, no-c-format
msgid "Create and add the container interceptors as configured for the container."
-msgstr ""
+msgstr "创建和添加为容器配置的拦截器。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:537
@@ -2045,7 +2070,7 @@
"Associate the container with an application object. This application object "
"represents a J2EE enterprise application and may contain multiple EJBs and "
"web contexts."
-msgstr ""
+msgstr "将容器和应用程序对象进行关联。应用程序对象代表 J2EE 企业级应用程序且可能包含多个 EJB 和 web 上下文。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:542
@@ -2055,13 +2080,13 @@
"turn starts all containers and makes the EJBs available to clients. If any "
"EJB fails to deploy, a deployment exception is thrown and the deployment "
"module is failed."
-msgstr ""
+msgstr "如果所有的 EJB 都成功地进行了部署，应用程序将被启动，且按顺序启动所有容器并使 EJB 可用于客户。如果任何 EJB 的部署没有成功，部署异常将被抛出且部署模块将停止。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:548
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Container configuration information"
-msgstr "其他配置选项"
+msgstr "容器配置信息"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:549
@@ -2073,12 +2098,14 @@
"<xref linkend=\"Container_configuration_information-"
"The_jboss_4_0_DTD_elements_related_to_container_configuration.\"/>."
msgstr ""
+"JBoss 用一个符合 <literal>jboss_4_0.dtd</literal> 的 XML 文件具体化了大多数（如果不是所有）的 EJB 容器的设置。<xref linkend=\"Container_configuration_information-"
+"The_jboss_4_0_DTD_elements_related_to_container_configuration.\"/> 展示了和容器配置信息相关的 DTD 部分。"
#. Tag: title
#: J2EE_EJBs_On_JBOSS.xml:553
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The jboss_4_0 DTD elements related to container configuration."
-msgstr "这个文件提供了缺省的容器配置。"
+msgstr "和容器配置相关的 jboss_4_0 DTD 元素。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:560
@@ -2096,7 +2123,7 @@
"located in the conf directory of any configuration file set that uses EJBs. "
"The following is a sample of <literal>container-configuration</literal> from "
"<literal>standardjboss.xml</literal>."
-msgstr ""
+msgstr "<literal>container-configuration</literal> 元素及其子元素为 <literal>container-name</literal> 元素给定的容器类型指定了容器配置设定。每个配置都指定如缺省的调用者类型、容器拦截器结构、实例缓冲/池及其大小、持久化管理者、安全性等信息。因为许多信息都要求对 JBoss 容器结构有详细的了解，JBoss 带有用于 4 个 EJB 类型的标准配置。这个配置文件名是 <literal>standardjboss.xml</literal>，它位于任何使用 EJB 的配置文件集的 conf 目录下。下面是 <literal>standardjboss.xml</literal> 里的一个 <literal>container-configuration</literal> 元素示例。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:563
@@ -2398,18 +2425,20 @@
"container-managed persistence entity version 2.0 = Standard CMP 2.x "
"EntityBean"
msgstr ""
+"container-managed persistence entity version 2.0 = Standard CMP 2.x "
+"EntityBean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:584
#, no-c-format
msgid "container-managed persistence entity version 1.1 = Standard CMP EntityBean"
-msgstr ""
+msgstr "container-managed persistence entity version 1.1 = Standard CMP EntityBean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:589
#, no-c-format
msgid "bean-managed persistence entity = Standard BMP EntityBean"
-msgstr ""
+msgstr "bean-managed persistence entity = Standard BMP EntityBean"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:594
More information about the jboss-cvs-commits
mailing list