[jboss-cvs] JBossAS SVN: r70604 - projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Mon Mar 10 00:06:48 EDT 2008


Author: xhuang at jboss.com
Date: 2008-03-10 00:06:48 -0400 (Mon, 10 Mar 2008)
New Revision: 70604

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_Security_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-03-10 00:17:54 UTC (rev 70603)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Messaging_On_JBOSS.po	2008-03-10 04:06:48 UTC (rev 70604)
@@ -10,7 +10,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-03-06 16:07+1000\n"
+"PO-Revision-Date: 2008-03-10 10:56+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team: Simplified Chinese <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -4188,7 +4188,6 @@
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:913
 #, no-c-format
-#, fuzzy
 msgid ""
 "<emphasis role=\"bold\">MaxDepth</emphasis>: The <literal>MaxDepth</literal> "
 "is an upper limit to the backlog of messages that can exist for a "
@@ -4201,9 +4200,7 @@
 "transaction or other transactions. This is because we don&#39;t want the "
 "transaction to fail during the commit phase when the message is physically "
 "added to the queue."
-msgstr ""
-"<emphasis role=\"bold\">MaxDepth</emphasis>:<literal>MaxDepth</literal> 是可存在于目的地里的积压消息的上限。超过这个上限时,如果继续添加新的消息将导致 <literal>org.jboss.mq.DestinationFullException</literal> 异常。在某些情况下仍然可以超过<literal>MaxDepth</literal>。例如,当消息被回放至队列里时。 "
-"这是因为在消息从物理上被添加到队列里时,我们不希望这个事务在提交阶段失败。"
+msgstr "<emphasis role=\"bold\">MaxDepth</emphasis>:<literal>MaxDepth</literal> 是可存在于目的地里的积压消息的上限。超过这个上限时,如果继续添加新的消息将导致 <literal>org.jboss.mq.DestinationFullException</literal> 异常。在某些情况下仍然可以超过<literal>MaxDepth</literal>。例如,当消息被回放至队列里时。执行读提交处理的事务也会查看队列的大小,忽略任何作为当前事务或其他事务结果添加的消息。这是因为在消息从物理上被添加到队列里时,我们不希望这个事务在提交阶段失败。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:918
@@ -4409,7 +4406,6 @@
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1011
 #, no-c-format
-#, fuzzy
 msgid ""
 "<emphasis role=\"bold\">MaxDepth</emphasis>: The <literal>MaxDepth</literal> "
 "is an upper limit to the backlog of messages that can exist for a "
@@ -4422,9 +4418,7 @@
 "transaction or other transactions. This is because we don&#39;t want the "
 "transaction to fail during the commit phase when the message is physically "
 "added to the topic."
-msgstr ""
-"<emphasis role=\"bold\">MaxDepth</emphasis>:<literal>MaxDepth</literal> 是存在于目的地里的积压消息的上限,如果超过这个值,试图添加新消息将导致 <literal>org.jboss.mq.DestinationFullException</literal> 异常。在某些情况下仍然可以超过<literal>MaxDepth</literal>。例如,当消息被回放至队列里时。 "
-"这是因为在消息从物理上被添加到队列里时,我们不希望这个事务在提交阶段失败。"
+msgstr "<emphasis role=\"bold\">MaxDepth</emphasis>:<literal>MaxDepth</literal> 是存在于目的地里的积压消息的上限,如果超过这个值,试图添加新消息将导致 <literal>org.jboss.mq.DestinationFullException</literal> 异常。在某些情况下仍然可以超过<literal>MaxDepth</literal>。例如,当消息被回放至队列里时。执行读提交处理的事务也会查看队列的大小,忽略任何作为当前事务或其他事务结果添加的消息。这是因为在消息从物理上被添加到队列里时,我们不希望这个事务在提交阶段失败。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1016
@@ -4571,7 +4565,7 @@
 "implementation of the <literal>JMSProviderAdaptor</literal> interface and "
 "configure the JMSProviderLoader with the class name of the implementation. "
 "We&#39;ll see an example of this in the configuration section."
