[jboss-cvs] JBossAS SVN: r67632 - projects/docs/trunk/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Nov 29 18:27:25 EST 2007
Author: xhuang at jboss.com
Date: 2007-11-29 18:27:25 -0500 (Thu, 29 Nov 2007)
New Revision: 67632
Modified:
projects/docs/trunk/Server_Configuration_Guide/zh-CN/Naming.po
Log:
update
Modified: projects/docs/trunk/Server_Configuration_Guide/zh-CN/Naming.po
===================================================================
--- projects/docs/trunk/Server_Configuration_Guide/zh-CN/Naming.po 2007-11-29 22:43:50 UTC (rev 67631)
+++ projects/docs/trunk/Server_Configuration_Guide/zh-CN/Naming.po 2007-11-29 23:27:25 UTC (rev 67632)
@@ -9,7 +9,7 @@
"Project-Id-Version: Naming\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2007-11-05 06:04+0000\n"
-"PO-Revision-Date: 2007-11-26 14:00+1000\n"
+"PO-Revision-Date: 2007-11-30 09:26+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <zh at li.org>\n"
"MIME-Version: 1.0\n"
@@ -3369,6 +3369,7 @@
#. Tag: para
#: Naming.xml:798
#, no-c-format
+#, fuzzy
msgid ""
"JNDI is a fundamental aspect of the J2EE specifications. One key usage is "
"the isolation of J2EE component code from the environment in which the code "
@@ -3380,7 +3381,7 @@
"available to the container components in the form of JNDI Context. The ENC "
"is utilized by the participants involved in the life cycle of a J2EE "
"component in the following ways."
-msgstr ""
+msgstr "JNDI 是 J2EE 规格的一个基本概念。其关键用途是把 J2EE 的组件代码从部署环境中分离。使用应用程序组件的环境允许对组件进行定制而不需要访问或修改组件的源码。应用程序组件环境被称为 ENC，即企业命名上下文。应用程序组件容器负责使 ENC 以 JNDI 上下文的形式为容器组件所使用。ENC "
#. Tag: para
#: Naming.xml:803
@@ -3391,16 +3392,17 @@
"for the component to specify the required ENC entries. The entries are "
"declarations of the information and resources the component requires at "
"runtime."
-msgstr ""
+msgstr "应用程序组件的商业逻辑应该通过 ENC 进行访问。组件提供者使用标准的部署描述符来指定所需的 ENC 条目。这些条目是组件在运行时所需的信息和资源的声明。"
#. Tag: para
#: Naming.xml:808
#, no-c-format
+#, fuzzy
msgid ""
"The container provides tools that allow a deployer of a component to map the "
"ENC references made by the component developer to the deployment environment "
"entity that satisfies the reference."
-msgstr ""
+msgstr "容器提供允许组件部署者"
#. Tag: para
#: Naming.xml:813
@@ -3408,7 +3410,7 @@
msgid ""
"The component deployer utilizes the container tools to ready a component for "
"final deployment."
-msgstr ""
+msgstr "组件部署者利用容器工具来为组件的最后部署作准备。"
#. Tag: para
#: Naming.xml:818
@@ -3416,7 +3418,7 @@
msgid ""
"The component container uses the deployment package information to build the "
"complete component ENC at runtime"
-msgstr ""
+msgstr "组件容器使用部署包信息来构建运行时的完整组件 ENC。"
#. Tag: para
#: Naming.xml:823
@@ -3427,6 +3429,8 @@
"specification is available at <ulink url=\"http://java.sun.com/j2ee/download."
"html\"></ulink>."
msgstr ""
+"关于 J2EE 平台里对 JNDI 的使用可以在 J2EE 1.4 规格的第 5 部分找到。请参考 <ulink url=\"http://java.sun.com/j2ee/download."
+"html\"></ulink> 里的 J2EE 规格。"
#. Tag: para
#: Naming.xml:826
@@ -3442,23 +3446,28 @@
"ENC_access_sample_code\"/> illustrates the prototypical lines of code a "
"component uses to access its ENC."
msgstr ""
+"应用程序组件实例使用 JNDI API 寻找 ENC。应用程序组件实例使用无参数的构造函数并依据 <literal>java:comp/env</literal> 查找命名环境来创建 <literal>javax.naming."
+"InitialContext</literal> 对象。应用程序组件的环境选项直接保存在 ENC 或其子上下文里。<xref linkend="
+"\"J2EE_and_JNDI___The_Application_Component_Environment-"
+"ENC_access_sample_code\"/> 演示了组件用来访问其 ENC 的原型代码。"
#. Tag: title
#: Naming.xml:829
#, no-c-format
msgid "ENC access sample code"
-msgstr ""
+msgstr "关于 ENC 访问的代码示例"
#. Tag: programlisting
#: Naming.xml:830
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"// Obtain the application component's ENC\n"
"Context iniCtx = new InitialContext();\n"
"Context compEnv = (Context) iniCtx.lookup(\"java:comp/env\");"
msgstr ""
-"InitialContext iniCtx = new InitialContext();\n"
-"LdapContext ldapCtx = iniCtx.lookup(\"external/ldap/jboss\");"
+"// Obtain the application component's ENC\n"
+"Context iniCtx = new InitialContext();\n"
+"Context compEnv = (Context) iniCtx.lookup(\"java:comp/env\");"
#. Tag: para
#: Naming.xml:831
@@ -3485,6 +3494,8 @@
"<literal>Web1</literal> may bind the same name to the deployment environment "
"language locale representation of red."
msgstr ""
+"应用程序组件环境是一个本地环境，它只能在应用服务器控制线程和应用程序组件交互时被组件访问。这意味着 EJB <literal>Bean1</literal> 不能够访问 EJB <literal>Bean2</literal> 的 ENC 元素，反之亦然。类似地，Web 应用程序 <literal>Web1</literal> 不能访问 Web 应用程序 <literal>Web2</literal> 或 <literal>Bean1</literal> 或 <literal>Bean2</"
+"literal> 的 ENC 元素。而且，任何客户端代码，不管它是在应用服务器 VM 内部或外部执行，都不能访问组件的 <literal>java:comp</literal> JNDI 上下文。ENC 的目的是提供一种独立的、只读的命名空间，它可以被应用程序组件使用而不用考虑其部署环境的类型。例如，EJB <literal>Bean1</literal> 可以定义 <literal>java:comp/env/red</literal> 来引用 RGB 红色的十六进制值，而 Web 应用程序 <literal>Web1</literal> 可以把相同的名字绑定到代表红色的部署环境语言代码。"
#. Tag: para
#: Naming.xml:834
@@ -3500,7 +3511,7 @@
"available to remote clients, provided the context or object supports "
"serialization. You'll see how the isolation of these naming scopes is "
"achieved in the <xref linkend=\"Naming_on_JBoss-The_JBossNS_Architecture\"/>."
-msgstr ""
+msgstr "在 JBoss 里有 3 个常用的命名作用域级别：<literal>java:comp</literal>、<literal>java:</literal> 及其他。如我们所讨论的，<literal>java:comp</literal> 上下文和其子上下文仅对于和特定上下文相关联的应用程序组件可用。<literal>java:</literal> 的子上下文和直接对象绑定仅在 JBoss 服务器虚拟机里可见，它对于远程客户是不可见的。只要支持串行化，任何其他上下文或者对象绑定都可以为远程客户可用。你将在 <xref linkend=\"Naming_on_JBoss-The_JBossNS_Architecture\"/> 里看到怎样实现这些命名作用域的分离的。"
#. Tag: para
#: Naming.xml:837
@@ -3513,12 +3524,15 @@
"interface would be bound to a globally visible name that should accessible "
"by remote client."
msgstr ""
+"对 <literal>java:</"
+"literal> 上下文绑定限制的一个例子是 <literal>javax.sql.DataSource</"
+"literal> 连接工厂，它只能在相关数据库池所在的 JBoss 服务器内部使用。另一方面，EJB home 接口将绑定到一个全局可见的名字，它可以被远程客户访问。"
#. Tag: title
#: Naming.xml:841
#, no-c-format
msgid "ENC Usage Conventions"
-msgstr ""
+msgstr "ENC 使用约定"
#. Tag: para
#: Naming.xml:842
@@ -3532,40 +3546,40 @@
"different types of information may be stored in and retrieved from JNDI "
"including:"
msgstr ""
+"JNDI 被用作 API 来具体化应用程序组件里的大量信息。应用程序组件用来访问这些信息的 JNDI 名字在 EJB 组件的标准 <literal>ejb-jar.xml</"
+"literal> 部署描述符或者 Web 组件的标准 <literal>web.xml</literal> 部署描述符里进行声明。可以存放在 JNDI 并从中读取的信息包括："
#. Tag: para
#: Naming.xml:847
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Environment entries as declared by the <literal>env-entry</literal> elements"
-msgstr "下列是 <literal>TCP</literal> 元素里的可用属性。"
+msgstr "<literal>env-entry</literal> 元素声明的环境条目"
#. Tag: para
#: Naming.xml:852
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"EJB references as declared by <literal>ejb-ref</literal> and <literal>ejb-"
"local-ref</literal> elements."
-msgstr "通过 <literal>get()</literal> 或 <literal>load()</literal> 方法取得数据。"
+msgstr ""
+"<literal>ejb-ref</literal> 和 <literal>ejb-"
+"local-ref</literal> 元素声明的 EJB 引用。"
#. Tag: para
#: Naming.xml:857
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Resource manager connection factory references as declared by the "
"<literal>resource-ref</literal> elements"
-msgstr ""
-"持久化对象之间一对一的关联关系是通过 <literal>one-to-one</literal> 元素定义"
-"的。"
+msgstr "<literal>resource-ref</literal> 元素声明了对资源管理者连接工厂的引用"
#. Tag: para
#: Naming.xml:862
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Resource environment references as declared by the <literal>resource-env-"
"ref</literal> elements"
-msgstr ""
-"持久化对象之间一对一的关联关系是通过 <literal>one-to-one</literal> 元素定义"
-"的。"
+msgstr "<literal>resource-env-ref</literal> 元素声明了对资源环境的引用"
#. Tag: para
#: Naming.xml:867
More information about the jboss-cvs-commits
mailing list