[jboss-cvs] JBossAS SVN: r69920 - 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 Feb 19 00:00:07 EST 2008
Author: xhuang at jboss.com
Date: 2008-02-19 00:00:07 -0500 (Tue, 19 Feb 2008)
New Revision: 69920
Modified:
projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po
Log:
update
Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po 2008-02-19 00:16:58 UTC (rev 69919)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po 2008-02-19 05:00:07 UTC (rev 69920)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Messaging_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-11-05 06:03+0000\n"
-"PO-Revision-Date: 2008-02-18 16:35+1000\n"
+"PO-Revision-Date: 2008-02-19 14:38+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <zh at li.org>\n"
"MIME-Version: 1.0\n"
@@ -2281,7 +2281,7 @@
"JNDI tree. Clients choose the protocol they wish to use by the JNDI location "
"used to obtain the JMS connection factory. JBossMQ currently has several "
"different invocation layers."
-msgstr ""
+msgstr "每个 IL 服务都把一个 JMS 连接工厂绑定到 JNDI 树的一个特殊位置上。客户端通过 JNDI 位置选择协议来获取 JMS 连接工厂。JBossMQ 目前有几个不同的调用层服务。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:186
@@ -2297,7 +2297,7 @@
"message at the socket level, the UIL2 protocol uses true asynchronous send "
"and receive messaging at the transport level, providing for improved "
"throughput and utilization."
-msgstr ""
+msgstr "<emphasis role=\"bold\">UIL2 IL</emphasis>：统一调用层版本 2（UIL2）是用于远程消息的首选调用层服务。多路复用层被用来提供双向通信。多路复用层为每个物理套接字创建两个虚拟套接字。这允许和由于防火墙或其他限制而不能使用服务器创建的连接的客户端进行通信。不象在套接字级别使用阻塞往返（blocking round-trip）消息的旧的 UIL 调用层，UIL2 协议在传输层级别使用真正的异步消息发送和接收，这提高了吞吐量和利用率。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:191
@@ -2312,6 +2312,8 @@
"Driven Beans (MDB) or any other component that runs in the same virtual "
"machine as the server such as servlets, MBeans, or EJBs."
msgstr ""
+"<emphasis role=\"bold\">JVM IL</emphasis>：当 JMS 客户端和服务器运行在相同的虚拟机里时，Java 虚拟机（JVM）调用层用来减少 TCI/IP 负荷。这个 IL 使用直接调用服务器的方法来处理客户端的请求。因为不需要创建套接字且不需要关联的工作线程，这提高了效率。Message "
+"Driven Beans (MDB) 或其他任何和服务器运行在相同虚拟机里的组件（如 servlet、MBean 或 EJB）都应该使用这种 IL。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:196
@@ -2324,12 +2326,14 @@
"for access to JMS through a firewall when the only port allowed requires "
"HTTP."
msgstr ""
+"<emphasis role=\"bold\">HTTP IL</emphasis>：HTTP 调用层（HTTPIL）允许通过 HTTP 或 HTTPS 协议访问 JBossMQ 服务。这种 IL 依赖部署在 <literal>deploy/jms/"
+"jbossmq-httpil.sar</literal> 里的 servlet 来处理 HTTP 请求。对于通过仅允许 HTTP 端口的防火墙访问 JMS，这很有用处。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:204
#, no-c-format
msgid "Security Manager"
-msgstr ""
+msgstr "Security Manager（安全管理者）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:205
@@ -2338,13 +2342,13 @@
"The JBossMQ <literal>SecurityManager</literal> is the service that enforces "
"an access control list to guard access to your destinations. This subsystem "
"works closely with the <literal>StateManager</literal> service."
-msgstr ""
+msgstr "JBossMQ <literal>SecurityManager</literal> 是通过访问控制列表来保护对目的地的访问的服务。这个子系统和 <literal>StateManager</literal> 服务密切相关。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:211
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Destination Manager"
-msgstr "JNDI 绑定管理者(Binding Manager)"
+msgstr "目的地管理者（Destination Manager）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:212
@@ -2356,12 +2360,14 @@
"such as the <literal>MessageCache</literal>, <literal>StateManager</"
"literal>, and <literal>PersistenceManager</literal>."
msgstr ""
+"<literal>DestinationManager</literal> 可以被认作 JBossMQ 里的中心服务。它记录服务器里所有创建的目的地。它也了解其他关键服务，如 <literal>MessageCache</literal>、<literal>StateManager</"
+"literal> 和 <literal>PersistenceManager</literal>。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:218
#, no-c-format
msgid "Message Cache"
-msgstr ""
+msgstr "Message Cache（消息缓存）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:219
@@ -2376,13 +2382,13 @@
"moving those messages from memory to persistent storage on disk. The "
"<literal>MessageCache</literal> uses a least recently used (LRU) algorithm "
"to determine which messages should go to disk."
-msgstr ""
+msgstr "服务器里创建的消息被传递给 <literal>MessageCache</literal> 进行管理。当消息被添加到没有接收者的目的地时，对 JVM 内存的使用增加。这些消息保存在主内存里，直到接收者把它们提走为止。如果 <literal>MessageCache</literal> 注意到 JVM 内存的使用超过了设定的限额，<literal>MessageCache</literal> 将开始把这些消息移至磁盘上的持久性存储空间。<literal>MessageCache</literal> 使用最近最少使用（least recently used，LRU）算法来决定移出哪些消息。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:225
-#, fuzzy, no-c-format
+#, no-c-format
msgid "State Manager"
-msgstr "状态传输（State Transfer）"
+msgstr "状态管理者（State Manager）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:226
@@ -2391,13 +2397,13 @@
"The <literal>StateManager</literal> (SM) is in charge of keeping track of "
"who is allowed to log into the server and what their durable subscriptions "
"are."
-msgstr ""
+msgstr "<literal>StateManager</literal> (SM) 负责记录登录服务器的用户及其持久的订阅。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:232
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Persistence Manager"
-msgstr "持久化类"
+msgstr "Persistence Manager（持久性管理者）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:233
@@ -2408,7 +2414,7 @@
"implementations of the persistent manager, but only one can be enabled per "
"server instance. You should enable the persistence manager that best matches "
"your requirements."
-msgstr ""
+msgstr "目的地使用 <literal>PersistenceManager</literal> (PM) 来存储标记为持久化的消息。JBossMQ 有几个不同的持久性管理者实现，但只有一个可以为每个服务器实例启用。你应该根据需要来启用持久性管理者。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:238
@@ -2422,7 +2428,7 @@
"is also highly integrated with the <literal>MessageCache</literal> to "
"provide efficient persistence on a system that has a very active "
"<literal>MessageCache</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">JDBC2 persistence manager</emphasis>：JDBC2 持久性管理者允许你用 JDBC 把持久性消息存储到一个关系型数据库。这个 PM 的性能和可以从数据库获得的性能直接相关。和其他持久性管理者相比，它有一个非常低的内存消耗。而且，它也高度集成在 <literal>MessageCache</literal> 里，为具有非常活跃的 <literal>MessageCache</literal> 的系统提供高效的持久化。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:243
@@ -2437,12 +2443,14 @@
"the real persistence manager and link the new name to the null persistence "
"manager."
msgstr ""
+"<emphasis role=\"bold\">Null Persistence Manager</emphasis>：这是可以委托真正的持久性管理者的 wrapper。目的地的配置决定持久化和缓存是否被实际执行。你可以在 <literal>docs/"
+"examples/jms</literal> 里找到示例配置。要使用由真实持久性管理者支持的 Null Persistence Manager，你需要修改真实持久性管理者的 <literal>ObjectName</literal> 并把新的名字链接至这个 Null Persistence Manager。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:251
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Destinations"
-msgstr "描述"
+msgstr "目的地（Destination）述"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:252
@@ -2452,13 +2460,13 @@
"and receive messages. There are two types of destination objects, "
"<literal>Queues</literal> and <literal>Topics</literal>. References to the "
"destinations created by JBossMQ are stored in JNDI."
-msgstr ""
+msgstr "目的地是客户端用来发送和接收消息的 JBossMQ 服务器上的对象。有两种类型的目的地对象：<literal>队列（Queue）</literal>和<literal>主题（Topic）</literal>。对 JBossMQ 创建的目的地的引用存储在 JNDI 里。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:256
#, no-c-format
msgid "Queues"
-msgstr ""
+msgstr "队列（Queue）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:257
@@ -2470,13 +2478,13 @@
"queue, the messages will be load balanced across the receivers. Queue "
"objects, by default, will be stored under the JNDI <literal>queue/</literal> "
"sub context."
-msgstr ""
+msgstr "点对点模式的客户端通常使用队列。它们期望发送到队列的消息将只被一个其他客户端接收一次。如果多个客户端从单个队列接收消息，这些消息将在所有接收者间进行负载平衡。在缺省情况下，对列对象将被存储在 JNDI <literal>queue/</literal> 子上下文里。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:263
#, no-c-format
msgid "Topics"
-msgstr ""
+msgstr "主题（Topic）"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:264
@@ -2492,13 +2500,13 @@
"messages, clients can start a durable subscription. This is like having a "
"VCR record a show you cannot watch at its scheduled time so that you can see "
"what you missed when you turn your TV back on."
-msgstr ""
+msgstr "主题用在发布-订阅模式里。当客户端发布一个消息到主题时，它期望这个消息的拷贝将被递送到订阅了这个主题的每个客户。主题消息和电视节目的发送方式相同。除非你打开了电视并观赏这个节目，否则你将错过它。类似地，如果客户端没有启动并从主题接收消息，它将错过发布到这个主题的消息。要解决丢失消息的问题，客户端可以使用一个持久性订阅。这好比在你不能及时观赏的节目播出时间用 VCD 进行录制，之后你打开电视就还可以看到这个错过的节目。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:274
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBoss MQ Configuration and MBeans"
-msgstr "JBossCache 配置"
+msgstr "JBoss MQ 配置和 MBean"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:275
@@ -2507,7 +2515,7 @@
"This section defines the MBean services that correspond to the components "
"introduced in the previous section along with their MBean attributes. The "
"configuration and service files that make up the JBossMQ system include:"
-msgstr ""
+msgstr "本节定义了对应于前一节和 MBean 属性一起介绍的组件的 MBean 服务。组成 JBossMQ 系统的配置和服务文件包括："
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:280
@@ -2516,7 +2524,7 @@
"<emphasis role=\"bold\">deploy/hsqldb-jdbc-state-service.xml</emphasis>: "
"This configures the JDBC state service for storing state in the embedded "
"Hypersonic database."
-msgstr ""
+msgstr "<emphasis role=\"bold\">deploy/hsqldb-jdbc-state-service.xml</emphasis>：它配置了在内嵌的 Hypersonic 数据库里存储状态的 JDBC 状态服务。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:285
@@ -2527,6 +2535,9 @@
"<literal>MessageCache</literal>, and jdbc2 <literal>PersistenceManager</"
"literal> for the embedded Hypersonic database."
msgstr ""
+"<emphasis role=\"bold\">deploy/jms/hsqldb-jdbc2-service.xml</emphasis>：这个服务描述符文件配置了用于内嵌的 Hypersonic 数据库的 <literal>DestinationManager</literal>、"
+"<literal>MessageCache</literal> 和 jdbc2 <literal>PersistenceManager</"
+"literal>。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:290
@@ -2538,14 +2549,17 @@
"remove destinations to this file, or deploy another <literal>*-service.xml</"
"literal> descriptor with the destination configurations."
msgstr ""
+"<emphasis role=\"bold\">deploy/jms/jbossmq-destinations-service.xml</"
+"emphasis>：这个服务描述符定义了 Testsuite 单元测试使用的缺省 JMS 对列和主题目的地配置。你可以在这个文件里添加/删除目的地，或者部署另外一个带有目的地配置的 <literal>*-service.xml</"
+"literal> 描述符。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:295
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">jbossmq-httpil.sar</emphasis>: This SAR file "
"configures the HTTP invocation layer."
-msgstr "<emphasis role=\"bold\">name</emphasis>：这个元素包含操作的名字。"
+msgstr "<emphasis role=\"bold\">jbossmq-httpil.sar</emphasis>：这个 SAR 文件配置 HTTP 调用层服务。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:300
@@ -2557,6 +2571,8 @@
"<literal>DynamicStateManager</literal>, and core interceptor stack. It also "
"defines the MDB default dead letter queue <literal>DLQ</literal>."
msgstr ""
+"<emphasis role=\"bold\">deploy/jms/jbossmq-service.xml</emphasis>：这个服务描述配置核心的 JBossMQ MBean，如 <literal>Invoker</literal>、<literal>SecurityManager</literal>、"
+"<literal>DynamicStateManager</literal>，以及核心的拦截器栈。它也定义 MDB 的缺省 dead letter queue（DLQ）。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:305
@@ -2565,26 +2581,24 @@
"<emphasis role=\"bold\">deploy/jms/jms-ds.xml</emphasis>: This is a JCA "
"connection factory and JMS provider MDB integration services configuration "
"which sets JBossMQ as the JMS provider."
-msgstr ""
+msgstr "<emphasis role=\"bold\">deploy/jms/jms-ds.xml</emphasis>：这是一个 JCA 连接工厂和把 JBossMQ 设置为 JMS 提供者的 MDB 集成服务的配置。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:310
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">deploy/jms/jms-ra.rar</emphasis>: This is a JCA "
"resource adaptor for JMS providers."
-msgstr "<emphasis role=\"bold\">parameter</emphasis>：这个元素描述了操作的签名。"
+msgstr "<emphasis role=\"bold\">deploy/jms/jms-ra.rar</emphasis>：这是一个用于 JMS 提供者的 JCA 资源适配器。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:315
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">deploy/jms/jvm-il-service.xml</emphasis>: This "
"service descriptor configures the <literal>JVMServerILService</literal> "
"which provides the JVM IL transport."
-msgstr ""
-"<emphasis role=\"bold\">FromName</emphasis>：<literal>LinkRef</literal> 在 "
-"JNDI 下绑定的位置。"
+msgstr "<emphasis role=\"bold\">deploy/jms/jvm-il-service.xml</emphasis>：这个服务描述符文件配置提供 JVM IL 支持的 <literal>JVMServerILService</literal>。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:320
@@ -2594,7 +2608,7 @@
"service descriptor configures the <literal>RMIServerILService</literal> "
"which provides the RMI IL. The queue and topic connection factory for this "
"IL is bound under the name <literal>RMIConnectionFactory</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">deploy/jms/rmi-il-service.xml</emphasis>：这个服务描述符配置提供 RMI IL 的 <literal>RMIServerILService</literal>。这个 IL 的队列和主题连接工厂绑定在 <literal>RMIConnectionFactory</literal> 上。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:325
@@ -2606,29 +2620,27 @@
"IL is bound under the name <literal>UIL2ConnectionFactory</literal> as well "
"as <literal>UILConnectionFactory</literal> to replace the deprecated version "
"1 UIL service."
-msgstr ""
+msgstr "<emphasis role=\"bold\">deploy/jms/uil2-service.xml</emphasis>：这个服务描述符配置提供 UIL2 传输的 <literal>UILServerILService</literal>。这个 IL 的队列和主题连接工厂绑定在 <literal>UIL2ConnectionFactory</literal> 和 <literal>UILConnectionFactory</literal> 上来替换已取消的版本为 1 的 UIL 服务。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:330
#, no-c-format
msgid "We will discuss the associated MBeans in the following subsections."
-msgstr ""
+msgstr "我们将在后续章节讨论相关的 MBean。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:334
#, no-c-format
msgid "org.jboss.mq.il.jvm.JVMServerILService"
-msgstr ""
+msgstr "org.jboss.mq.il.jvm.JVMServerILService"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:335
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>org.jboss.mq.il.jvm.JVMServerILService</literal> MBean is used "
"to configure the JVM IL. The configurable attributes are as follows:"
-msgstr ""
-"<literal>PooledInvoker</literal> MBean 支持许多属性来配置套接字传输层。它的可"
-"配置属性是："
+msgstr "<literal>org.jboss.mq.il.jvm.JVMServerILService</literal> MBean 用来配置 JVM IL。其可配置属性如下："
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:340
@@ -2639,29 +2651,25 @@
"requests to the JMS server. This is not something you would typically change "
"from the <literal>jboss.mq:service=Invoker</literal> setting unless you "
"change the entry point service."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Invoker</emphasis>：这个属性指定把转入请求传给 JMS 服务器的 JMS 入口服务的 JMX ObjectName。除非你修改入口服务，否则你通常不会在 <literal>jboss.mq:service=Invoker</literal> 设置里对它进行修改。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:345 J2EE_Messaging_On_JBOSS.xml:374
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ConnectionFactoryJNDIRef</emphasis>: The JNDI "
"location that this IL will bind a <literal>ConnectionFactory</literal> setup "
"to use this IL."
-msgstr ""
-"<emphasis role=\"bold\">FromName</emphasis>：<literal>LinkRef</literal> 在 "
-"JNDI 下绑定的位置。"
+msgstr "<emphasis role=\"bold\">ConnectionFactoryJNDIRef</emphasis>：这个 IL 将 <literal>ConnectionFactory</literal> 设置绑定的 JNDI 位置。 "
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:350 J2EE_Messaging_On_JBOSS.xml:379
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">XAConnectionFactoryJNDIRef</emphasis>: The JNDI "
"location that this IL will bind a <literal>XAConnectionFactory</literal> "
"setup to use this IL."
-msgstr ""
-"<emphasis role=\"bold\">FromName</emphasis>：<literal>LinkRef</literal> 在 "
-"JNDI 下绑定的位置。"
+msgstr "<emphasis role=\"bold\">XAConnectionFactoryJNDIRef</emphasis>：这个 IL 将 <literal>XAConnectionFactory</literal> 设置绑定的 JNDI 位置。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:355
@@ -2672,13 +2680,13 @@
"connection is still valid. If this is set to zero, then no ping message will "
"be sent. Since it is impossible for JVM IL connection to go bad, it is "
"recommended that you keep this set to 0."
-msgstr ""
+msgstr "<emphasis role=\"bold\">PingPeriod</emphasis>：客户端发送 Ping 消息给服务器来验证连接的有效性的时间间隔，其单位为毫秒。如果设置为 0，表示不发送 Ping 消息。既然 JVM IL 连接不可能出问题，我们推荐把这个值设为 0。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:363
#, no-c-format
msgid "org.jboss.mq.il.uil2.UILServerILService"
-msgstr ""
+msgstr "org.jboss.mq.il.uil2.UILServerILService"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:364
@@ -2686,7 +2694,7 @@
msgid ""
"The <literal>org.jboss.mq.il.uil2.UILServerILService</literal> is used to "
"configure the UIL2 IL. The configurable attributes are as follows:"
-msgstr ""
+msgstr "<literal>org.jboss.mq.il.uil2.UILServerILService</literal> 用来配置 UIL2 IL。其可配置属性如下："
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:369
@@ -2697,7 +2705,7 @@
"pass incoming requests to the JMS server. This is not something you would "
"typically change from the <literal>jboss.mq:service=Invoker</literal> "
"setting unless you change the entry point service."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Invoker</emphasis>：这个属性指定用来往 JMS 服务器传递传入请求的 JMS 入口服务的 JMX <literal>ObjectName</literal>。除非你修改入口服务，否则你通常不会在 <literal>jboss.mq:service=Invoker</literal> 设置里对它进行修改。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:384
@@ -2707,7 +2715,7 @@
"the client should send a ping message to the server to validate that the "
"connection is still valid. If this is set to zero, then no ping message will "
"be sent."
-msgstr ""
+msgstr "<emphasis role=\"bold\">PingPeriod</emphasis>：客户端发送 Ping 消息给服务器来验证连接的有效性的时间间隔，其单位为毫秒。如果设置为 0，表示不发送 Ping 消息。既然 JVM IL 连接不可能出问题，我们推荐把这个值设为 0。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:389
@@ -2718,18 +2726,19 @@
"This allows detection of dead sockets that are not responsive and are not "
"capable of receiving ping messages. Note that this setting should be longer "
"in duration than the <literal>PingPeriod</literal> setting."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ReadTimeout</emphasis>：作为 UIL2 套接字的 <literal>SoTimeout</literal> 值的时间间隔，单位为毫秒。这允许检测已不再响应且不能够接收 Ping 消息的失效的套接字。请注意，这个设置应该比 <literal>PingPeriod</literal> 设置更长。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:394
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">BufferSize</emphasis>: The size in bytes used as the "
"buffer over the basic socket streams. This corresponds to the <literal>java."
"io.BufferedOutputStream</literal> buffer size."
msgstr ""
-"<emphasis role=\"bold\">bufferSize</emphasis>：它是这个连接器建立的输入流的缓"
-"冲区大小（字节）。它的缺省值是 2048 个字节。"
+"<emphasis role=\"bold\">BufferSize</emphasis>：基本套接字流的缓"
+"冲区大小（字节）。它对应 <literal>java."
+"io.BufferedOutputStream</literal> 的缓冲区大小。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:399
@@ -2745,29 +2754,31 @@
"reads or writes require a duration greater than the <literal>PingPeriod</"
"literal>."
msgstr ""
+"<emphasis role=\"bold\">ChunkSize</emphasis>：stream listener 通知之间的字节数。UIL2 层服务使用支持基于读/写至流里的数据触发的 heartbeat 的 <literal>org.jboss."
+"util.stream.NotifyingBufferedOutputStream</literal> 和 <literal>NotifyingBufferedInputStream</literal> 实现。每当 <literal>ChunkSize</literal> 个字节读取/写入到流里。当大量的读或些操作需要的时间大于 <literal>PingPeriod</"
+"literal> 时，这可以作为 ping 或 keepalive 通知。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:404
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ServerBindPort</emphasis>: The protocol listening "
"port for this IL. If not specified default is 0, which means that a random "
"port will be chosen."
msgstr ""
-"<emphasis role=\"bold\">ServerBindPort</emphasis>：用于服务器套接字的端口。如"
-"果为 0 则表示使用匿名端口。"
+"<emphasis role=\"bold\">ServerBindPort</emphasis>：用于这个 IL 的侦听端口。如"
+"果没有设置则缺省为 0，这表示使用随机端口。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:409
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">BindAddress</emphasis>: The specific address this IL "
"listens on. This can be used on a multi-homed host for a <literal>java.net."
"ServerSocket</literal> that will only accept connection requests on one of "
"its addresses."
msgstr ""
-"<emphasis role=\"bold\">BindAddress</emphasis>：<literal>NamingService</"
-"literal> 侦听的特定地址。它可以用在多宿主主机上，使用只接受其中一个地址的连接"
+"<emphasis role=\"bold\">BindAddress</emphasis>：IL 侦听的特定地址。它可以用在多宿主主机上，使用只接受其中一个地址的连接"
"请求的 <literal>java.net.ServerSocket</literal>。"
#. Tag: para
@@ -2779,10 +2790,12 @@
"This may improve request response times. Otherwise request packets may be "
"buffered by the operating system to create larger IP packets."
msgstr ""
+"<emphasis role=\"bold\">EnableTcpNoDelay</emphasis>：<literal>TcpNoDelay</"
+"literal> 导致只要请求被刷新，TCP/IP 数据包就被发送。 这可以提高请求响应时间。否则操作系统可以缓存请求数据包来创建更大的 IP 数据包。 "
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:419
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ServerSocketFactory</emphasis>: The <literal>javax."
"net.ServerSocketFactory</literal> implementation class name to use to create "
@@ -2790,36 +2803,34 @@
"default factory will be obtained from <literal>javax.net.ServerSocketFactory."
"getDefault()</literal>."
msgstr ""
-"<emphasis role=\"bold\">JNPServerSocketFactory</emphasis>：可选的自定义 "
-"<literal>javax.net.ServerSocketFactory</literal> 实现的类名。它是 "
-"<literal>ServerSocket</literal> 用来引导 JBossNS <literal>Naming</literal> 接"
-"口下载的工厂(factory)。它如果没有被指定，将使用 <literal>javax.net."
+"<emphasis role=\"bold\">JNPServerSocketFactory</emphasis>：用来创建服务 <literal>java.net.ServerSocket</literal> 的 <literal>javax.net.ServerSocketFactory</literal> 实现的类名。它如果没有被指定，将使用 <literal>javax.net."
"ServerSocketFactory.getDefault()</literal> 方法的值。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:424
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ClientAddress</emphasis>: The address passed to the "
"client as the address that should be used to connect to the server."
-msgstr "<emphasis role=\"bold\">className</emphasis>：提供服务实现的类的名字。"
+msgstr "<emphasis role=\"bold\">ClientAddress</emphasis>：传递给客户端的用来连接服务器的地址。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:429
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ClientSocketFactory</emphasis>: The <literal>javax."
"net.SocketFactory</literal> implementation class name to use on the client. "
"If not specified the default factory will be obtained from <literal>javax."
"net.SocketFactory.getDefault()</literal>."
msgstr ""
-"<emphasis role=\"bold\">ClientSocketFactory</emphasis>：可选的自定义 "
-"<literal>java.rmi.server.RMIClientSocketFactory</literal> 实现的类名。如果它"
-"没有指定，将使用缺省的 <literal>RMIClientSocketFactory</literal>。"
+"<emphasis role=\"bold\">ClientSocketFactory</emphasis>：用于客户端的 <literal>javax."
+"net.SocketFactory</literal> 实现的类名。如果它"
+"没有指定，将使用缺省的 <literal>javax."
+"net.SocketFactory.getDefault()</literal>。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:434
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">SecurityDomain</emphasis>: Specify the security "
"domain name to use with JBoss SSL aware socket factories. This is the JNDI "
@@ -2827,15 +2838,14 @@
"<literal>security-domain</literal> element of the <literal>jboss.xml</"
"literal> and <literal>jboss-web.xml</literal> descriptors."
msgstr ""
-"<emphasis role=\"bold\">DefaultSecurityDomain</emphasis>：它指定在 WAR 文件"
-"的 <literal>jboss-web.xml</literal> 里的 <literal>security-domain</literal> "
-"没有显性地指定的情况下的 JAAS 安全域名。"
+"<emphasis role=\"bold\">SecurityDomain</emphasis>：指定和可识别 JBoss SSL 的套接字工厂一起使用的安全域名。这是 <literal>jboss.xml</"
+"literal> 和 <literal>jboss-web.xml</literal> 描述符里的 <literal>security-domain</literal> 元素所描述的安全管理者实现的 JNDI 名称。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:440
#, no-c-format
msgid "Configuring UIL2 for SSL"
-msgstr ""
+msgstr "为 SSL 配置 UIL2"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:441
@@ -2847,12 +2857,14 @@
"custom JBoss SSL socket factories is shown in <xref linkend="
"\"Configuring_UIL2_for_SSL-An_example_UIL2_config_fragment_for_using_SSL\"/>."
msgstr ""
+"UIL2 服务通过用和 IL 服务相关联的安全域名集成 JSSE 的自定义套接字工厂来支持 SSL。<xref linkend="
+"\"Configuring_UIL2_for_SSL-An_example_UIL2_config_fragment_for_using_SSL\"/> 展示了一个解释自定义 JBoss SSL 套接字工厂的用法的 UIL2 服务描述符的例子。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:444
#, no-c-format
msgid "An example UIL2 config fragment for using SSL"
-msgstr ""
+msgstr "使用 SSL 的 UIL2 配置示例片段"
#. Tag: programlisting
#: J2EE_Messaging_On_JBOSS.xml:445
@@ -2899,12 +2911,52 @@
" <attribute name=\"KeyStorePass\">changeme</attribute>\n"
"</mbean>"
msgstr ""
+"<mbean code=\"org.jboss.mq.il.uil2.UILServerILService\"\n"
+" name=\"jboss.mq:service=InvocationLayer,type=HTTPSUIL2\">\n"
+" <depends optional-attribute-name=\"Invoker\">jboss.mq:"
+"service=Invoker</depends>\n"
+" <attribute name=\"ConnectionFactoryJNDIRef\">"
+"SSLConnectionFactory</attribute>\n"
+" <attribute name=\"XAConnectionFactoryJNDIRef\">"
+"SSLXAConnectionFactory</attribute>\n"
+" \n"
+" <!-- ... -->\n"
+"\n"
+" <!-- SSL Socket Factories -->\n"
+" <attribute name=\"ClientSocketFactory\">\n"
+" org.jboss.security.ssl.ClientSocketFactory\n"
+" </attribute>\n"
+" <attribute name=\"ServerSocketFactory\">\n"
+" org.jboss.security.ssl.DomainServerSocketFactory\n"
+" </attribute>\n"
+" <!-- Security domain - see below -->\n"
+" <attribute name=\"SecurityDomain\">java:/jaas/SSL</"
+"attribute>\n"
+"</mbean>\n"
+"\n"
+"<!-- Configures the keystore on the \"SSL\" security domain\n"
+" This mbean is better placed in conf/jboss-service.xml where it\n"
+" can be used by other services, but it will work from anywhere.\n"
+" Use keytool from the sdk to create the keystore. -->\n"
+" \n"
+"<mbean code=\"org.jboss.security.plugins.JaasSecurityDomain\"\n"
+" name=\"jboss.security:service=JaasSecurityDomain,domain=SSL\">\n"
+" <!-- This must correlate with the java:/jaas/SSL above -->\n"
+" <constructor>\n"
+" <arg type=\"java.lang.String\" value=\"SSL\"/>\n"
+" </constructor>\n"
+" <!-- The location of the keystore resource: loads from the\n"
+" classpath and the server conf dir is a good default -->\n"
+" <attribute name=\"KeyStoreURL\">resource:uil2.keystore</"
+"attribute>\n"
+" <attribute name=\"KeyStorePass\">changeme</attribute>\n"
+"</mbean>"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:450
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JMS client properties for the UIL2 transport"
-msgstr "A JNDI client that uses HTTPS as the transport"
+msgstr "用于 UIL2 传输的 JMS 客户端属性"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:451
@@ -2912,7 +2964,7 @@
msgid ""
"There are several system properties that a JMS client using the UIL2 "
"transport can set to control the client connection back to the server"
-msgstr ""
+msgstr "使用 UIL2 传输的 JMS 客户度可以设置几个系统属性来控制客户端到服务器的连接"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:456
@@ -2924,7 +2976,7 @@
"the<literal>InetAddress.getHostAddress</literal> value. This will only make "
"a difference if name resolution differs between the server and client "
"environments."
-msgstr ""
+msgstr "<emphasis role=\"bold\">org.jboss.mq.il.uil2.useServerHost</emphasis>：这个系统属性允许客户端连接至服务器 <literal>InetAddress.getHostName</literal> 而不是 <literal>InetAddress.getHostAddress</literal>。这只有在服务器和客户端环境间的名字解析不同时才有区别。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:461
@@ -2933,7 +2985,7 @@
"<emphasis role=\"bold\">org.jboss.mq.il.uil2.localAddr</emphasis>: This "
"system property allows a client to define the local interface to which its "
"sockets should be bound."
-msgstr ""
+msgstr "<emphasis role=\"bold\">org.jboss.mq.il.uil2.localAddr</emphasis>：这个系统属性允许客户端定义它的套接字应该绑定的本地接口。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:466
@@ -2942,7 +2994,7 @@
"<emphasis role=\"bold\">org.jboss.mq.il.uil2.localPort</emphasis>: This "
"system property allows a client to define the local port to which its "
"sockets should be bound"
-msgstr ""
+msgstr "<emphasis role=\"bold\">org.jboss.mq.il.uil2.localPort</emphasis>：这个系统属性允许客户端定义它的套接字应该绑定的本地端口。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:471
@@ -2952,7 +3004,7 @@
"system property allows a client to override the address to which it attempts "
"to connect to. This is useful for networks where NAT is occurring between "
"the client and JMS server."
-msgstr ""
+msgstr "<emphasis role=\"bold\">org.jboss.mq.il.uil2.serverAddr</emphasis>：这个系统属性允许客户端覆盖它试图连接的地址。这对于在客户端和 JMS 服务器间存在 NAT 的网络来说很有用。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:476
@@ -2962,7 +3014,7 @@
"system property allows a client to override the port to which it attempts to "
"connect. This is useful for networks where port forwarding is occurring "
"between the client and jms server."
-msgstr ""
+msgstr "<emphasis role=\"bold\">org.jboss.mq.il.uil2.serverPort</emphasis>：这个系统属性允许客户端覆盖它试图连接的端口。这对于在客户端和 JMS 服务器间存在端口映射（port forwarding）的网络来说很有用。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:481
@@ -2973,6 +3025,8 @@
"JMS server. Retries are only made for <literal>java.net.ConnectException</"
"literal> failures. A value <= 0 means no retry attempts will be made."
msgstr ""
+"<emphasis role=\"bold\">org.jboss.mq.il.uil2.retryCount</emphasis>：这个系统属性控制重试连接 JMS 服务器的次数。重试仅在 <literal>java.net.ConnectException</"
+"literal> 失败时才发生。值为 0 则表示不允许重试。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:486
@@ -2981,13 +3035,13 @@
"<emphasis role=\"bold\">org.jboss.mq.il.uil2.retryDelay</emphasis>: This "
"system property controls the delay in milliseconds between retries due to "
"<literal>ConnectException</literal> failures."
-msgstr ""
+msgstr "<emphasis role=\"bold\">org.jboss.mq.il.uil2.retryDelay</emphasis>：这个系统属性控制由于 <literal>ConnectException</literal> 失败导致的重试之间的延迟（毫秒）。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:496
#, no-c-format
msgid "org.jboss.mq.il.http.HTTPServerILService"
-msgstr ""
+msgstr "org.jboss.mq.il.http.HTTPServerILService"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:497
@@ -2998,7 +3052,7 @@
"HTTP or HTTPS connections. The relies on the servlet deployed in the "
"<literal>deploy/jms/jbossmq-httpil.sar</literal> to handle the HTTP traffic. "
"The configurable attributes are as follows:"
-msgstr ""
+msgstr "<literal>org.jboss.mq.il.http.HTTPServerILService</literal> 用来管理 HTTP/S IL。这个 IL 允许通过 HTTP 或 HTTPS 连接使用 JMS 服务。它依赖部署在 <literal>deploy/jms/jbossmq-httpil.sar</literal> 里的 Servelet 来处理 HTTP 请求。其可配置属性如下："
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:502
@@ -3009,6 +3063,8 @@
"on the client by setting the system property <literal>org.jboss.mq.il.http."
"timeout</literal> to the number of seconds."
msgstr ""
+"<emphasis role=\"bold\">TimeOut</emphasis>：客户端 HTTP 请求等待消息的超时时间（秒）。它可以通过客户端设置系统属性 <literal>org.jboss.mq.il.http."
+"timeout</literal> 来覆盖。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:507
@@ -3027,6 +3083,8 @@
"restinterval</literal> with the number of seconds you wish to wait between "
"requests."
msgstr ""
+"<emphasis role=\"bold\">RestInterval</emphasis>：客户端在每次请求后睡眠的秒数。它缺省为 0，但你可以设置这个值和 <literal>TimeOut</literal> 来实现纯粹的定时轮询机制。例如，你可以简单地通过设置 <literal>TimeOut</literal> 为 0 和 <literal>RestInterval</literal> 为 60 来发出短期的请求。这会导致客户端向服务器发送一个非阻塞性请求，返回任何可用的消息，然后在发送另外一个请求前睡眠 60 秒。就象 <literal>TimeOut</literal> 值，它可以在客户端指定 <literal>org.jboss.mq.il.http."
+"restinterval</literal> 为你希望的值来显性地被覆盖。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:512
@@ -3041,6 +3099,8 @@
"URL will be formed from <literal>URLPrefix + URLHostName + \":\" + URLPort + "
"\"/\" + URLSuffix</literal>."
msgstr ""
+"<emphasis role=\"bold\">URL</emphasis>：设置 servlet URL。这个值优先于任何独立的值组合（例如，<literal>URLPrefix</literal>、<literal>URLSuffix</literal>、<literal>URLPort</literal> 等）。它可以是一个实际的 URL 或调用 <literal>System.getProperty(propertyname)</literal> 用于客户端来解析正确的 URL 的属性名。 如果没有指定，这个 URL 的格式将为 <literal>URLPrefix + URLHostName + \":\" + URLPort + "
+"\"/\" + URLSuffix</literal>。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:517
@@ -4390,55 +4450,51 @@
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1026
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">AllMessageCount</emphasis>: The message count across "
"all queue types associated with the topic."
-msgstr ""
-"<emphasis role=\"bold\">descriptors</emphasis>：与操作元数据关联的任何描述"
-"符。"
+msgstr "<emphasis role=\"bold\">AllMessageCount</emphasis>：和这个主题关联的所有队列里的消息的数目。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1031
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">AllSubscriptionsCount</emphasis>: The count of "
"durable and non-durable subscriptions."
-msgstr "<emphasis role=\"bold\">description</emphasis>：构造函数的描述"
+msgstr "<emphasis role=\"bold\">AllSubscriptionsCount</emphasis>：持久性和非持久性订阅的数量。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1036
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">DurableMessageCount</emphasis>: The count of "
"messages in durable subscription queues."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>：这个元素指定操作的易读的描"
-"述。"
+msgstr "<emphasis role=\"bold\">DurableMessageCount</emphasis>：持久性订阅队列里的消息的数目。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1041
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"d <emphasis role=\"bold\">DurableSubscriptionsCount</emphasis>: The count of "
"durable subscribers."
-msgstr "<emphasis role=\"bold\">description</emphasis>：对attribute的描述"
+msgstr "d <emphasis role=\"bold\">DurableSubscriptionsCount</emphasis>：持久性订阅者的数量。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1051
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">NonDurableMessageCount</emphasis>: The count on "
"messages in non-durable subscription queues."
-msgstr "<emphasis role=\"bold\">read-only</emphasis>：只读。"
+msgstr "<emphasis role=\"bold\">NonDurableMessageCount</emphasis>：非持久性订阅队列里的消息数目。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1056
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">NonDurableSubscriptionsCount</emphasis>: The count "
"of non-durable subscribers."
-msgstr "<emphasis role=\"bold\">description</emphasis>：对attribute的描述"
+msgstr "<emphasis role=\"bold\">NonDurableSubscriptionsCount</emphasis>：非持久性订阅者的数量。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1061
@@ -4572,47 +4628,45 @@
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1118
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">ProviderAdapterClass</emphasis>: The fully qualified "
"class name of the org.jboss.jms.jndi.JMSProviderAdapter<literal></literal> "
"interface to create an instance of."
-msgstr ""
-"<emphasis role=\"bold\">className</emphasis>：这是 <literal>org.apache."
-"catalina.Valve</literal> 接口实现的类全名。"
+msgstr "<emphasis role=\"bold\">ProviderAdapterClass</emphasis>：实例化 org.jboss.jms.jndi.JMSProviderAdapter<literal></literal> 接口的全限定类名。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1123
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">FactoryRef</emphasis>: The JNDI name under which the "
"provider <literal>javax.jms.ConnectionFactory</literal> will be bound."
-msgstr "<emphasis role=\"bold\">JndiName</emphasis>：代理将被绑定的 JNDI 名。"
+msgstr "<emphasis role=\"bold\">FactoryRef</emphasis>：提供者 <literal>javax.jms.ConnectionFactory</literal> 将被绑定的 JNDI 名称。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1128
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">QueueFactoryRef</emphasis>: The JNDI name under "
"which the provider <literal>javax.jms.QueueConnectionFactory</literal> will "
"be bound."
-msgstr "<emphasis role=\"bold\">JndiName</emphasis>：代理将被绑定的 JNDI 名。"
+msgstr "<emphasis role=\"bold\">QueueFactoryRef</emphasis>：提供者 <literal>javax.jms.QueueConnectionFactory</literal> 将绑定的 JNDI 名称。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1133
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">TopicFactoryRef</emphasis>: The JNDI name under "
"which the <literal>javax.jms.TopicConnectionFactory</literal> will be bound."
-msgstr "<emphasis role=\"bold\">JndiName</emphasis>：外部的上下文绑定的 JNDI 名。"
+msgstr "<emphasis role=\"bold\">TopicFactoryRef</emphasis>：<literal>javax.jms.TopicConnectionFactory</literal> 将绑定的 JNDI 名称。"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1138
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">Properties</emphasis>: The JNDI properties of the "
"initial context used to look up the factories."
-msgstr "<emphasis role=\"bold\">JndiName</emphasis>：外部的上下文绑定的 JNDI 名。"
+msgstr "<emphasis role=\"bold\">Properties</emphasis>：用来查找工厂的初始上下文的 JNDI 属性。"
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:1143
@@ -4746,7 +4800,7 @@
#: J2EE_Messaging_On_JBOSS.xml:1156
#, no-c-format
msgid "A jms-ds.xml descriptor for integrating a JMS provider adaptor via JCA"
-msgstr ""
+msgstr "用于通过 JCA 集成 JMS 提供者适配器的 jms-ds.xml 描述符"
#. Tag: programlisting
#: J2EE_Messaging_On_JBOSS.xml:1157
@@ -4821,9 +4875,9 @@
#. Tag: title
#: J2EE_Messaging_On_JBOSS.xml:1186
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Integrating non-JBoss JMS Providers"
-msgstr "编写JBoss MBean服务"
+msgstr "集成非 JBoss JMS 提供者"
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1187
@@ -4832,7 +4886,7 @@
"We have mentioned that one can replace the JBossMQ JMS implementation with a "
"foreign implementation. Here we summarize the various approaches one can "
"take to do the replacement:"
-msgstr ""
+msgstr "我们曾提到你可以用其他实现替换 JBossMQ JMS 实现。这里我们对进行替换所需的不同方法进行总结："
#. Tag: para
#: J2EE_Messaging_On_JBOSS.xml:1192
More information about the jboss-cvs-commits
mailing list