-msgstr ""
+msgstr "让我们从 <literal>org.jboss.jms.jndi.JMSProviderLoader</literal> MBean 开始。这个 MBean 负责把 <literal>org.jboss.jms.jndi.JMSProviderAdaptor</literal> 实例加载到 JBoss 服务器里并绑定至 JNDI。<literal>JMSProviderAdaptor</literal> 接口是定义如何取得 JMS 提供者的根 JNDI 上下文的抽象,它也获取和设置根 JNDI 上下文的 <literal>Context.PROVIDER_URL</literal> çš„ JNDI 名、以及根上下文的 <literal>QueueConnectionFactory</literal> å’Œ <literal>TopicConnectionFactory</literal> 位置。这些对于引导 JMS 提供者是必需的。通过把这些信息抽象至一个接口,其他的 JMS ASF 提供者实现就可以和 JBoss MDB 容器一起使用。<literal>org.jboss.jms.jndi.JBossMQProvider</literal> 是 <literal>JMSProviderAdaptor</literal> 接口的缺省实现,它为 JBossMQ JMS 提供者提供适配器。要用其他的 <literal>JMSProviderAdaptor</literal> 接口实现替换 JBossMQ 提供者,你å!
 ªéœ€ç®€å•åœ°åˆ›å»ºä¸€ä¸ª <literal>JMSProviderAdaptor</literal> 接口的实现并用这个实现的类名配置 JMSProviderLoader 就可以了。我们在配置章节里将看到这样的例子。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1103
@@ -4586,6 +4580,9 @@
 "<literal>ServerSessionPoolFactory</literal> factory implementation is the "
 "JBoss <literal>org.jboss.jms.asf.StdServerSessionPoolFactory</literal> class."
 msgstr ""
+"除了能够替换用于 MDB 的 JMS 提供者,你还可以替换 javax.jms.ServerSessionPool 接口的实现。这可以通过 <literal>org."
+"jboss.jms.asf.ServerSessionPoolLoader</literal> MBean 的 <literal>PoolFactoryClass</literal> 属性配置 <literal>org.jboss.jms.asf."
+"ServerSessionPoolFactory</literal> 实现的类名来实现。<literal>ServerSessionPoolFactory</literal> 工厂缺省的实现是 JBoss <literal>org.jboss.jms.asf.StdServerSessionPoolFactory</literal> 类。"
 
 #. Tag: title
 #: J2EE_Messaging_On_JBOSS.xml:1107
@@ -4603,7 +4600,7 @@
 "interface. It is used by the message driven bean container to access a JMS "
 "service provider in a provider independent manner. The configurable "
 "attributes of the <literal>JMSProviderLoader</literal> service are:"
-msgstr ""
+msgstr "<literal>JMSProviderLoader</literal> MBean 服务创建了一个 JMS 提供者适配器并绑定至 JNDI。JMS 提供者适配器是实现 <literal>org.jboss.jms.jndi.JMSProviderAdapter</literal> 接口的类。Message Driven Bean 容器以独立于 JMS 提供者的方式使用它来访问 JMS 服务器提供者。<literal>JMSProviderLoader</literal> 服务的可配置属性是:"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1113
@@ -4615,6 +4612,8 @@
 "literal> unless overridden by the <literal>AdapterJNDIName</literal> "
 "attribute."
 msgstr ""
+"<emphasis role=\"bold\">ProviderName</emphasis>:JMS 提供者的唯一名称。除非被 <literal>AdapterJNDIName</literal> 属性覆盖,否则它将被用来把 <literal>JMSProviderAdapter</"
+"literal> 实例绑定到基于 <literal>java:/&lt;ProviderName&gt;</literal> 的 JNDI。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1118
@@ -4721,6 +4720,9 @@
 "jboss.jms.jndi.JMSProviderLoader_MBean-_A_jboss."
 "xml_fragment_for_specifying_the_MDB_JMS_provider_adaptor\"/>."
 msgstr ""
+"如 <literal>jboss.xml</literal> fragment given in <xref linkend=\"org."
+"jboss.jms.jndi.JMSProviderLoader_MBean-_A_jboss."
+"xml_fragment_for_specifying_the_MDB_JMS_provider_adaptor\"/> 所展示的配置,MDB 调用者可以引用 RemoteJMSProvider。"
 
 #. Tag: title
 #: J2EE_Messaging_On_JBOSS.xml:1148
