[jboss-cvs] JBossAS SVN: r67435 - projects/docs/trunk/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Nov 25 23:01:53 EST 2007
Author: xhuang at jboss.com
Date: 2007-11-25 23:01:53 -0500 (Sun, 25 Nov 2007)
New Revision: 67435
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-26 03:51:42 UTC (rev 67434)
+++ projects/docs/trunk/Server_Configuration_Guide/zh-CN/Naming.po 2007-11-26 04:01:53 UTC (rev 67435)
@@ -1,18 +1,21 @@
+# translation of Naming.po to
# Language /tmp/mike/JBEAP420/JBAS translations for JBEAP package.
# Copyright (C) 2007 Free Software Foundation, Inc.
+#
# Automatically generated, 2007.
-#
+# Xi HUANG <xhuang at redhat.com>, 2007.
msgid ""
msgstr ""
-"Project-Id-Version: JBEAP 420\n"
+"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: 2001-02-09 01:25+0100\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2007-11-26 14:00+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: <zh at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: Naming.xml:6
@@ -141,7 +144,7 @@
#. Tag: para
#: Naming.xml:30
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"As an example, consider the Unix file system's naming convention. Each "
"file is named from its path relative to the root of the file system, with "
@@ -157,7 +160,7 @@
"的相对路径来命名，路径里的每一部分都用斜杠(\"<literal>/</literal>\")来分隔。"
"文件路径从左至右排列。例如，<literal>/usr/jboss/readme.txt</literal>，命名了"
"文件系统的根目录下的目录 <literal>usr</literal> 下的子目录 <literal>jboss</"
-"literal> 里的一个 <literal>readme.txt</literal> 文件。JBoss 命名把 UNIX 风格"
+"literal> 里的一个 <literal>readme.txt</literal> 文件。JBoss 把 UNIX 风格"
"的命名空间作为它的命名规则。"
#. Tag: para
@@ -315,35 +318,33 @@
#. Tag: para
#: Naming.xml:58
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"When you create an <literal>InitialContext</literal>, it is initialized with "
"properties from the environment. JNDI determines each property's value "
"by merging the values from the following two sources, in order."
msgstr ""
"当你创建一个 <literal>InitialContext</literal> 时，它将用系统环境里的属性进行"
-"初始化。JNDI 通过合并下面两个来源的值来按顺序决定每一个属性值。"
+"初始化。JNDI 通过合并下面两个来源的值来按顺序决定每一个属性值。 "
#. Tag: para
#: Naming.xml:63
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The first occurrence of the property from the constructor's environment "
"parameter and (for appropriate properties) the applet parameters and system "
"properties."
-msgstr "构造函数的环境参数和(对合适的属性而言) applet 参数以及系统属性。"
+msgstr "构造函数的环境参数和(对合适的属性而言) applet 参数以及系统属性。 "
#. Tag: para
#: Naming.xml:68
#, no-c-format
-msgid ""
-"All <literal>jndi.properties</literal> resource files found on the classpath."
-msgstr ""
-"在 classpath 上发现的所有 <literal>jndi.properties</literal> 资源文件。"
+msgid "All <literal>jndi.properties</literal> resource files found on the classpath."
+msgstr "在 classpath 上发现的所有 <literal>jndi.properties</literal> 资源文件。"
#. Tag: para
#: Naming.xml:73
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"For each property found in both of these two sources, the property's "
"value is determined as follows. If the property is one of the standard JNDI "
@@ -359,7 +360,7 @@
"JNDI 工厂(factories)的列表的标准 JNDI 属性之一，所有的值都连成一个用冒号隔开"
"的列表。对于其他属性，只使用第一个被发现的值。指定 JNDI 环境属性的首选方法是"
"通过 <literal>jndi.properties</literal> 文件，它允许你的代码独立于与 JNDI 提"
-"供者相关的信息，这样当修改 JNDI 提供者时，你将不需要修改代码或者重新编译。"
+"供者相关的信息，这样当修改 JNDI 提供者时，你将不需要修改代码或者重新编译。 "
#. Tag: para
#: Naming.xml:76
@@ -423,7 +424,7 @@
#. Tag: para
#: Naming.xml:93
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The JBossNS architecture is a Java socket/RMI based implementation of the "
"<literal>javax.naming.Context</literal> interface. It is a client/server "
@@ -438,8 +439,8 @@
"JBossNS 架构是一个基于 Java socket/RMI 的 <literal>javax.naming.Context</"
"literal> 接口的应用。它是一个可以远程访问的客户端/服务器实现。这个实现进行了"
"优化，使得 JBossNS 服务器运行的同一 VM 内的访问不需要调用套接字。同一 VM 内的"
-"访问通过一个作为全局 singleton 的可用的对象引用来实现。<xref linkend=\"ch3."
-"jbossns.fig\"/> 说明了 JBossNS 实现里的一些关键类和它们的关系。"
+"访问通过一个作为全局 singleton 的可用的对象引用来实现。<xref linkend="
+"\"The_JBossNS_Architecture-Key_components_in_the_JBossNS_architecture.\"/> 说明了 JBossNS 实现里的一些关键类和它们的关系。"
#. Tag: title
#: Naming.xml:97
@@ -599,7 +600,7 @@
#. Tag: para
#: Naming.xml:152
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"If a context instance does not exist for the class loader instance, one is "
"created and associated with that class loader in the <literal>ENCFactory</"
@@ -610,7 +611,7 @@
"如果这个类加载器实例的上下文实例不存在，将创建一个上下文实例并和 "
"<literal>ENCFactory</literal> 映射里的类加载器关联。因此，应用程序组件的 ENC "
"的正确隔离依赖于每个组件都接收一个独立的与组件执行线程关联的 "
-"<literal>ClassLoader</literal>。"
+"<literal>ClassLoader</literal>。 "
#. Tag: para
#: Naming.xml:155
@@ -659,7 +660,7 @@
#. Tag: para
#: Naming.xml:161
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The details of threads and the thread context class loader won't be "
"explored here, but the JNDI tutorial provides a concise discussion that is "
@@ -668,7 +669,7 @@
msgstr ""
"线程和线程类加载器的细节不会在这里探讨，但 JNDI tutorial 提供了一个合适的简要"
"讨论。细节请参考 <ulink url=\"http://java.sun.com/products/jndi/tutorial/"
-"beyond/misc/classloader.html\"></ulink>。"
+"beyond/misc/classloader.html\"></ulink>。 "
#. Tag: para
#: Naming.xml:164
@@ -693,7 +694,7 @@
#. Tag: para
#: Naming.xml:174
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Exports the <literal>NamingServer</literal> instance's <literal>org.jnp."
"naming.interfaces.Naming</literal> RMI interface using the configured "
@@ -701,9 +702,9 @@
"<literal>ServerSocketFactory</literal>attributes."
msgstr ""
"用配置好的 <literal>RmiPort</literal>，<literal>ClientSocketFactory</"
-"literal>，<literal>ServerSocketFactory</literal> 属性开放 "
+"literal>，<literal>ServerSocketFactory</literal> 属性导出 "
"<literal>NamingServer</literal> 实例的 <literal>org.jnp.naming.interfaces."
-"Naming</literal> RMI 接口。"
+"Naming</literal> RMI 接口。 "
#. Tag: para
#: Naming.xml:179
@@ -1032,7 +1033,7 @@
#. Tag: para
#: Naming.xml:270
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"When running in a clustered JBoss environment, you can choose not to specify "
"a <literal>Context.PROVIDER_URL</literal> value and let the client query the "
@@ -1054,7 +1055,7 @@
"literal> 服务的配置运行时才可行。发现(discovery)过程由发送多点传送请求包到发"
"现地址/端口和等待接点应答组成。这个应答是 <literal>Naming</literal> 接口的一"
"个 HA-RMI 版本。下面的 <literal>InitialContext</literal> 属性影响了发现的配"
-"置："
+"置： "
#. Tag: para
#: Naming.xml:275
@@ -1125,7 +1126,7 @@
#. Tag: para
#: Naming.xml:304
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The JNDI naming service can be accessed over HTTP. From a JNDI client's "
"perspective this is a transparent change as they continue to use the JNDI "
@@ -1142,7 +1143,7 @@
"literal> 接口的操作被翻译成发送到 servlet 的 HTTP posts，这个 servlet 用它的 "
"JMX 调用操作把请求传入 NamingService。把 HTTP 当做访问协议的优势包括更好的经"
"由防火墙和代理服务器的访问，以及用标准的基于 servlet 角色的安全性来使对 JNDI "
-"服务的访问更加安全。"
+"服务的访问更加安全。 "
#. Tag: para
#: Naming.xml:307
@@ -1230,7 +1231,7 @@
#. Tag: para
#: Naming.xml:347
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The JNDI <literal>Context</literal> implementation returned by the "
"<literal>HttpNamingContextFactory</literal> is a proxy that delegates "
@@ -1252,7 +1253,8 @@
"有一个众所周知的公用接口，这个值可能已经被绑定在服务器端了。如果 JBoss web 服"
"务器处于一个或多个防火墙或代理服务器后面，这个代理就不可能知道它要求的 URL 是"
"什么。在这种情况下，代理将与一个必须在客户端设置的系统属性值相关联。请参考 "
-"<xref linkend=\"ch3.accessingjndi\"/> 里关于 HTTP 上的 JNDI 操作的更多信息。"
+"<xref linkend="
+"\"JNDI_over_HTTP-Accessing_JNDI_over_HTTP\"/> 里关于 HTTP 上的 JNDI 操作的更多信息。"
#. Tag: title
#: Naming.xml:353
@@ -1262,7 +1264,7 @@
#. Tag: para
#: Naming.xml:354
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"JAAS is the preferred method for authenticating a remote client to JBoss. "
"However, for simplicity and to ease the migration from other application "
@@ -1274,7 +1276,7 @@
"JAAS 是验证 JBoss 的远程客户的首选方法。然而，基于简单性和使不使用 JAAS 的其"
"他应用服务器环境的移植更加轻松，JBoss 允许你通过 <literal>InitialContext</"
"literal> 验证安全性凭据(security credentials)。虽然 JAAS 仍旧被使用，但在客户"
-"应用程序里 JAAS 接口的应用并不常见。"
+"应用程序里 JAAS 接口的应用并不常见。 "
#. Tag: para
#: Naming.xml:357
@@ -1366,7 +1368,7 @@
#. Tag: para
#: Naming.xml:396
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"When using Sun's CosNaming it is necessary to use a different naming "
"context factory from the default. CosNaming looks for the ORB in JNDI "
@@ -1380,7 +1382,7 @@
"CosNaming 在 JNDI 里查找 ORB 而不是使用 <literal>deploy/iiop-service.xml?</"
"literal> 里配置的 ORB。你有必要把全局的上下文工厂设置为 <literal>org.jboss."
"iiop.naming.ORBInitialContextFactory</literal>，它会把 ORB 设置成 JBoss 的 "
-"ORB。这是在 <literal>conf/jndi.propeties</literal> 文件里完成的："
+"ORB。这是在 <literal>conf/jndi.propeties</literal> 文件里完成的： "
#. Tag: programlisting
#: Naming.xml:399
@@ -1440,7 +1442,7 @@
#. Tag: programlisting
#: Naming.xml:417
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">http-invoker.sar</emphasis>\n"
"+- META-INF/jboss-service.xml\n"
@@ -1464,8 +1466,6 @@
"class\n"
"| +- WEB-INF/classes/org/jboss/invocation/http/servlet/ReadOnlyAccessFilter."
"class\n"
-"| +- WEB-INF/classes/roles.properties\n"
-"| +- WEB-INF/classes/users.properties\n"
"| +- WEB-INF/web.xml\n"
"| +- META-INF/MANIFEST.MF\n"
"+- META-INF/MANIFEST.MF"
@@ -1511,7 +1511,7 @@
#. Tag: para
#: Naming.xml:432
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Before looking at the configurations let's look at the operation of the "
"<literal>http-invoker</literal> services. <xref linkend="
@@ -1529,7 +1529,9 @@
"literal> interface implementation."
msgstr ""
"在阅读这个配置之前，让我们来看看 <literal>http-invoker</literal> 服务的操作。"
-"<xref linkend=\"ch3.httpinvoker.fig\"/> 展示了 JBoss JNDI 代理和它和 "
+"<xref linkend="
+"\"Accessing_JNDI_over_HTTP-"
+"The_HTTP_invoker_proxyserver_structure_for_a_JNDI_Context\"/> 展示了 JBoss JNDI 代理和它和 "
"<literal>http-invoker</literal> 的 JBoss 服务器端组件之间的关系的逻辑视图。"
"把 <literal>Context.INITIAL_CONTEXT_FACTORY</literal> 属性设置为 "
"<literal>org.jboss.naming.HttpNamingContextFactory</literal> 并把 "
@@ -1541,7 +1543,7 @@
#. Tag: para
#: Naming.xml:435
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The proxy is an instance of <literal>org.jboss.invocation.http.interfaces."
"HttpInvokerProxy</literal>, and implements the <literal>org.jnp.interfaces."
@@ -1558,11 +1560,11 @@
"posts 对 <literal>InvokerServlet</literal> 的 <literal>Naming</literal> 接口"
"方法调用打包。<literal>InvokerServlet</literal> 把这些 posts 翻译成对 "
"<literal>NamingService</literal> 的 JMX 调用，并把调用结果返回给 HTTP post 响"
-"应里的代理。"
+"应里的代理。 "
#. Tag: para
#: Naming.xml:438
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"There are several configuration values that need to be set to tie all of "
"these components together and <xref linkend=\"Accessing_JNDI_over_HTTP-"
@@ -1570,8 +1572,8 @@
"illustrates the relationship between configuration files and the "
"corresponding components."
msgstr ""
-"有几个配置的值需要设置成与所有的组件相关联，<xref linkend=\"ch3.httpjndiconf."
-"fig\"/> 说明了配置文件和对应的组件之间的关系。"
+"有几个配置的值需要设置成与所有的组件相关联，<xref linkend=\"Accessing_JNDI_over_HTTP-"
+"The_relationship_between_configuration_files_and_JNDIHTTP_component\"/> 说明了配置文件和对应的组件之间的关系。"
#. Tag: title
#: Naming.xml:442
@@ -1696,7 +1698,7 @@
#. Tag: para
#: Naming.xml:485
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">JndiName</emphasis>: The name in JNDI under which "
"the proxy is bound. This needs to be set to a blank/empty string to indicate "
@@ -1706,11 +1708,11 @@
msgstr ""
"<emphasis role=\"bold\">JndiName</emphasis>：代理所绑定的 JNDI 名。如果接口不"
"应该绑定 JNDI，这个值应设为空串。我们不能够使用 JNDI 引导它自己，这是 "
-"<literal>NamingFactoryServlet</literal> 的任务。"
+"<literal>NamingFactoryServlet</literal> 的任务。 "
#. Tag: para
#: Naming.xml:490
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>http-invoker.sar/invoker.war/WEB-INF/web.xml</literal> "
"descriptor defines the mappings of the <literal>NamingFactoryServlet</"
@@ -1723,7 +1725,7 @@
"<literal>NamingFactoryServlet</literal> 和 <literal>InvokerServlet</literal> "
"以及它们 <literal>NamingFactoryServlet</literal> 的初始参数的映射关系。"
"<literal>JNDIFactory</literal> 条目是和 JNDI/HTTP 相关的 "
-"<literal>NamingFactoryServlet</literal> 的配置，它定义了："
+"<literal>NamingFactoryServlet</literal> 的配置，它定义了： "
#. Tag: para
#: Naming.xml:495
@@ -1746,14 +1748,14 @@
#. Tag: para
#: Naming.xml:500
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"A proxy initialization parameter that defines the name of the "
"<literal>namingProxyMBean</literal> attribute to query for the Naming proxy "
"value. This defaults to an attribute name of <literal>Proxy</literal>."
msgstr ""
"一个定义 <literal>namingProxyMBean</literal> 属性名来查询命名代理值的的代理初"
-"始参数，它缺省为 <literal>Proxy</literal> 的一个属性名。"
+"始参数，它缺省为 <literal>Proxy</literal> 的一个属性名。 "
#. Tag: para
#: Naming.xml:505
@@ -1821,7 +1823,7 @@
#. Tag: para
#: Naming.xml:527
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"We also provide a configuration of the <literal>HttpProxyFactory</literal> "
"setup to use an HTTPS URL. The following example shows the section of the "
@@ -1835,11 +1837,11 @@
"URL。下面的示例展示了提供这个配置的 <literal>http-invoker.sar</literal> "
"<literal>jboss-service.xml</literal> 描述符。所有和标准的 HTTP 配置相关的改动"
"是 <literal>InvokerURLPrefix</literal> 和 <literal>InvokerURLSuffix</"
-"literal> 属性，它们用 8443 端口设置了一个 HTTPS URL。"
+"literal> 属性，它们用 8443 端口设置了一个 HTTPS URL。 "
#. Tag: programlisting
#: Naming.xml:530
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<!-- Expose the Naming service interface via HTTPS -->\n"
"<mbean code=\"org.jboss.invocation.http.server.HttpProxyFactory\" \n"
@@ -1880,28 +1882,30 @@
" <!-- Compose the invoker URL from the cluster node address -->\n"
" <attribute name=\"InvokerURLPrefix\">https://</attribute>\n"
" <attribute name=\"InvokerURLSuffix\">:8443/invoker/"
-"JMXInvokerServlet </attribute>\n"
+"JMXInvokerServlet \n"
+"</attribute>\n"
" <attribute name=\"UseHostName\">true</attribute>\n"
-" <attribute name=\"ExportedInterface\">org.jnp.interfaces.Naming "
+" <attribute name=\"ExportedInterface\">org.jnp.interfaces.Naming \n"
"</attribute>\n"
" <attribute name=\"JndiName\"/>\n"
" <attribute name=\"ClientInterceptors\">\n"
" <interceptors>\n"
-" <interceptor>org.jboss.proxy.ClientMethodInterceptor </"
-"interceptor>\n"
-" <interceptor>org.jboss.proxy.SecurityInterceptor</"
-"interceptor>\n"
+" <interceptor>org.jboss.proxy.ClientMethodInterceptor \n"
+"</interceptor>\n"
+" <interceptor>org.jboss.proxy.SecurityInterceptor\n"
+"</interceptor>\n"
" <interceptor>org.jboss.naming.interceptors."
-"ExceptionInterceptor </interceptor>\n"
-" <interceptor>org.jboss.invocation.InvokerInterceptor </"
-"interceptor>\n"
+"ExceptionInterceptor \n"
+"</interceptor>\n"
+" <interceptor>org.jboss.invocation.InvokerInterceptor \n"
+"</interceptor>\n"
" </interceptors>\n"
" </attribute>\n"
"</mbean>"
#. Tag: para
#: Naming.xml:531
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"At a minimum, a JNDI client using HTTPS requires setting up a HTTPS URL "
"protocol handler. We will be using the Java Secure Socket Extension (JSSE) "
@@ -1912,7 +1916,8 @@
msgstr ""
"使用 JNDI 的客户要求最少设置一个 HTTPS URL 协议的处理程序。我们将为 HTTPS 使"
"用 Java Secure Socket Extension (JSSE)。JSSE 文档很好地描述了使用 HTTPS 所必"
-"需的事情，配置 <xref linkend=\"ch3.jndiclienthttps.ex\"/> 里的示例客户需要下"
+"需的事情，配置 <xref linkend=\"Accessing_JNDI_over_HTTPS-"
+"A_JNDI_client_that_uses_HTTPS_as_the_transport\"/> 里的示例客户需要下"
"面的步骤："
#. Tag: para
@@ -2084,7 +2089,7 @@
#. Tag: programlisting
#: Naming.xml:569
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"[examples]$ ant -Dchap=naming -Dex=1 run-example\n"
"...\n"
@@ -2100,12 +2105,12 @@
"[examples]$ ant -Dchap=naming -Dex=1 run-example\n"
"...\n"
"run-example1:\n"
-" [java] Created InitialContext, env={java.naming.provider.url=https://"
-"localhost:8443/invo\n"
-"ker/JNDIFactorySSL, java.naming.factory.initial=org.jboss.naming."
-"HttpNamingContextFactory}\n"
-" [java] lookup(jmx/invoker/RMIAdaptor): org.jboss.invocation.jrmp."
-"interfaces.JRMPInvokerP\n"
+"\n"
+"[java] Created InitialContext, env={java.naming. \\ \n"
+"provider.url=https://localhost:8443/invoker/JNDIFactorySSL, java.naming. \\\n"
+"factory.initial=org.jboss.naming.HttpNamingContextFactory}\n"
+" [java] lookup(jmx/invoker/RMIAdaptor): org.jboss.invocation.jrmp. \\\n"
+" interfaces.JRMPInvokerP\n"
"roxy at cac3fa"
#. Tag: title
@@ -2116,7 +2121,7 @@
#. Tag: para
#: Naming.xml:574
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"One benefit to accessing JNDI over HTTP is that it is easy to secure access "
"to the JNDI <literal>InitialContext</literal> factory as well as the naming "
@@ -2140,17 +2145,15 @@
"<literal>all</literal> 里的 <literal>http-invoker.sar/invoker.war</literal> "
"目录下。要启用对 JNDI 的安全访问，你需要编辑 <literal>invoker.war/WEB-INF/"
"web.xml</literal> 描述符并删除所有的不安全的 servlet 映射。例如，如果用户已经"
-"被验证并充当 <literal>HttpInvoker</literal> 的角色时，<xref linkend=\"ch3."
-"webxmlsec.ex\"/> 里展示的 <literal>web.xml</literal> 描述符只允许对 "
+"被验证并充当 <literal>HttpInvoker</literal> 的角色时，<xref linkend=\"Securing_Access_to_JNDI_over_HTTP-An_example_web."
+"xml_descriptor_for_secured_access_to_the_JNDI_servlets\"/> 描述符只允许对 "
"<literal>invoker.war</literal> servlets 的访问。"
#. Tag: title
#: Naming.xml:577
-#, fuzzy, no-c-format
+#, no-c-format
msgid "An example web.xml descriptor for secured access to the JNDI servlets"
-msgstr ""
-"An example jboss-app.xml descriptor for enabled scoped class loading at the "
-"EAR level."
+msgstr "用于 JNDI servlet 安全控制的示例 web.xml 描述符"
#. Tag: programlisting
#: Naming.xml:578
@@ -2307,7 +2310,7 @@
#. Tag: para
#: Naming.xml:583
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The <literal>security-domain</literal> element defines the name of the "
"security domain that will be used for the JAAS login module configuration "
@@ -2317,8 +2320,9 @@
"domain name."
msgstr ""
"<literal>security-domain</literal> 元素定义安全领域的名字，用于验证和授权的 "
-"JAAS 登录(login module)模块配置将使用它。请参考 <xref linkend=\"ch8."
-"declarativesecurity.sect\"/> 里关于安全领域的含义和配置的详细内容。"
+"JAAS 登录(login module)模块配置将使用它。请参考 <xref linkend="
+"\"J2EE_Declarative_Security_Overview-Enabling_Declarative_Security_in_JBoss"
+"\"/> 里关于安全领域的含义和配置的详细内容。"
#. Tag: title
#: Naming.xml:589
@@ -2328,7 +2332,7 @@
#. Tag: para
#: Naming.xml:590
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Another feature available for the JNDI/HTTP naming service is the ability to "
"define a context that can be accessed by unauthenticated users in read-only "
@@ -2340,7 +2344,7 @@
"JNDI/HTTP 命名服务的另外一个可用特征是定义可以在只读模式被未验证的客户访问的"
"上下文的能力。这对于验证层(authentication layer)使用的服务来说很重要。例如，"
"<literal>SRPLoginModule</literal> 需要查找用来执行验证的 SRP 服务器接口。现在"
-"我们来看看只读的 JNDI 在 JBoss 里是怎么工作的。"
+"我们来看看只读的 JNDI 在 JBoss 里是怎么工作的。 "
#. Tag: para
#: Naming.xml:593
@@ -2356,7 +2360,7 @@
#. Tag: programlisting
#: Naming.xml:596
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<servlet>\n"
" <servlet-name>ReadOnlyJNDIFactory</servlet-name>\n"
@@ -2395,7 +2399,7 @@
"stub\n"
" through http, but only for a single read-only context. The return "
"content \n"
-" is serialized MarshalledValue containg the org.jnp.interfaces."
+" is serialized MarshalledValue containing the org.jnp.interfaces."
"Naming \n"
" stub.\n"
" </description>\n"
@@ -2635,7 +2639,7 @@
#. Tag: para
#: Naming.xml:609
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Attempts to look up any objects outside of the readonly context will fail. "
"Note that JBoss doesn't ship with any data in the <literal>readonly</"
@@ -2644,7 +2648,7 @@
msgstr ""
"查找在只读上下文之外的任何对象都会失败。注意 JBoss 并不带有 "
"<literal>readonly</literal> 上下文里的任何数据，所以除非你创建它，否则只读上"
-"下文不会被绑定。"
+"下文不会被绑定。 "
#. Tag: title
#: Naming.xml:617
@@ -2697,7 +2701,7 @@
#. Tag: programlisting
#: Naming.xml:626
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<mbean code=\"org.jboss.naming.JNDIBindingServiceMgr\" \n"
" name=\"jboss.tests:name=example1\">\n"
@@ -2723,8 +2727,9 @@
" <jndi:bindings xmlns:xs=\"http://www.w3.org/2001/XMLSchema-"
"instance\" \n"
" xmlns:jndi=\"urn:jboss:jndi-binding-service\"\n"
-" xs:schemaLocation=\"urn:jboss:jndi-binding-service "
-"resource:jndi-binding-service_1_0.xsd\"> \n"
+" xs:schemaLocation=\"urn:jboss:jndi-binding-service "
+"\\\n"
+" resource:jndi-binding-service_1_0.xsd\"> \n"
" <jndi:binding name=\"bindexample/message\">\n"
" <jndi:value trim=\"true\">\n"
" Hello, JNDI!\n"
@@ -2824,7 +2829,7 @@
#. Tag: programlisting
#: Naming.xml:642
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<jndi:binding name=\"maps/testProps\">\n"
" <java:properties xmlns:java=\"urn:jboss:java-properties\" \n"
@@ -2845,8 +2850,8 @@
"<jndi:binding name=\"maps/testProps\">\n"
" <java:properties xmlns:java=\"urn:jboss:java-properties\" \n"
" xmlns:xs=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
-" xs:schemaLocation=\"urn:jboss:java-properties resource:"
-"java-properties_1_0.xsd\">\n"
+" xs:schemaLocation=\"urn:jboss:java-properties \\\n"
+" resource:java-properties_1_0.xsd\">\n"
" <java:property>\n"
" <java:key>key1</java:key>\n"
" <java:value>value1</java:value>\n"
@@ -2870,9 +2875,9 @@
#. Tag: title
#: Naming.xml:649
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The org.jboss.naming.NamingAlias MBean"
-msgstr "The org.jboss.naming.JNDIView MBean"
+msgstr "The org.jboss.naming.NamingAlias MBean"
#. Tag: para
#: Naming.xml:650
@@ -2992,12 +2997,11 @@
msgid ""
"<emphasis role=\"bold\">JndiName</emphasis>: The JNDI name under which the "
"external context is to be bound."
-msgstr ""
-"<emphasis role=\"bold\">JndiName</emphasis>：外部的上下文绑定的 JNDI 名。"
+msgstr "<emphasis role=\"bold\">JndiName</emphasis>：外部的上下文绑定的 JNDI 名。"
#. Tag: para
#: Naming.xml:686
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">RemoteAccess</emphasis>: A boolean flag indicating "
"if the external <literal>InitialContext</literal> should be bound using a "
@@ -3023,7 +3027,7 @@
"<literal>new InitialContext(env)</literal> 时才可行。这要求 env 的 "
"<literal>Context.PROVIDER_URL</literal> 值在访问这个上下文的远程 VM 是可解析"
"的。对于 LDAP 示例，这是可用的。而对于文件系统示例来说，这很可能不行，除非文"
-"件系统路径指向通用的网络路径。如果没有设置，它缺省为 false。"
+"件系统路径指向通用的网络路径。如果没有设置，它缺省为 false。 "
#. Tag: para
#: Naming.xml:691
@@ -3080,7 +3084,7 @@
#. Tag: para
#: Naming.xml:706
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">PropertiesURL</emphasis>: This set the <literal>jndi."
"properties</literal> information for the external <literal>InitialContext</"
@@ -3089,7 +3093,7 @@
msgstr ""
"<emphasis role=\"bold\">PropertiesURL</emphasis>：它为外部属性文件里的外部 "
"<literal>InitialContext</literal> 设置 <literal>jndi.properties</literal> 信"
-"息。它可以是一个 URL，字符串或者 classpath 资源名。下面是一些示例："
+"息。它可以是一个 URL，字符串或者 classpath 资源名。下面是一些示例： "
#. Tag: para
#: Naming.xml:711
@@ -3189,7 +3193,7 @@
#. Tag: para
#: Naming.xml:741
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Using the same code fragment outside of the JBoss server VM will work in "
"this case because the <literal>RemoteAccess</literal> property was set to "
@@ -3202,7 +3206,7 @@
"<literal>RemoteAccess</literal> 属性被设置成了 true。如果这个属性为 false，因"
"为远程客户会接收一个<literal>ObjectFactory</literal> 的 <literal>Reference</"
"literal> 对象，它不能够重新创建外部的 <literal>IntialContext</literal>，所以"
-"就不能使用这个代码片段了。"
+"就不能使用这个代码片段了。 "
#. Tag: programlisting
#: Naming.xml:744
@@ -3291,7 +3295,7 @@
#. Tag: para
#: Naming.xml:759
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The JNDIView MBean allows the user to view the JNDI namespace tree as it "
"exists in the JBoss server using the JMX agent view interface. To view the "
@@ -3306,7 +3310,8 @@
"视图接口一样。用 JNDIView MBean 查看 JBoss JNDI 命名空间，你需要用 http 接口"
"连接到 JMX 代理视图。缺省的设定是：<literal>http://localhost:8080/jmx-"
"console/</literal>。在这个网页上，你将看到一个列出按域名排序的注册的 MBeans "
-"的部分。它应该和 <xref linkend=\"ch3.jmxconsole.fig\"/> 展示的类似。"
+"的部分。它应该和 <xref linkend=\"The_org.jboss.naming."
+"JNDIView_MBean-The_JMX_Console_view_of_the_configured_JBoss_MBeans\"/> 展示的类似。"
#. Tag: title
#: Naming.xml:763
@@ -3316,7 +3321,7 @@
#. Tag: para
#: Naming.xml:770
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Selecting the JNDIView link takes you to the JNDIView MBean view, which will "
"have a list of the JNDIView MBean operations. This view should look similar "
@@ -3324,7 +3329,8 @@
"The_JMX_Console_view_of_the_JNDIView_MBean\"/>."
msgstr ""
"选择带你进入 JNDIView MBean 视图的 JNDIView 链接，它将有 JNDIView MBean 操作"
-"的一个列表。这个视图应该和 <xref linkend=\"ch3.jndiview.fig\"/> 展示的类似。"
+"的一个列表。这个视图应该和 <xref linkend=\"The_org.jboss.naming.JNDIView_MBean-"
+"The_JMX_Console_view_of_the_JNDIView_MBean\"/> 展示的类似。"
#. Tag: title
#: Naming.xml:774
@@ -3334,7 +3340,7 @@
#. Tag: para
#: Naming.xml:781
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"The list operation dumps out the JBoss server JNDI namespace as an HTML page "
"using a simple text view. As an example, invoking the list operation "
@@ -3343,20 +3349,22 @@
">."
msgstr ""
"list 操作用简单的文本视图的方式把 JBoss 服务器的 JNDI 命名空间输出到一个 "
-"HTML 页面上。调用 list 操作会产生和 <xref linkend=\"ch3.jndiviewlist.fig\"/> "
+"HTML 页面上。调用 list 操作会产生和 <xref linkend=\"The_org.jboss.naming."
+"JNDIView_MBean-The_JMX_Console_view_of_the_JNDIView_list_operation_output\"/"
+"> "
"类似的输出。"
#. Tag: title
#: Naming.xml:785
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The JMX Console view of the JNDIView list operation output"
-msgstr "The JMX Console view of the JNDIView MBean"
+msgstr "JNDIView 列表操作输出的 JMX 控制台视图"
#. Tag: title
#: Naming.xml:797
#, no-c-format
msgid "J2EE and JNDI - The Application Component Environment"
-msgstr ""
+msgstr "J2EE and JNDI - 应用程序组件环境"
#. Tag: para
#: Naming.xml:798
@@ -3528,8 +3536,7 @@
#. Tag: para
#: Naming.xml:847
#, fuzzy, no-c-format
-msgid ""
-"Environment entries as declared by the <literal>env-entry</literal> elements"
+msgid "Environment entries as declared by the <literal>env-entry</literal> elements"
msgstr "下列是 <literal>TCP</literal> 元素里的可用属性。"
#. Tag: para
@@ -3538,8 +3545,7 @@
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>get()</literal> 或 <literal>load()</literal> 方法取得数据。"
#. Tag: para
#: Naming.xml:857
@@ -4023,8 +4029,7 @@
"The <literal>ProductBeanUser</literal><literal>ejb-ref</literal> link "
"destination is set to the deployment name of <literal>jboss/store/"
"ProductHome</literal>"
-msgstr ""
-"在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
+msgstr "在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
#. Tag: para
#: Naming.xml:1042
@@ -4032,8 +4037,7 @@
msgid ""
"The deployment JNDI name of the <literal>ProductBean</literal> is set to "
"<literal>jboss/store/ProductHome</literal>"
-msgstr ""
-"在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
+msgstr "在 <literal>Order</literal> 中，<literal>OrderLine</literal> 的集合则是这样："
#. Tag: title
#: Naming.xml:1047
@@ -4686,3 +4690,4 @@
" <!-- ... -->\n"
"</session>"
msgstr ""
+
More information about the jboss-cvs-commits
mailing list