[jboss-cvs] JBossAS SVN: r85871 - 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
Mon Mar 16 00:07:47 EDT 2009
Author: xhuang at jboss.com
Date: 2009-03-16 00:07:46 -0400 (Mon, 16 Mar 2009)
New Revision: 85871
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Naming.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po 2009-03-16 03:43:17 UTC (rev 85870)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Connectors_On_JBOSS.po 2009-03-16 04:07:46 UTC (rev 85871)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Connectors_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-03-13 15:59+1000\n"
+"PO-Revision-Date: 2009-03-16 13:45+1000\n"
"Last-Translator: Xi HUANG\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -149,7 +149,7 @@
"the pool management is to allow for scalability. Resource connections are "
"typically expense objects to create and pooling them allows for more "
"effective reuse and management."
-msgstr ""
+msgstr "<emphasis role=\"bold\">Connection management</emphasis>：允许应用服务器建立资源连接池的合约。连接池管理的目的是实现可扩充性。创建资源连接对象通常是开销较大，把它们放入连接池可以更有效地重用和管理。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:49
@@ -178,7 +178,7 @@
"integration information. The resource adaptor also exposes the resource "
"manager to the application server components. This can be done using the CCI "
"and/or a resource adaptor specific API."
-msgstr ""
+msgstr "资源适配器实现了系统合约的资源管理方面。这使建立应用服务器连接池、提供事务资源信息并使用安全性集成信息成为必需。资源适配器也为应用服务器组件开放资源管理者。这可以用 CCI 和/或资源适配器专有的 API 来实现。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:62
@@ -193,6 +193,8 @@
"resource adaptor is that the client has the option of using the resource "
"adaptor independent CCI API if the resource adaptor supports this."
msgstr ""
+"应用程序组件使用标准的 J2EE 容器到组件的合约集成到应用服务器里。对于 EJB 组件，这个合约由 J2EE 规格定义。应用程序组件和资源适配器以和其他任何标准资源工厂相同的方式进行交互，例如<literal>javax.sql."
+"DataSource</literal> JDBC 资源工厂。它和 JCA 资源适配器的唯一区别是客户可以使用独立于资源适配器的 CCI API（如果该资源适配器支持它）。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:65
@@ -201,7 +203,7 @@
"(from the JCA 1.5 specification) illustrates the relationship between the "
"JCA architecture participants in terms of how they relate to the JCA SPI, "
"CCI and JTA packages."
-msgstr ""
+msgstr "JCA 1.5 规格按照 JCA 构架参与者怎样和 JCA SPI、CCI 和 JTA 包关联解释了它们之间的关系。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:69
@@ -209,7 +211,7 @@
msgid ""
"The JCA 1.0 specification class diagram for the connection management "
"architecture."
-msgstr ""
+msgstr "连接管理架构的 JCA 1.0 规格类图。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:76
@@ -224,12 +226,17 @@
"implementation are discussed in the following section on the JBossCX "
"architecture."
msgstr ""
+"JBossCX 架构提供了应用服务器专有类的实现。<xref linkend=\"JCA_Overview-"
+"The_JCA_1.0_specification_class_diagram_for_the_connection_management_architecture."
+"\"/> 显示了对 <literal>javax."
+"resource.spi.ConnectionManager</literal> 和 <literal>javax.resource.spi."
+"ConnectionEventListener</literal> 接口的实现。后面关于 JBossCX 架构的内容讨论这个实现的关键方面。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:82
-#, fuzzy, no-c-format
+#, no-c-format
msgid "An Overview of the JBossCX Architecture"
-msgstr "JBossNS 架构"
+msgstr "JBossCX 构架概述"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:83
@@ -239,7 +246,7 @@
"required for the use of JCA resource adaptors. This is primarily a "
"connection pooling and management extension along with a number of MBeans "
"for loading resource adaptors into the JBoss server."
-msgstr ""
+msgstr "JBossCX 构架提供使用 JCA 资源适配器所需的应用服务器构架扩展。这主要是一个连接池和管理的扩展以及一些用于把资源适配器加载到 JBoss 服务器里的 MBean。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:86
@@ -255,6 +262,10 @@
"available to the <literal>org.jboss.resource.connectionmanager."
"RARDeployment</literal> MBean."
msgstr ""
+"RAR 部署由三个成对的 MBean 组成。它们是 <literal>org.jboss.resource.deployment.RARDeployment</literal>、<literal>org."
+"jboss.resource.connectionmanager.RARDeployment</literal> 和 <literal>org."
+"jboss.resource.connectionmanager.BaseConnectionManager2</literal>。<literal>org.jboss.resource.deployment.RARDeployment</literal> 简单地封装了 RAR <literal>META-INF/ra.xml</literal> 描述符的元数据。它把这些信息开放为 DynamicMBean，使其为 <literal>org.jboss.resource.connectionmanager."
+"RARDeployment</literal> MBean 可用。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:89
@@ -271,6 +282,10 @@
"implementation with a <literal>org.jboss.resource.connectionmgr."
"RARDeployment</literal> dependent."
msgstr ""
+"RARDeployer 服务处理包含资源适配器（RAR）的归档文件的部署。当 RAR 文件被部署时，它创建 <literal>org.jboss.resource."
+"deployment.RARDeployment</literal> MBean。使资源适配器为应用程序组件所用的第一步是部署 RAR 文件。对于每个部署的 RAR，你必须配置一个或多个连接工厂并绑定到 JNDI。这个任务由 JBoss 服务的描述符来完成，它设置依赖于 <literal>org.jboss.resource.connectionmgr."
+"RARDeployment</literal> 的 <literal>org.jboss."
+"resource.connectionmanager.BaseConnectionManager2</literal> MBean 实现。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:93
@@ -292,6 +307,10 @@
"transaction semantics you want, provided the JCA resource adaptor supports "
"the corresponding transaction capability."
msgstr ""
+"<literal>org.jboss.resource.connectionmanager.BaseConnectionManager2</"
+"literal> MBean 是一个用于 JCA 规格要求的不同类型的连接管理者的基类。它的子类包括 <literal>NoTxConnectionManager</"
+"literal>、<literal>LocalTxConnectionManager</literal> 和 "
+"<literal>XATxConnectionManager</literal>。这些子类分别对应支持无事务、本地事务和 XA 事务的资源适配器。你可以根据事务类型来选择使用的子类，假设 JCA 资源适配器支持对应的事务能力。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:97
@@ -340,10 +359,13 @@
"login-config.xml</literal> JAAS login module configuration file. This "
"defines which JAAS login modules execute to perform authentication."
msgstr ""
+"<emphasis role=\"bold\">SecurityDomainJndiName</emphasis>：它指定用于资源连接验证和授权的安全域的 JNDI 名称。其形式通常为 <literal>java:/jaas/<domain></literal>，这里的 <literal><"
+"domain></literal> 是 <literal>conf/"
+"login-config.xml</literal> JAAS 登录模块配置文件里的值。它定义了哪个 JAAS 登录模块来执行验证。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:117
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">JaasSecurityManagerService</emphasis>: This is the "
"<literal>ObjectName</literal> of the security manager service. This should "
@@ -352,10 +374,9 @@
"security:service=JaasSecurityManager</literal>. This attribute will likely "
"be removed in the future."
msgstr ""
-"<emphasis role=\"bold\">InvokerName</emphasis>：<literal>conf/jboss-service."
-"xml</literal> 描述符里定义的 <literal>NamingService</literal> 的 JMX "
-"<literal>ObjectName</literal>。JBoss 发行版本里定义的标准设定是 "
-"<literal>jboss:service=Naming</literal>。"
+"<emphasis role=\"bold\">JaasSecurityManagerService</emphasis>：这是安全管理者服务的 <literal>ObjectName</literal>。这应该被设置为 <literal>conf/"
+"jboss-service.xml</literal> 描述符里定义的安全管理者 MBean 的名称，目前它是 <literal>jboss."
+"security:service=JaasSecurityManager</literal>。将来这个属性很可能被删除。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:125
@@ -392,6 +413,11 @@
"when it deploys a RAR file. This attribute will likely be removed in the "
"future."
msgstr ""
+"<emphasis role=\"bold\">OldRarDeployment</emphasis>：这是包含资源适配器元数据的 <literal>org.jboss.resource."
+"RarDeployment</literal> MBean 的 <literal>ObjectName</literal>。这个名字的形式是 <literal>jboss.jca:service=RARDeployment,name=<"
+"ra-display-name></literal>，这里的 <literal><ra-display-name></"
+"literal> 是 <literal>ra.xml</literal> 描述符的 <literal>display-name</"
+"literal> 属性值。当 <literal>RARDeployer</literal> 部署 RAR 文件时，它创建这个属性。将来这个属性很可能被删除。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:136
@@ -403,7 +429,7 @@
"of the attributes depend on the resource adaptor "
"<literal>ManagedConnectionFactory</literal> instance. The following example "
"shows the structure of the content of this attribute."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ManagedConnectionFactoryProperties</emphasis>：这是一个 (name, type, value) 的集合，它定义了 <literal>ManagedConnectionFactory</literal> 实例的属性。因此，这些属性的名称取决于资源适配器 <literal>ManagedConnectionFactory</literal> 实例。下面的例子显示了这个属性的内容的结构："
#. Tag: programlisting
#: J2EE_Connectors_On_JBOSS.xml:139
@@ -452,6 +478,8 @@
"<literal>java.beans.PropertyEditor</literal> class for the "
"<literal>AttrXType</literal>."
msgstr ""
+"<literal>AttrXName</literal> 是第 X 个属性名，<literal>AttrXType</"
+"literal> 是该属性的权限定名，而 <literal>AttrXValue</literal> 是其字符串形式。从字符串到 <literal>AttrXType</literal> 的转换是通过 <literal>AttrXType</literal> 的 <literal>java.beans.PropertyEditor</literal> 类完成的。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:145
@@ -467,12 +495,14 @@
"outside of the JBoss server VM. In the future this restriction may be "
"configurable."
msgstr ""
+"<emphasis role=\"bold\">JndiName</emphasis>：这是可用资源适配器对应的 JNDI 名称。资源适配器的客户端使用这个名称来获取 <literal>javax.resource.cci."
+"ConnectionFactory</literal> 或资源适配器专有的连接工厂。完整的 JNDI 名称将是<literal>java:/<JndiName></literal>，表示 <literal>JndiName</literal> 属性值将以 <literal>java:/</literal> 为前缀。这阻止了在 JBoss 服务器 VM 外面使用连接工厂。将来这个限制可能是可配置的。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:153
#, no-c-format
msgid "JBossManagedConnectionPool MBean"
-msgstr ""
+msgstr "JBossManagedConnectionPool MBean"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:154
@@ -899,7 +929,7 @@
"<emphasis role=\"bold\">transaction-support</emphasis>: The level of "
"transaction support, here defined as <literal>NoTransaction</literal>, "
"meaning the file system resource adaptor does not do transactional work."
-msgstr ""
+msgstr "<emphasis role=\"bold\">transaction-support</emphasis>：事务支持的级别，这里定因为 <literal>NoTransaction</literal>，表示文件系统资源适配器不进行事务性的操作。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:305
@@ -912,12 +942,15 @@
"\"A_Sample_Skeleton_JCA_Resource_Adaptor-The_notxfs_ds."
"xml_resource_adaptor_MBeans_service_descriptor.\"/>."
msgstr ""
+"RAR 类和部署描述符只定义了一个资源适配器。要使用这个资源适配器，它必须用一个 <literal>ds.xml</literal> 描述文件集成到 JBoss 应用服务器里。<xref linkend="
+"\"A_Sample_Skeleton_JCA_Resource_Adaptor-The_notxfs_ds."
+"xml_resource_adaptor_MBeans_service_descriptor.\"/> 显示了一个文件系统适配器的例子。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:308
#, no-c-format
msgid "The notxfs-ds.xml resource adaptor MBeans service descriptor."
-msgstr ""
+msgstr "notxfs-ds.xml 是资源适配器 MBean 的服务器描述符。"
#. Tag: programlisting
#: J2EE_Connectors_On_JBOSS.xml:309
@@ -943,6 +976,25 @@
" </no-tx-connection-factory>\n"
"</connection-factories>"
msgstr ""
+"<!DOCTYPE connection-factories PUBLIC\n"
+" \"-//JBoss//DTD JBOSS JCA Config 1.5//EN\"\n"
+" \"http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd\">\n"
+"<!-- \n"
+" The non-transaction FileSystem resource adaptor service "
+"configuration\n"
+"-->\n"
+"<connection-factories>\n"
+" <no-tx-connection-factory>\n"
+" <jndi-name>NoTransFS</jndi-name>\n"
+" <rar-name>jca-ex1.rar</rar-name>\n"
+" <connection-definition>\n"
+" org.jboss.book.jca.ex1.ra.DirContextFactory\n"
+" </connection-definition>\n"
+" <config-property name=\"FileSystemRootDir\"\n"
+" type=\"java.lang.String\">/tmp/db/fs_store</"
+"config-property>\n"
+" </no-tx-connection-factory>\n"
+"</connection-factories>"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:310
@@ -1032,6 +1084,8 @@
"connection, and then immediately closes the connection. The <literal>echo</"
"literal> method code is shown below."
msgstr ""
+"现在我们想通过一个 J2EE 组件测试对资源适配器的访问。为了实现这一点，我们创建了一个临时的 session bean，它只有一个方法 <literal>echo</literal>。在 <literal>echo</literal> 方法内部，EJB 访问资源适配器连接工厂，创建一个连接，然后马上关闭这个连接。下面是 <literal>echo</"
+"literal> 方法的内容。"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:345
@@ -1039,7 +1093,7 @@
msgid ""
"The stateless session bean echo method code that shows the access of the "
"resource adaptor connection factory."
-msgstr ""
+msgstr "stateless session bean 的 echo 方法的代码演示了对资源适配器连接工厂的访问。"
#. Tag: programlisting
#: J2EE_Connectors_On_JBOSS.xml:346
@@ -1092,6 +1146,7 @@
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:347
#, no-c-format
+#, fuzzy
msgid ""
"The EJB is not using the CCI interface to access the resource adaptor. "
"Rather, it is using the resource adaptor specific API based on the "
@@ -1102,7 +1157,7 @@
"and closing the connection. The EJB does not actually do anything with the "
"connection, as this would only exercise the resource adaptor implementation "
"since this is a non-transactional resource."
-msgstr ""
+msgstr "这个 EJB "
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:350
@@ -1425,9 +1480,9 @@
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:487
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The non-transactional DataSource configuration schema"
-msgstr "The JBoss installer security configuration screen"
+msgstr "非事务性的数据源配置模式"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:495
@@ -1437,21 +1492,21 @@
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:503
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The XA DataSource configuration schema"
-msgstr "The JBoss AS installer configuration sets"
+msgstr "XA 数据源配置模式"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:511
#, no-c-format
msgid "The schema for the experimental non-XA DataSource with failover"
-msgstr ""
+msgstr "用于带有失效切换的实验性的非 XA 数据源的模式"
#. Tag: title
#: J2EE_Connectors_On_JBOSS.xml:519
#, no-c-format
msgid "The schema for the experimental XA Datasource with failover"
-msgstr ""
+msgstr "用于带有失效切换的实验性的 XA 数据源的模式"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:526
@@ -1610,7 +1665,7 @@
"statement that should be run on a connection before it is returned from the "
"pool to test its validity to test for stale pool connections. An example "
"statement could be: <literal>select count(*) from x</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">check-valid-connection-sql</emphasis>：这是一个 SQL 语句，它在连接从连接池返回前运行来测试其有效性从而检测过时的连接。示例语句是：<literal>select count(*) from x</literal>。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:596
@@ -1892,13 +1947,11 @@
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:743
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">url-delimeter</emphasis>: This element specifies a "
"character used to separate multiple JDBC URLs."
-msgstr ""
-"<emphasis role=\"bold\">description</emphasis>：这个元素指定操作的易读的描"
-"述。"
+msgstr "<emphasis role=\"bold\">url-delimeter</emphasis>：这个元素指定用来分隔多个 JDBC URL 的字符。"
#. Tag: para
#: J2EE_Connectors_On_JBOSS.xml:748
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Naming.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Naming.po 2009-03-16 03:43:17 UTC (rev 85870)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Naming.po 2009-03-16 04:07:46 UTC (rev 85871)
@@ -9,8 +9,8 @@
"Project-Id-Version: Naming\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-03-10 10:41+1000\n"
-"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"PO-Revision-Date: 2009-03-16 14:06+1000\n"
+"Last-Translator: Xi HUANG\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -3623,91 +3623,89 @@
#. Tag: para
#: Naming.xml:880
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"An optional <emphasis role=\"bold\">description</emphasis> element that "
"provides a description of the entry"
-msgstr "<emphasis role=\"bold\">description</emphasis>：参数的可选描述。"
+msgstr "提供条目的描述的可选 <emphasis role=\"bold\">description</emphasis> 元素。"
#. Tag: para
#: Naming.xml:885
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"An <emphasis role=\"bold\">env-entry-name</emphasis> element giving the name "
"of the entry relative to <literal>java:comp/env</literal>"
-msgstr ""
-"<emphasis role=\"bold\">PartitionName</emphasis> 指定了部署这个 farm 的群集的"
-"名字。它的缺省值是 <literal>DefaultPartition</literal>。"
+msgstr "指定相对于 <literal>java:comp/env</literal> 的条目名称的 <emphasis role=\"bold\">env-entry-name</emphasis> 元素"
#. Tag: para
#: Naming.xml:890
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"An <emphasis role=\"bold\">env-entry-type</emphasis> element giving the Java "
"type of the entry value that must be one of:"
-msgstr "<emphasis role=\"bold\">Never</emphasis>：属性值永远都不要持久化"
+msgstr "指定条目值必须为下列值之一的 <emphasis role=\"bold\">env-entry-type</emphasis> 元素："
#. Tag: literal
#: Naming.xml:894
#, no-c-format
msgid "java.lang.Byte"
-msgstr ""
+msgstr "java.lang.Byte"
#. Tag: literal
#: Naming.xml:899
#, no-c-format
msgid "java.lang.Boolean"
-msgstr ""
+msgstr "java.lang.Boolean"
#. Tag: literal
#: Naming.xml:904
#, no-c-format
msgid "java.lang.Character"
-msgstr ""
+msgstr "java.lang.Character"
#. Tag: literal
#: Naming.xml:909
#, no-c-format
msgid "java.lang.Double"
-msgstr ""
+msgstr "java.lang.Double"
#. Tag: literal
#: Naming.xml:914
#, no-c-format
msgid "java.lang.Float"
-msgstr ""
+msgstr "java.lang.Float"
#. Tag: literal
#: Naming.xml:919
#, no-c-format
msgid "java.lang.Integer"
-msgstr ""
+msgstr "java.lang.Integer"
#. Tag: literal
#: Naming.xml:924
#, no-c-format
msgid "java.lang.Long"
-msgstr ""
+msgstr "java.lang.Long"
#. Tag: literal
#: Naming.xml:929
#, no-c-format
msgid "java.lang.Short"
-msgstr ""
+msgstr "java.lang.Short"
#. Tag: literal
#: Naming.xml:934
#, no-c-format
msgid "java.lang.String"
-msgstr ""
+msgstr "java.lang.String"
#. Tag: para
#: Naming.xml:941
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"An <emphasis role=\"bold\">env-entry-value</emphasis> element giving the "
"value of entry as a string"
-msgstr "<emphasis role=\"bold\">name</emphasis>：这个元素包含操作的名字。"
+msgstr "给出条目值的字符串形式的 <emphasis role=\"bold\">env-entry-value</emphasis> 元素"
#. Tag: para
#: Naming.xml:946
@@ -3728,7 +3726,7 @@
#: Naming.xml:949
#, no-c-format
msgid "An example ejb-jar.xml env-entry fragment"
-msgstr ""
+msgstr "ejb-jar.xml 的 env-entry 代码片段"
#. Tag: programlisting
#: Naming.xml:950
@@ -3754,12 +3752,31 @@
"</session>\n"
"<!-- ... -->"
msgstr ""
+"<!-- ... -->\n"
+"<session>\n"
+" <ejb-name>ASessionBean</ejb-name>\n"
+" <!-- ... -->\n"
+" <env-entry>\n"
+" <description>The maximum number of tax exemptions allowed </"
+"description>\n"
+" <env-entry-name>maxExemptions</env-entry-name>\n"
+" <env-entry-type>java.lang.Integer</env-entry-type>\n"
+" <env-entry-value>15</env-entry-value>\n"
+" </env-entry>\n"
+" <env-entry>\n"
+" <description>The tax rate </description>\n"
+" <env-entry-name>taxRate</env-entry-name>\n"
+" <env-entry-type>java.lang.Float</env-entry-type>\n"
+" <env-entry-value>0.23</env-entry-value>\n"
+" </env-entry>\n"
+"</session>\n"
+"<!-- ... -->"
#. Tag: title
#: Naming.xml:951
#, no-c-format
msgid "ENC env-entry access code fragment"
-msgstr ""
+msgstr "访问 ENC env-entry 的代码片段"
#. Tag: programlisting
#: Naming.xml:952
@@ -3770,12 +3787,16 @@
"Integer maxExemptions = (Integer) envCtx.lookup(\"maxExemptions\");\n"
"Float taxRate = (Float) envCtx.lookup(\"taxRate\");"
msgstr ""
+"InitialContext iniCtx = new InitialContext();\n"
+"Context envCtx = (Context) iniCtx.lookup(\"java:comp/env\");\n"
+"Integer maxExemptions = (Integer) envCtx.lookup(\"maxExemptions\");\n"
+"Float taxRate = (Float) envCtx.lookup(\"taxRate\");"
#. Tag: title
#: Naming.xml:957
#, no-c-format
msgid "EJB References"
-msgstr ""
+msgstr "EJB 引用"
#. Tag: para
#: Naming.xml:958
@@ -3786,7 +3807,7 @@
"deployment time decision, there needs to be a way for a component developer "
"to declare a reference to an EJB that will be linked by the deployer. EJB "
"references satisfy this requirement."
-msgstr ""
+msgstr "EJB 和 Web 组件和其他 EJB 交互是很常见的。因为 EJB 的 home 接口绑定的 JNDI 名称是在部署时才进行绑定的，组件开发者需要有办法声明一个 EJB 的引用来进行链接。而 EJB 引用就满足这样的要求。就不"
#. Tag: para
#: Naming.xml:961
@@ -3853,11 +3874,11 @@
#. Tag: para
#: Naming.xml:989
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"A <emphasis role=\"bold\">remote</emphasis> element that gives the fully "
"qualified class name of the EJB remote interface."
-msgstr "<emphasis role=\"bold\">name</emphasis>：这个元素包含通知类的类全名。"
+msgstr "指定 EJB 远程接口的权限定名的 <emphasis role=\"bold\">remote</emphasis> 元素。"
#. Tag: para
#: Naming.xml:994
@@ -3988,7 +4009,7 @@
#: Naming.xml:1004
#, no-c-format
msgid "ENC ejb-ref access code fragment"
-msgstr ""
+msgstr "访问 ENC ejb-ref 的代码片段"
#. Tag: programlisting
#: Naming.xml:1005
@@ -4006,13 +4027,13 @@
#. Tag: title
#: Naming.xml:1010
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"EJB References with <literal>jboss.xml</literal> and <literal>jboss-web.xml</"
"literal>"
msgstr ""
-"JBoss JMX jar 和 GNU regex jar, <literal>jboss-jmx.jar</literal> 和 "
-"<literal>gnu-regexp.jar</literal>。"
+"<literal>jboss.xml</literal> 和 <literal>jboss-web.xml</"
+"literal> 里的 EJB 引用"
#. Tag: para
#: Naming.xml:1011
@@ -4794,7 +4815,7 @@
#: Naming.xml:1237
#, no-c-format
msgid "ENC resource-env-ref access code fragment"
-msgstr ""
+msgstr "访问 ENC resource-env-ref 的代码片段"
#. Tag: programlisting
#: Naming.xml:1238
@@ -4817,6 +4838,7 @@
#. Tag: para
#: Naming.xml:1244
#, no-c-format
+#, fuzzy
msgid ""
"The purpose of the JBoss <literal>jboss.xml</literal> EJB deployment "
"descriptor and <literal>jboss-web.xml</literal> Web application deployment "
@@ -4827,7 +4849,7 @@
"literal> or <literal>jboss-web.xml</literal> descriptor. The JBoss "
"<literal>resource-env-ref</literal> element consists of the following child "
"elements:"
-msgstr ""
+msgstr "JBoss <literal>jboss.xml</literal> EJB 部署描述符和 <literal>jboss-web.xml</literal> Web 应用程序部署描述符的目的是提供逻辑名和 JNDI 名称的链接。"
#. Tag: para
#: Naming.xml:1249
More information about the jboss-cvs-commits
mailing list