@@ -4775,6 +4777,8 @@
 "topic on multiple servers by configuring multiple bindings with different "
 "<literal>JMSProviderAdapterJNDI</literal> settings."
 msgstr ""
+"因为你可以指定多个 <literal>invoker-proxy-"
+"binding</literal> 元素,这允许 MDB 通过不同的 <literal>JMSProviderAdapterJNDI</literal> 设置配置多个绑定来侦听多个服务器上的相同的队列/主题。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1153
@@ -4785,6 +4789,9 @@
 "JMSProviderLoader_MBean-A_jms_ds."
 "xml_descriptor_for_integrating_a_JMS_provider_adaptor_via_JCA\"/>."
 msgstr ""
+"此外,你可以用 <xref linkend=\"org.jboss.jms.jndi."
+"JMSProviderLoader_MBean-A_jms_ds."
+"xml_descriptor_for_integrating_a_JMS_provider_adaptor_via_JCA\"/> 里展示的 JCA 配置来集成 JMS 提供者。"
 
 #. Tag: title
 #: J2EE_Messaging_On_JBOSS.xml:1156
@@ -4840,30 +4847,27 @@
 "factory for <literal>javax.jms.ServerSessionPool</literal> objects used by "
 "the message driven bean container. The configurable attributes of the "
 "<literal>ServerSessionPoolLoader</literal> service are:"
-msgstr ""
+msgstr "<literal>ServerSessionPoolLoader</literal> MBean 服务管理用于 MDB 容器使用的 <literal>javax.jms.ServerSessionPool</literal> 对象的工厂。<literal>ServerSessionPoolLoader</literal> 服务的可配置属性是:"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1168
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<emphasis role=\"bold\">PoolName</emphasis>: A unique name for the session "
 "pool. This will be used to bind the <literal>ServerSessionPoolFactory</"
 "literal> instance into JNDI under <literal>java:/PoolName</literal>."
-msgstr ""
-"<emphasis role=\"bold\">name</emphasis>:attribute的名字,在"
-"<literal>MBeanServer.getAttribute()</literal>操作里使用。"
+msgstr "<emphasis role=\"bold\">PoolName</emphasis>:Session 池的唯一名称。它用来把 <literal>ServerSessionPoolFactory</literal> 实例绑定至 <literal>java:/PoolName</literal> JNDI。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1173
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<emphasis role=\"bold\">PoolFactoryClass</emphasis>: The fully qualified "
 "class name of the <literal>org.jboss.jms.asf.ServerSessionPoolFactory</"
 "literal> interface to create an instance of."
 msgstr ""
-"<emphasis role=\"bold\">RMIServerSocketFactory</emphasis>:在输出代理接口时,"
-"指定 <literal>java.rmi.server.RMIServerSocketFactory</literal> 接口使用的类全"
-"名。"
+"<emphasis role=\"bold\">PoolFactoryClass</emphasis>:用于创建实例的 <literal>org.jboss.jms.asf.ServerSessionPoolFactory</"
+"literal> 接口的全限定名。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1178
@@ -4876,6 +4880,8 @@
 "<literal>Instance</literal> operation which returns a <literal>org.jboss.tm."
 "XidFactoryMBean</literal> instance."
 msgstr ""
+"<emphasis role=\"bold\">XidFactory</emphasis>:当不要求两阶段提交时,这个服务用来为本地事务生成 <literal>javax.transaction.xa."
+"Xid</literal> 值的 JMX <literal>ObjectName</literal>。<literal>XidFactory</literal> MBean 必须提供一个返回 <literal>org.jboss.tm.XidFactoryMBean</literal> 实例的 <literal>Instance</literal> 操作。"
 
 #. Tag: title
 #: J2EE_Messaging_On_JBOSS.xml:1186
@@ -4899,7 +4905,7 @@
 "Replace the JMSProviderLoader JBossMQProvider class with one that "
 "instantiates the correct JNDI context for communicating with the foreign JMS "
 "providers managed objects."
