[jboss-cvs] JBossAS SVN: r90873 - 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
Tue Jul 7 01:55:02 EDT 2009
Author: xhuang at jboss.com
Date: 2009-07-07 01:55:02 -0400 (Tue, 07 Jul 2009)
New Revision: 90873
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-07 05:24:32 UTC (rev 90872)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_EJBs_On_JBOSS.po 2009-07-07 05:55:02 UTC (rev 90873)
@@ -9,7 +9,7 @@
"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-02 15:19+1000\n"
+"PO-Revision-Date: 2009-07-07 15:53+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -451,6 +451,10 @@
"<literal>jboss:service=invoker,type=jrmp</literal>, the "
"<literal>JRMPInvoker</literal> service."
msgstr ""
+"<emphasis role=\"bold\">org.jboss.invocation.InvokerInterceptor</emphasis>：封装对传输专有调用者的方法调用的调度。如果客户在和服务器相同的 VM 里执行，它将通过 by reference 调用者优选调用路径。当客户在服务器 VM 外部执行时，拦截器把调用委托给和调用上下文相关联的传输调用者。在使用 <xref linkend="
+"\"The_EJB_Client_Side_View-"
+"The_client_interceptors_from_the_Standard_Stateless_SessionBean_configuration."
+"\"/> 里的配置时，这会是和 <literal>jboss:service=invoker,type=jrmp</literal> 相关联的调用者 stub： <literal>JRMPInvoker</literal> 服务。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:126
@@ -461,12 +465,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>，不对 in-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
@@ -480,23 +486,23 @@
"<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 descriptor</literal> 或服务器的 <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>：用于 Entity 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>：用于群集 Entity Bean 的 RMI/JRMP 配置"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:148
@@ -585,18 +591,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
@@ -609,19 +619,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> 元素给出代理调用者将关联的脱管调用者 MBean 服务的 JMX <literal>ObjectName</literal> 字符串。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:219
@@ -635,14 +645,17 @@
"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
@@ -650,7 +663,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
@@ -659,14 +672,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
@@ -679,6 +696,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
@@ -688,29 +707,30 @@
"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-class-loader 元素定义应该和用于动态类加载关联的 <literal>org.jboss.web.WebClassLoader</literal> 实例。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:266
@@ -718,11 +738,11 @@
msgid ""
"The following <literal>proxy-factory-config</literal> is for an entity bean "
"accessed over RMI."
-msgstr ""
+msgstr "下面的 <literal>proxy-factory-config</literal> 用于通过 RMI 访问的 Entity Bean。"
#. Tag: programlisting
#: J2EE_EJBs_On_JBOSS.xml:269
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<proxy-factory-config>\n"
" <client-interceptors>\n"
@@ -771,68 +791,52 @@
" </client-interceptors>\n"
"</proxy-factory-config>"
msgstr ""
-"<jboss>\n"
-" <session>\n"
-" <ejb-name>nextgen_RetryInterceptorStatelessSession</ejb-"
-"name>\n"
-" <invoker-bindings>\n"
-" <invoker>\n"
-" <invoker-proxy-binding-name>\n"
-" clustered-retry-stateless-rmi-invoker\n"
-" </invoker-proxy-binding-name>\n"
-" <jndi-name>\n"
-" nextgen_RetryInterceptorStatelessSession\n"
-" </jndi-name>\n"
-" </invoker>\n"
-" </invoker-bindings>\n"
-" <clustered>true</clustered>\n"
-" </session>\n"
-"\n"
-" <invoker-proxy-binding>\n"
-" <name>clustered-retry-stateless-rmi-invoker</name>\n"
-" <invoker-mbean>jboss:service=invoker,type=jrmpha</invoker-"
-"mbean>\n"
-" <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-"
-"factory>\n"
-" <proxy-factory-config>\n"
-" <client-interceptors>\n"
-" <home>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.HomeInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.SecurityInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.TransactionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.RetryInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.invocation.InvokerInterceptor\n"
-" </interceptor>\n"
-" </home>\n"
-" <bean>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.StatelessSessionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.SecurityInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.TransactionInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.proxy.ejb.RetryInterceptor\n"
-" </interceptor>\n"
-" <interceptor>\n"
-" org.jboss.invocation.InvokerInterceptor\n"
-" </interceptor>\n"
-" </bean>\n"
-" </client-interceptors>\n"
-" </proxy-factory-config>\n"
-" </invoker-proxy-binding>"
+"<proxy-factory-config>\n"
+" <client-interceptors>\n"
+" <home>\n"
+" <interceptor>org.jboss.proxy.ejb.HomeInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.proxy.SecurityInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.proxy.TransactionInterceptor</"
+"interceptor>\n"
+" <interceptor call-by-value=\"false\">\n"
+" org.jboss.invocation.InvokerInterceptor\n"
+" </interceptor>\n"
+" <interceptor call-by-value=\"true\">\n"
+" org.jboss.invocation.MarshallingInvokerInterceptor\n"
+" </interceptor>\n"
+" </home>\n"
+" <bean>\n"
+" <interceptor>org.jboss.proxy.ejb.EntityInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.proxy.SecurityInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.proxy.TransactionInterceptor</"
+"interceptor>\n"
+" <interceptor call-by-value=\"false\">\n"
+" org.jboss.invocation.InvokerInterceptor\n"
+" </interceptor>\n"
+" <interceptor call-by-value=\"true\">\n"
+" org.jboss.invocation.MarshallingInvokerInterceptor\n"
+" </interceptor>\n"
+" </bean>\n"
+" <list-entity>\n"
+" <interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.proxy.SecurityInterceptor</"
+"interceptor>\n"
+" <interceptor>org.jboss.proxy.TransactionInterceptor</"
+"interceptor>\n"
+" <interceptor call-by-value=\"false\">\n"
+" org.jboss.invocation.InvokerInterceptor\n"
+" </interceptor>\n"
+" <interceptor call-by-value=\"true\">\n"
+" org.jboss.invocation.MarshallingInvokerInterceptor\n"
+" </interceptor>\n"
+" </list-entity>\n"
+" </client-interceptors>\n"
+"</proxy-factory-config>"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:270
@@ -841,44 +845,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=\"bold\">prefix</emphasis>：这是每个日志文件名的前缀。它的缺省"
-"值是 <literal>access_log</literal>。"
+"<emphasis role=\"bold\">poa</emphasis>：可移植对象适配器的用法。有效值为 <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
@@ -886,7 +890,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
@@ -900,6 +904,13 @@
" <jnp-context>iiop</jnp-context>\n"
"</proxy-factory-config>"
msgstr ""
+"<proxy-factory-config>\n"
+" <web-class-loader>org.jboss.iiop.WebCL</web-class-loader>\n"
+" <poa>per-servant</poa>\n"
+" <register-ejbs-in-jnp-context>true</register-ejbs-in-jnp-"
+"context>\n"
+" <jnp-context>iiop</jnp-context>\n"
+"</proxy-factory-config>"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:304
@@ -908,27 +919,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
@@ -945,18 +954,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> 参数值。它是可一次分配给服务器会话的最大消息数目。缺省为 1。这个值不应该被修改，除非你的 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>：指定会话池里的会话保持活动状态的时间间隔（毫秒）。缺省值为 30000（30 秒）。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:329
@@ -964,27 +972,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
@@ -992,7 +996,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
@@ -1003,6 +1007,8 @@
"mandatory for an MDB and must implement <literal>org.jboss.jms.jndi."
"JMSProviderAdapter</literal>."
msgstr ""
+"<emphasis role=\"bold\">JMSProviderAdapterJNDI</emphasis>：<literal>java:/</literal> 命名空间里的 JMS 提供者适配器的 JNDI 名称。对于 MDB 来说这是强制的且必须实现 <literal>org.jboss.jms.jndi."
+"JMSProviderAdapter</literal>。"
#. Tag: para
#: J2EE_EJBs_On_JBOSS.xml:354
@@ -1012,7 +1018,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
@@ -1020,13 +1026,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
@@ -1051,12 +1057,30 @@
" </MDBConfig>\n"
"</proxy-factory-config>"
msgstr ""
+"<proxy-factory-config>\n"
+" <JMSProviderAdapterJNDI>DefaultJMSProvider</"
+"JMSProviderAdapterJNDI>\n"
+" <ServerSessionPoolFactoryJNDI>StdJMSPool</"
+"ServerSessionPoolFactoryJNDI>\n"
+" <MinimumSize>1</MinimumSize>\n"
+" <MaximumSize>15</MaximumSize>\n"
+" <KeepAliveMillis>30000</KeepAliveMillis>\n"
+" <MaxMessages>1</MaxMessages>\n"
+" <MDBConfig>\n"
+" <ReconnectIntervalSec>10</ReconnectIntervalSec>\n"
+" <DLQConfig>\n"
+" <DestinationQueue>queue/DLQ</DestinationQueue>\n"
+" <MaxTimesRedelivered>10</MaxTimesRedelivered>\n"
+" <TimeToLive>0</TimeToLive>\n"
+" </DLQConfig>\n"
+" </MDBConfig>\n"
+"</proxy-factory-config>"
#. Tag: title
#: 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
@@ -1065,13 +1089,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
More information about the jboss-cvs-commits
mailing list