-msgstr ""
+msgstr "用初始化正确的用于和外部 JMS 提供者所管理的对象通信的 JNDI 上下文的类替换 JMSProviderLoader JBossMQProvider 类。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1197
@@ -4907,7 +4913,7 @@
 msgid ""
 "Use the <literal>ExternalContext</literal> MBean to federate the foreign JMS "
 "providers managed objects into the JBoss JNDI tree."
-msgstr ""
+msgstr "使用 <literal>ExternalContext</literal> MBean 来把外部的 JMS 提供者管理的对象联合到 JBoss JNDI 树里。"
 
 #. Tag: para
 #: J2EE_Messaging_On_JBOSS.xml:1202
@@ -4918,4 +4924,7 @@
 "\"http://wiki.jboss.org/wiki/Wiki.jsp?page=IntegrationWithWebSphereMQSeries"
 "\"></ulink>."
 msgstr ""
+"使用 MBean 来把外部 JMS 对象初始化至 JBoss JNDI 树里。在 <ulink url="
+"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=IntegrationWithWebSphereMQSeries"
+"\"></ulink> 上的 Websphere MQ 里,你可以找到使用这种方法的一个例子。"
 

Modified: projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po
===================================================================
--- projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po	2008-03-10 00:17:54 UTC (rev 70603)
+++ projects/docs/trunk/AS_4/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po	2008-03-10 04:06:48 UTC (rev 70604)
@@ -10,7 +10,7 @@
 "Project-Id-Version: J2EE_Security_On_JBOSS\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2007-11-05 06:04+0000\n"
-"PO-Revision-Date: 2008-03-06 15:40+1000\n"
+"PO-Revision-Date: 2008-03-10 14:02+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team: Simplified Chinese <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -934,6 +934,8 @@
 "<literal>CONFIDENTIAL</literal> flag indicates that the use of SSL is "
 "required."
 msgstr ""
+"可选的 <literal>user-data-constraint</literal> 元素指定用于客户和服务器连接的传输层的需求。这种需求可能用于内容完整性(阻止数据在通信过程中被篡改)或保密性(阻止在传输时被读取)。transport-guarantee 元素的值指定客户和服务器之间通信被保护的程度。它的值为 <literal>NONE</literal>、<literal>INTEGRAL</literal> 和 <literal>CONFIDENTIAL</literal>。<literal>NONE</literal> 表示应用程序不要求任何传输保证。<literal>INTEGRAL</literal> 表示应用程序要求在客户和服务器之间发送的数据不能在传输过程中被修改。<literal>CONFIDENTIAL</literal> 则表示应用程序要求其他实体不能查看传输的内容。大多数情况下,<literal>INTEGRAL</literal> 或 "
+"<literal>CONFIDENTIAL</literal> 标记表示对 SSL 的使用是必需的。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:183
@@ -968,6 +970,9 @@
 "<literal>auth-method</literal> value is not <literal>FORM</literal>, then "
 "<literal>form-login-config</literal> and its child elements are ignored."
 msgstr ""
+"<literal>auth-method</literal> 子元素指定用于 web 应用程序的验证机制。对任何由验证约束保护的 web 资源的访问之前,用户必须用配置的机制进行验证。合法的 <literal>auth-method</literal> 值是<literal>BASIC</literal>、 "
+"<literal>DIGEST</literal>、<literal>FORM</literal> 和 <literal>CLIENT-"
+"CERT</literal>。<literal>realm-name</literal> 子元素指定在 HTTP basic 和 digest 验证中使用的 realm 名称。<literal>form-login-config</literal> 子元素指定在基于表单的登录过程中使用的登录和出错页面。如果 <literal>auth-method</literal> 的值不是 <literal>FORM</literal>,<literal>form-login-config</literal> 及其子元素将被忽略。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:197
@@ -981,6 +986,10 @@
 "role. There is no required transport guarantee and the authentication method "
 "used for obtaining the user identity is BASIC HTTP authentication."
 msgstr ""
+"例如,<xref linkend=\"Web_Content_Security_Constraints-_A_web."
+"xml_descriptor_fragment_which_illustrates_the_use_of_the_security_constraint_and_related_elements."
+"\"/> 里给出的 <literal>web.xml</literal> 描述符片段指定了任何 <literal>/"
+"restricted</literal> 目录下的 URL 都需要具有 <literal>AuthorizedUser</literal> 角色。因为采用  BASIC HTTP 验证方式,所以这个 web 应用程序不要求传输保证以及获取用户标识符的验证方法。"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:200
@@ -989,6 +998,8 @@
 "A web.xml descriptor fragment which illustrates the use of the security-"
 "constraint and related elements."
 msgstr ""
+"解释 security-"
+"constraint 和相关元素的用法的 web.xml 描述符片段。"
 
 #. Tag: programlisting
 #: J2EE_Security_On_JBOSS.xml:201
@@ -1022,6 +1033,33 @@
 "    &lt;/security-role&gt;\n"
 "&lt;/web-app&gt;"
 msgstr ""
+"&lt;web-app&gt;\n"
+"    &lt;!-- ... --&gt;\n"
+"    &lt;security-constraint&gt;\n"
+"        &lt;web-resource-collection&gt;\n"
+"            &lt;web-resource-name&gt;Secure Content&lt;/web-resource-"
+"name&gt;\n"
+"            &lt;url-pattern&gt;/restricted/*&lt;/url-pattern&gt;\n"
+"        &lt;/web-resource-collection&gt;\n"
+"        &lt;auth-constraint&gt;\n"
+"            &lt;role-name&gt;AuthorizedUser&lt;/role-name&gt;\n"
+"        &lt;/auth-constraint&gt;\n"
+"        &lt;user-data-constraint&gt;\n"
+"            &lt;transport-guarantee&gt;NONE&lt;/transport-guarantee&gt;\n"
+"        &lt;/user-data-constraint&gt;\n"
+"    &lt;/security-constraint&gt;\n"
+"    &lt;!-- ... --&gt;\n"
+"    &lt;login-config&gt;\n"
+"        &lt;auth-method&gt;BASIC&lt;/auth-method&gt;\n"
+"        &lt;realm-name&gt;The Restricted Zone&lt;/realm-name&gt;\n"
+"    &lt;/login-config&gt;\n"
+"    &lt;!-- ... --&gt;\n"
+"    &lt;security-role&gt;\n"
+"        &lt;description&gt;The role required to access restricted content "
+"&lt;/description&gt;\n"
+"        &lt;role-name&gt;AuthorizedUser&lt;/role-name&gt;\n"
+"    &lt;/security-role&gt;\n"
+"&lt;/web-app&gt;"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:206
@@ -1044,12 +1082,14 @@
 "security configuration are discussed in <xref linkend=\"Security_on_JBoss-"
 "The_JBoss_Security_Model\"/>."
 msgstr ""
+"目前已经介绍的 J2EE 安全方面的元素仅仅描述了从应用程序的视角出发的安全性要求。因为 J2EE 关于安全性的元素声明了逻辑角色,应用程序部署者把这些角色从应用程序域映射至部署环境。J2EE 规格忽略了这些和服务器相关的细节。在 JBoss 里,从应用程序域至部署环境的映射需要指定一个安全管理者,它用 JBoss 服务器特定的部署描述符实现了 J2EE 的安全模型。关于安全配置背后的细节,我们将在 <xref linkend=\"Security_on_JBoss-"
+"The_JBoss_Security_Model\"/> 里进行讨论。"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:215
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "An Introduction to JAAS"
-msgstr "JMX的简介"
+msgstr "JAAS 简介"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:216
@@ -1060,13 +1100,13 @@
 "implementation details of JBossSX. The following sections provide an "
 "introduction to JAAS to prepare you for the JBossSX architecture discussion "
 "later in this chapter."
-msgstr ""
+msgstr "JBossSX 框架是基于 JAAS API 的。理解 JAAS API 的基本要素对于理解 JBossSX 的实现细节很重要。下面的章节提供了对 JAAS 简介,你可以为后面讨论 JBossSX 架构做好准备。"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:220
 #, no-c-format
 msgid "What is JAAS?"
-msgstr ""
+msgstr "什么是 JAAS?"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:221
@@ -1080,7 +1120,7 @@
 "for JDK 1.3 and is bundled with JDK 1.4+. Because the JBossSX framework uses "
 "only the authentication capabilities of JAAS to implement the declarative "
 "role-based J2EE security model, this introduction focuses on only that topic."
-msgstr ""
+msgstr "JAAS 1.0 API 由一套用于用户验证和授权的 Java 软件包组成。它用 Java 实现了标准的 Pluggable Authentication Module (PAM) 框架并扩展了 Java 2 平台的访问控制架构来支持基于用户的授权。一开始 JAAS 是作为 JDK 1.3 的扩展软件包发布的,而 JDK 1.4+ 则对它进行了捆绑。因为 JBossSX 框架只使用 JAAS 的验证功能来实现声明式的基于角色的 J2EE 安全模型,所以这个简介只注重这方面的内容。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:224
@@ -1093,13 +1133,13 @@
 "achieved without changing the JBossSX security manager implementation. All "
 "that needs to change is the configuration of the authentication stack that "
 "JAAS uses."
-msgstr ""
+msgstr "JAAS 验证以可插拔的形式执行。这允许 Java 应用程序独立于底层的验证技术并允许 JBossSX 安全管理者工作于不同的安全架构里。不修改 JBossSX 安全管理者的实现就可以集成安全架构。仅需修改的是 JAAS 使用的验证栈的配置。"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:228
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The JAAS Core Classes"
-msgstr "order by 子句"
+msgstr "JAAS 核心类"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:229
@@ -1109,41 +1149,41 @@
 "authentication, and authorization. The following list presents only the "
 "common and authentication classes because these are the specific classes "
 "used to implement the functionality of JBossSX covered in this chapter."
-msgstr ""
+msgstr "JAAS 核心类可以分成 3 个类别:通用(Common)、验证(authentication)和授权(authorization)。下面的列表仅列出通用和验证类,这是因为本章所涉及的 JBossSX 的功能是用这些类来实现的。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:232
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The are the common classes:"
-msgstr "from 子句"
+msgstr "通用类:"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:237
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "<literal>Subject</literal> (<literal>javax.security.auth.Subject</literal>)"
-msgstr ""
-"通过 <literal>java -Dproperty=value</literal> 来设置系统(<literal>System</"
-"literal>)属性。"
+msgstr "<literal>Subject</literal> (<literal>javax.security.auth.Subject</literal>)"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:242
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "<literal>Principal</literal> (<literal>java.security.Principal</literal>)"
-msgstr "<literal>coalesce()</literal> 和 <literal>nullif()</literal>"
+msgstr "<literal>Principal</literal> (<literal>java.security.Principal</literal>)"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:247
 #, no-c-format
 msgid "These are the authentication classes:"
-msgstr ""
+msgstr "验证类:"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:252
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<literal>Callback</literal> (<literal>javax.security.auth.callback.Callback</"
 "literal>)"
-msgstr "<literal>coalesce()</literal> 和 <literal>nullif()</literal>"
+msgstr ""
+"<literal>Callback</literal> (<literal>javax.security.auth.callback.Callback</"
+"literal>)"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:257
@@ -1152,14 +1192,18 @@
 "<literal>CallbackHandler</literal> (<literal>javax.security.auth.callback."
 "CallbackHandler</literal>)"
 msgstr ""
+"<literal>CallbackHandler</literal> (<literal>javax.security.auth.callback."
+"CallbackHandler</literal>)"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:262
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<literal>Configuration</literal> (<literal>javax.security.auth.login."
 "Configuration</literal>)"
-msgstr "<literal>Configuration</literal> 也允许你指定配置属性:"
+msgstr ""
+"<literal>Configuration</literal> (<literal>javax.security.auth.login."
+"Configuration</literal>)"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:267
@@ -1168,20 +1212,24 @@
 "<literal>LoginContext</literal> (<literal>javax.security.auth.login."
 "LoginContext</literal>)"
 msgstr ""
+"<literal>LoginContext</literal> (<literal>javax.security.auth.login."
+"LoginContext</literal>)"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:272
-#, fuzzy, no-c-format
+#, no-c-format
 msgid ""
 "<literal>LoginModule</literal> (<literal>javax.security.auth.spi."
 "LoginModule</literal>)"
-msgstr "<literal>coalesce()</literal> 和 <literal>nullif()</literal>"
+msgstr ""
+"<literal>LoginModule</literal> (<literal>javax.security.auth.spi."
+"LoginModule</literal>)"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:278
 #, no-c-format
 msgid "The Subject and Principal Classes"
-msgstr ""
+msgstr "Subject 和 Principal 类"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:279
@@ -1197,6 +1245,8 @@
 "literal> interface to represent a principal, which is essentially just a "
 "typed name."
 msgstr ""
+"为了给访问资源授权,应用程序首先需要验证请求的来源。JAAS 框架定义了代表请求来源的术语:subject。<literal>Subject</literal> 类是 JAAS 的中心类。<literal>Subject</literal> 代表单个实体的信息,如某个人或服务。它包括实体的 principal、public credential 和 private credential。JAAS API 使用现有的 Java 2 <literal>java.security.Principal</"
+"literal> 接口来表示 principal,这基本上只是一个类型名。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:282
@@ -1208,7 +1258,7 @@
 "principal (123-45-6789), and a username principal (johnd), all of which help "
 "distinguish the subject from other subjects. To retrieve the principals "
 "associated with a subject, two methods are available:"
-msgstr ""
+msgstr "在验证过程中,Subject 和与之关联的标识符(或 Principal)一起被传递。Subject 可能有多个 Principal。例如,某人可能有一个名字标识(John Doe)、一个社会保险号码标识(123-45-6789)、以及一个用户名表示(johnd),这些都有助于区分他和其他 Subject。要获取和 Subject 想关联的 Principal,你可以使用两种方法:"
 
 #. Tag: programlisting
 #: J2EE_Security_On_JBOSS.xml:285
@@ -1217,6 +1267,8 @@
 "public Set getPrincipals() {...}\n"
 "public Set getPrincipals(Class c) {...}"
 msgstr ""
+"public Set getPrincipals() {...}\n"
+"public Set getPrincipals(Class c) {...}"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:286
@@ -1230,12 +1282,16 @@
 "literal>, so an instance in the principals set may represent a logical "
 "grouping of other principals or groups of principals."
 msgstr ""
+"第一个方法返回该 Subject 包含的所有的 Principal。第二个方法返回值类 <literal>c</"
+"literal> 或其子类的实例的 Principal。如果这个 Subject 没有匹配的 Principal,将返回空值。请注意,<literal>java.security.acl.Group</"
+"literal> 接口是 <literal>java.security.Principal</"
+"literal> 的子接口,所以 Principal 集合里的实例可能代表其他 Principal 或组的逻辑分组。"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:292
 #, no-c-format
 msgid "Authentication of a Subject"
-msgstr ""
+msgstr "验证 Subject "
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:293
@@ -1243,7 +1299,7 @@
 msgid ""
 "Authentication of a subject requires a JAAS login. The login procedure "
 "consists of the following steps:"
-msgstr ""
+msgstr "验证 Subject 要求 JAAS 登录。登录过程由下列步骤组成:"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:298
@@ -1253,7 +1309,7 @@
 "the name of the login configuration and a <literal>CallbackHandler</literal> "
 "to populate the <literal>Callback</literal> objects, as required by the "
 "configuration <literal>LoginModule</literal>s."
-msgstr ""
+msgstr "如 <literal>LoginModule</literal> 配置所示,应用程序初始化 <literal>LoginContext</literal> 并传入登录配置的名字以及一个 <literal>CallbackHandler</literal> 来传递 <literal>Callback</literal> 对象。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:303
@@ -1264,12 +1320,14 @@
 "named login configuration. If no such named configuration exists the "
 "<literal>other</literal> configuration is used as a default."
 msgstr ""
+"<literal>LoginContext</literal> 构建一个 <literal>Configuration</"
+"literal> 来加载登录配置里包括的所有 <literal>LoginModules</literal>。如果该命名配置不存在,<literal>other</literal> 配置将作为缺省配置使用。 "
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:308
-#, fuzzy, no-c-format
+#, no-c-format
 msgid "The application invokes the <literal>LoginContext.login</literal> method."
-msgstr "这个 <literal>Set</literal> 的映射"
+msgstr "应用程序调用 <literal>LoginContext.login</literal> 方法。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:313




More information about the jboss-cvs-commits mailing list