[jboss-cvs] JBossAS SVN: r92909 - 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
Fri Aug 28 04:19:59 EDT 2009


Author: xhuang at jboss.com
Date: 2009-08-28 04:19:59 -0400 (Fri, 28 Aug 2009)
New Revision: 92909

Modified:
   projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_JBoss.po
   projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_Open_Source.po
   projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po
Log:
update

Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_JBoss.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_JBoss.po	2009-08-28 06:45:37 UTC (rev 92908)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_JBoss.po	2009-08-28 08:19:59 UTC (rev 92909)
@@ -9,7 +9,7 @@
 "Project-Id-Version: About_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-08-24 14:39+1000\n"
+"PO-Revision-Date: 2009-08-28 16:09+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -26,150 +26,108 @@
 #. Tag: para
 #: About_JBoss.xml:6
 #, no-c-format
-msgid ""
-"JBoss, a division of Red Hat, is the global leader in open source middleware "
-"software, combining enterprise-class JEMS open source software with the "
-"industry’s leading services and tools to provide simply a better way to "
-"transform your business to Service-Oriented Architecture (SOA)."
+msgid "JBoss, a division of Red Hat, is the global leader in open source middleware software, combining enterprise-class JEMS open source software with the industry’s leading services and tools to provide simply a better way to transform your business to Service-Oriented Architecture (SOA)."
 msgstr "JBoss,作为红帽的一个部门,是开源中间件软件的全球领导者,它把企业级的 JEMS 开源软件和行业领先的服务和工具结合在一起,提供了把企业转向面向服务构建(Service-Oriented Architecture,SOA)的更好途径。"
 
 #. Tag: para
 #: About_JBoss.xml:9
 #, no-c-format
-#, fuzzy
-msgid ""
-"JBoss, pioneered the disruptive Professional Open Source model, which "
-"combines the best of the open source and proprietary software worlds to make "
-"open source a safe choice for the enterprise and give CIOs peace of mind. "
-"This includes the royalty-free software, transparent development and active "
-"community inherent in open source and the accountability and professional "
-"support services expected of a traditional software vendor. The company "
-"finds innovative open source projects and professionalizes the project from "
-"a hobby into a livelihood by hiring the lead developer(s), often the "
-"founders themselves. JBoss provides the resources, core development and "
-"support services to enable popular open source projects to scale into "
-"enterprise-class software."
+msgid "JBoss, pioneered the disruptive Professional Open Source model, which combines the best of the open source and proprietary software worlds to make open source a safe choice for the enterprise and give CIOs peace of mind. This includes the royalty-free software, transparent development and active community inherent in open source and the accountability and professional support services expected of a traditional software vendor. The company finds innovative open source projects and professionalizes the project from a hobby into a livelihood by hiring the lead developer(s), often the founders themselves. JBoss provides the resources, core development and support services to enable popular open source projects to scale into enterprise-class software."
 msgstr "JBoss 提倡开创性的专业开源模型,组合最好的开源和私有软件,为企业提供安全的开源选择 "
 
 #. Tag: para
 #: About_JBoss.xml:12
 #, no-c-format
-msgid ""
-"<emphasis>Coverage:</emphasis> North America and Europe on a direct basis. "
-"JBoss provides coverage worldwide via our extensive authorized partner "
-"network."
+msgid "<emphasis>Coverage:</emphasis> North America and Europe on a direct basis. JBoss provides coverage worldwide via our extensive authorized partner network."
 msgstr "<emphasis>覆盖范围</emphasis>:为北美和欧洲提供直接服务,对世界其他地区通过授权的合作网络提供服务。"
 
 #. Tag: para
 #: About_JBoss.xml:15
 #, no-c-format
-msgid ""
-"<emphasis>Mission Statement:</emphasis> JBoss&#39; mission is to "
-"revolutionize the way enterprise middleware software is built, distributed, "
-"and supported through the Professional Open Source model. We are committed "
-"to delivering innovative and high quality technology and services that make "
-"JBoss the safe choice for enterprises and software providers."
+msgid "<emphasis>Mission Statement:</emphasis> JBoss&#39; mission is to revolutionize the way enterprise middleware software is built, distributed, and supported through the Professional Open Source model. We are committed to delivering innovative and high quality technology and services that make JBoss the safe choice for enterprises and software providers."
 msgstr ""
 
 #. Tag: para
 #: About_JBoss.xml:18
 #, no-c-format
-msgid ""
-"<emphasis>Customers:</emphasis> Enterprise customers deploying JBoss "
-"technologies in mission-critical applications with professional services "
-"support from JBoss include Aviva Canada, Continental Airlines, La Quinta, "
-"NLG, MCI, Nielsen Media Research and Travelocity. For a current list of "
-"customer success stories, please visit the <ulink url=\"http://www.jboss.com/"
-"customers/index\">Customers</ulink> section of our website."
+msgid "<emphasis>Customers:</emphasis> Enterprise customers deploying JBoss technologies in mission-critical applications with professional services support from JBoss include Aviva Canada, Continental Airlines, La Quinta, NLG, MCI, Nielsen Media Research and Travelocity. For a current list of customer success stories, please visit the <ulink url=\"http://www.jboss.com/customers/index\">Customers</ulink> section of our website."
 msgstr ""
 
 #. Tag: para
 #: About_JBoss.xml:21
 #, no-c-format
-msgid ""
-"<emphasis>Partners:</emphasis> JBoss works with software and hardware "
-"vendors, systems integrators and OEMs to deliver implementation services, "
-"frontline support, and certification for products embedded with JBoss "
-"technologies. For more information on the JBoss Certified Partner Program, "
-"please visit the <ulink url=\"http://www.jboss.com/partners/index"
-"\">Partners</ulink> section of our website."
+msgid "<emphasis>Partners:</emphasis> JBoss works with software and hardware vendors, systems integrators and OEMs to deliver implementation services, frontline support, and certification for products embedded with JBoss technologies. For more information on the JBoss Certified Partner Program, please visit the <ulink url=\"http://www.jboss.com/partners/index\">Partners</ulink> section of our website."
 msgstr ""
 
 #. Tag: para
 #: About_JBoss.xml:24
 #, no-c-format
 msgid "Professional Open Source(tm) from JBoss Inc. offers you:"
-msgstr ""
+msgstr "JBoss Inc. 的 Professional Open Source(tm) 为你提供:"
 
 #. Tag: para
 #: About_JBoss.xml:27
 #, no-c-format
 msgid "Standards-based and stable Java Middleware technology"
-msgstr ""
+msgstr "基于标准的、稳定的 Java 中间件技术"
 
 #. Tag: para
 #: About_JBoss.xml:32
 #, no-c-format
 msgid "No cost open source product licenses"
-msgstr ""
+msgstr "无需成本的开源产品许可证"
 
 #. Tag: para
 #: About_JBoss.xml:37
 #, no-c-format
 msgid "Backed by a professional and expert support staff"
-msgstr ""
+msgstr "由专家和专业支持人员提供的服务"
 
 #. Tag: para
 #: About_JBoss.xml:42
 #, no-c-format
-msgid ""
-"Comprehensive services including <ulink url=\"http://www.jboss.com/services/"
-"profsupport\">Professional Support</ulink>, <ulink url=\"http://www.jboss."
-"com/services/certification\">Training</ulink>, and <ulink url=\"http://www."
-"jboss.com/services/consulting\">Consulting</ulink>"
-msgstr ""
+msgid "Comprehensive services including <ulink url=\"http://www.jboss.com/services/profsupport\">Professional Support</ulink>, <ulink url=\"http://www.jboss.com/services/certification\">Training</ulink>, and <ulink url=\"http://www.jboss.com/services/consulting\">Consulting</ulink>"
+msgstr "完备的服务,包括 <ulink url=\"http://www.jboss.com/services/profsupport\">Professional Support</ulink>、<ulink url=\"http://www.jboss.com/services/certification\">Training</ulink> 和 <ulink url=\"http://www.jboss.com/services/consulting\">Consulting</ulink>"
 
 #. Tag: para
 #: About_JBoss.xml:47
 #, no-c-format
 msgid "A very large and active community of developers"
-msgstr ""
+msgstr "庞大且活跃的开发人员社区"
 
 #. Tag: para
 #: About_JBoss.xml:52
 #, no-c-format
-msgid ""
-"An extensive worldwide network of authorized and certified <ulink url="
-"\"http://www.jboss.com/partners/index\">partners</ulink>"
-msgstr ""
+msgid "An extensive worldwide network of authorized and certified <ulink url=\"http://www.jboss.com/partners/index\">partners</ulink>"
+msgstr "由通过授权和认证的<ulink url=\"http://www.jboss.com/partners/index\">合作伙伴</ulink>组成的遍布全世界的网络。"
 
 #. Tag: para
 #: About_JBoss.xml:58
 #, no-c-format
 msgid "Benefits of Professional Open Source from JBoss Inc.:"
-msgstr ""
+msgstr "JBoss Inc. 的 Professional Open Source 能为你提供:"
 
 #. Tag: para
 #: About_JBoss.xml:61
 #, no-c-format
 msgid "Lowest possible total cost of ownership"
-msgstr ""
+msgstr "尽可能低的成本"
 
 #. Tag: para
 #: About_JBoss.xml:66
 #, no-c-format
 msgid "Reliable and safe technology"
-msgstr ""
+msgstr "可靠和安全的技术"
 
 #. Tag: para
 #: About_JBoss.xml:71
 #, no-c-format
 msgid "Support, accountability, and trust from a stable company"
-msgstr ""
+msgstr "来自可靠公司的支持、承诺和信任"
 
 #. Tag: para
 #: About_JBoss.xml:76
 #, no-c-format
 msgid "Expedited problem resolution compared to commercial software vendors"
-msgstr ""
+msgstr "可和商业级软件供应商媲美的对问题的快速解决"
 

Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_Open_Source.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_Open_Source.po	2009-08-28 06:45:37 UTC (rev 92908)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/About_Open_Source.po	2009-08-28 08:19:59 UTC (rev 92909)
@@ -9,7 +9,7 @@
 "Project-Id-Version: About_Open_Source\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-08-26 11:00+1000\n"
+"PO-Revision-Date: 2009-08-28 16:12+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -26,22 +26,8 @@
 #. Tag: para
 #: About_Open_Source.xml:6
 #, no-c-format
-msgid ""
-"The basic idea behind open source is very simple: When programmers can read, "
-"redistribute, and modify the source code for a piece of software, the "
-"software evolves. People improve it, people adapt it, people fix bugs. And "
-"this can happen at a speed that, if one is used to the slow pace of "
-"conventional software development, seems astonishing. Open Source is an "
-"often-misunderstood term relating to free software. The Open Source "
-"Initiative (OSI) web site provides a number of resources that define the "
-"various aspects of Open Source including an Open Source Definition at: "
-"<ulink url=\"http://www.opensource.org/docs/definition.html\">http://www."
-"opensource.org/docs/definition.html</ulink>. The following quote from the "
-"OSI home page summarizes the key aspects as they relate to JBoss nicely:"
-msgstr ""
-"开源软件背后的基本逻辑很简单:当程序员可以读取、分发和修改源代码时,软件就会进步。人们改进它、采用它并修复错误。对于习惯于传统软件开发的慢节奏的人来说,开源软件的开发速度可能会让人感到惊奇。开源软件通常被误解为免费软件。Open Source "
-"Initiative (OSI) 网站提供了一些资源以定义开源软件的不同方面,其中包括:<ulink url=\"http://www.opensource.org/docs/definition.html\">http://www."
-"opensource.org/docs/definition.html</ulink>。OSI 主页上的如下内容很好的总结了和 JBoss 相关的关键概念:"
+msgid "The basic idea behind open source is very simple: When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing. Open Source is an often-misunderstood term relating to free software. The Open Source Initiative (OSI) web site provides a number of resources that define the various aspects of Open Source including an Open Source Definition at: <ulink url=\"http://www.opensource.org/docs/definition.html\">http://www.opensource.org/docs/definition.html</ulink>. The following quote from the OSI home page summarizes the key aspects as they relate to JBoss nicely:"
+msgstr "开源软件背后的基本逻辑很简单:当程序员可以读取、分发和修改源代码时,软件就会进步。人们改进它、采用它并修复错误。对于习惯于传统软件开发的慢节奏的人来说,开源软件的开发速度可能会让人感到惊奇。开源软件通常被误解为免费软件。Open Source Initiative (OSI) 网站提供了一些资源以定义开源软件的不同方面,其中包括:<ulink url=\"http://www.opensource.org/docs/definition.html\">http://www.opensource.org/docs/definition.html</ulink>。OSI 主页上的如下内容很好的总结了和 JBoss 相关的关键概念:"
 
 #. Tag: attribution
 #: About_Open_Source.xml:9
@@ -52,11 +38,7 @@
 #. Tag: para
 #: About_Open_Source.xml:9
 #, no-c-format
-msgid ""
-"We in the open source community have learned that this rapid evolutionary "
-"process produces better software than the traditional closed model, in which "
-"only very few programmers can see the source and everybody else must blindly "
-"use an opaque block of bits."
+msgid "We in the open source community have learned that this rapid evolutionary process produces better software than the traditional closed model, in which only very few programmers can see the source and everybody else must blindly use an opaque block of bits."
 msgstr ""
 
 #. Tag: para
@@ -68,10 +50,6 @@
 #. Tag: para
 #: About_Open_Source.xml:15
 #, no-c-format
-msgid ""
-"Open source software is an idea whose time has finally come. For twenty "
-"years it has been building momentum in the technical cultures that built the "
-"Internet and the World Wide Web. Now it&#39;s breaking out into the "
-"commercial world, and that&#39;s changing all the rules. Are you ready?"
-msgstr ""
+msgid "Open source software is an idea whose time has finally come. For twenty years it has been building momentum in the technical cultures that built the Internet and the World Wide Web. Now it&#39;s breaking out into the commercial world, and that&#39;s changing all the rules. Are you ready?"
+msgstr "开源软件的时代最终来临了。二十多年来,它已经成为了构建互联网和万维网的技术文化的里程碑。现在它进入了商业领域并将改变所有规则。你准备好了吗?"
 

Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po	2009-08-28 06:45:37 UTC (rev 92908)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po	2009-08-28 08:19:59 UTC (rev 92909)
@@ -9,7 +9,7 @@
 "Project-Id-Version: J2EE_Security_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-08-28 15:49+1000\n"
+"PO-Revision-Date: 2009-08-28 18:18+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -1690,7 +1690,7 @@
 #: J2EE_Security_On_JBOSS.xml:609
 #, no-c-format
 msgid "The second fundamental role of the <literal>JaasSecurityManagerService</literal> is to provide a JNDI <literal>javax.naming.spi.ObjectFactory</literal> implementation to allow for simple code-free management of the JNDI name to security manager implementation mapping. It has been mentioned that security is enabled by specifying the JNDI name of the security manager implementation via the <literal>security-domain</literal> deployment descriptor element. When you specify a JNDI name, there has to be an object-binding there to use. To simplify the setup of the JNDI name to security manager bindings, the <literal>JaasSecurityManagerService</literal> manages the association of security manager instances to names by binding a next naming system reference with itself as the JNDI ObjectFactory under the name <literal>java:/jaas</literal>. This allows one to use a naming convention of the form <literal>java:/jaas/XYZ</literal> as the value for the <literal>security-domain</li!
 teral> element, and the security manager instance for the <literal>XYZ</literal> security domain will be created as needed for you. The security manager for the domain <literal>XYZ</literal> is created on the first lookup against the <literal>java:/jaas/XYZ</literal> binding by creating an instance of the class specified by the <literal>SecurityManagerClassName</literal> attribute using a constructor that takes the name of the security domain. For example, consider the following container security configuration snippet:"
-msgstr ""
+msgstr "<literal>JaasSecurityManagerService</literal> 的第二个基本角色是提供 JNDI <literal>javax.naming.spi.ObjectFactory</literal> 实现来允许对 JNDI 名称和安全管理者实现之间的映射的简单无代码管理。我们已经提到通过 <literal>security-domain</literal> 部署描述符元素指定安全管理者实现的 JNDI 名称可以启用安全性。当你指定一个 JNDI 名称时,你可以使用对象绑定。为了简化 JNDI 名称和安全管理者绑定的映射的设置,<literal>JaasSecurityManagerService</literal> 通过把下一个命名系统引用和自己进行绑定在 <literal>java:/jaas</literal> 下面,管理安全管理者实例和名称间的关系。<literal>JaasSecurityManagerService</literal> 在第一次查找 <literal>java:/jaas/XYZ</literal> 绑定时就创建了 <literal>XYZ</literal> 域的安全管理者,这是通过由 <literal>SecurityManagerClassName</literal> 属性指定的类的实例来创建的。!
 例如,考虑下面的容器安全性配置片段:"
 
 #. Tag: programlisting
 #: J2EE_Security_On_JBOSS.xml:612
@@ -1718,19 +1718,19 @@
 #: J2EE_Security_On_JBOSS.xml:616
 #, no-c-format
 msgid "The <literal>JaasSecurityManagerService</literal> MBean is configured by default for use in the standard JBoss distribution, and you can often use the default configuration as is. The configurable attributes of the <literal>JaasSecurityManagerService</literal> include:"
-msgstr ""
+msgstr "标准 JBoss 版本里缺省配置了 <literal>JaasSecurityManagerService</literal> MBean,你可以经常使用缺省的配置。<literal>JaasSecurityManagerService</literal> 的可配置属性包括:"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:621
 #, no-c-format
 msgid "<emphasis role=\"bold\">SecurityManagerClassName</emphasis>: The name of the class that provides the security manager implementation. The implementation must support both the <literal>org.jboss.security.AuthenticationManager</literal> and <literal>org.jboss.security.RealmMapping</literal> interfaces. If not specified this defaults to the JAAS-based <literal>org.jboss.security.plugins.JaasSecurityManager</literal>."
-msgstr ""
+msgstr "<emphasis role=\"bold\">SecurityManagerClassName</emphasis>:提供安全管理者实现的类的名称。这个实现必须支持 <literal>org.jboss.security.AuthenticationManager</literal> 和 <literal>org.jboss.security.RealmMapping</literal> 接口。如果没有指定,它缺省为基于 JAAS 的 <literal>org.jboss.security.plugins.JaasSecurityManager</literal>。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:626
 #, no-c-format
 msgid "<emphasis role=\"bold\">CallbackHandlerClassName</emphasis>: The name of the class that provides the <literal>javax.security.auth.callback.CallbackHandler</literal> implementation used by the <literal>JaasSecurityManager</literal>. You can override the handler used by the <literal>JaasSecurityManager</literal> if the default implementation (<literal>org.jboss.security.auth.callback.SecurityAssociationHandler</literal>) does not meet your needs. This is a rather deep configuration that generally should not be set unless you know what you are doing."
-msgstr ""
+msgstr "<emphasis role=\"bold\">CallbackHandlerClassName</emphasis>:提供 <literal>JaasSecurityManager</literal> 使用的 <literal>javax.security.auth.callback.CallbackHandler</literal> 实现的类的名称。如果缺省的实现(<literal>org.jboss.security.auth.callback.SecurityAssociationHandler</literal>)不符合你的要求,你可以覆盖 <literal>JaasSecurityManager</literal> 使用的处理程序。这是相当深入的配置方式,除非有必要,你通常不应该进行设置。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:631
@@ -1742,7 +1742,7 @@
 #: J2EE_Security_On_JBOSS.xml:636
 #, no-c-format
 msgid "<emphasis role=\"bold\">AuthenticationCacheJndiName</emphasis>: Specifies the location of the security credential cache policy. This is first treated as an <literal>ObjectFactory</literal> location capable of returning <literal>CachePolicy</literal> instances on a per-security-domain basis. This is done by appending the name of the security domain to this name when looking up the <literal>CachePolicy</literal> for a domain. If this fails, the location is treated as a single <literal>CachePolicy</literal> for all security domains. As a default, a timed cache policy is used."
-msgstr ""
+msgstr "<emphasis role=\"bold\">AuthenticationCacheJndiName</emphasis>:指定安全性 credential 缓存策略的位置。它首先被作为能够为每个安全域返回 <literal>CachePolicy</literal> 实例的 <literal>ObjectFactory</literal> 对待。这是通过在查找 <literal>CachePolicy</literal> 时把安全域的名称附加到这个名称上来实现的。如果没有成功,其位置将被作为用于所有安全域的单一 <literal>CachePolicy</literal> 对待。在缺省情况下使用定时的缓存策略(Timed Cache Policy)。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:641
@@ -1760,26 +1760,26 @@
 #: J2EE_Security_On_JBOSS.xml:651
 #, no-c-format
 msgid "<emphasis role=\"bold\">DefaultUnauthenticatedPrincipal</emphasis>: Specifies the principal to use for unauthenticated users. This setting makes it possible to set default permissions for users who have not been authenticated."
-msgstr ""
+msgstr "<emphasis role=\"bold\">DefaultUnauthenticatedPrincipal</emphasis>:指定用于未验证用户的 principal。这个设置使为还未验证的用户设置缺省权限成为可能。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:656
 #, no-c-format
 msgid "The <literal>JaasSecurityManagerService</literal> also supports a number of useful operations. These include flushing any security domain authentication cache at runtime, getting the list of active users in a security domain authentication cache, and any of the security manager interface methods."
-msgstr ""
+msgstr "<literal>JaasSecurityManagerService</literal> 也支持大量有用的操作。这包括在运行时冲刷安全域验证缓存、获取安全域验证缓存里的活动用户列表以及任何安全管理者接口方法。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:659
 #, no-c-format
 msgid "Flushing a security domain authentication cache can be used to drop all cached credentials when the underlying store has been updated and you want the store state to be used immediately. The MBean operation signature is: <literal>public void flushAuthenticationCache(String securityDomain)</literal>."
-msgstr ""
+msgstr "冲刷安全域验证缓存可用于当底层的存储已经更新而你希望马上使用存储状态时删除所有缓存的 credential。这个 MBean 操作的签名是:<literal>public void flushAuthenticationCache(String securityDomain)</literal>。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:662
 #: J2EE_Security_On_JBOSS.xml:669
 #, no-c-format
 msgid "This can be invoked programmatically using the following code snippet:"
-msgstr ""
+msgstr "这可以用下面的代码在程序里进行调用:"
 
 #. Tag: programlisting
 #: J2EE_Security_On_JBOSS.xml:665
@@ -1803,7 +1803,7 @@
 #: J2EE_Security_On_JBOSS.xml:666
 #, no-c-format
 msgid "Getting the list of active users provides a snapshot of the <literal>Principals</literal> keys in a security domain authentication cache that are not expired. The MBean operation signature is: <literal>public List getAuthenticationCachePrincipals(String securityDomain)</literal>."
-msgstr ""
+msgstr "获取活动用户的列表提供了安全域验证缓存里没有过期的 <literal>Principals</literal> 主键的快照。这个 MBean 操作的签名是:<literal>public List getAuthenticationCachePrincipals(String securityDomain)</literal>。"
 
 #. Tag: programlisting
 #: J2EE_Security_On_JBOSS.xml:672
@@ -1993,43 +1993,43 @@
 #: J2EE_Security_On_JBOSS.xml:780
 #, no-c-format
 msgid "The <literal>name</literal> attribute of the <literal>application-policy</literal> is the login configuration name. Applications policy elements will be bound by that name in JNDI under the the <literal>java:/jaas</literal> context. Applications will link to security domains through this JNDI name in their deployment descriptors. (See the <literal>security-domain</literal> elements in <literal>jboss.xml</literal>, <literal>jboss-web.xml</literal> and <literal>jboss-service.xml</literal> files for examples)"
-msgstr ""
+msgstr "<literal>application-policy</literal> 的 <literal>name</literal> 属性是登录配置的名称。应用程序的 policy 元素将绑定在 JNDI  <literal>java:/jaas</literal> 上下文里。应用程序将在部署描述符里通过这个 JNDI 名称链接到安全域。(请参考 <literal>jboss.xml</literal>、<literal>jboss-web.xml</literal> 和 <literal>jboss-service.xml</literal> 文件里的 <literal>security-domain</literal> 元素)"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:783
 #, no-c-format
 msgid "The <literal>code</literal> attribute of the <literal>login-module</literal> element specifies the class name of the login module implementation. The <literal>required</literal> flag attribute controls the overall behavior of the authentication stack. The allowed values and meanings are:"
-msgstr ""
+msgstr "<literal>login-module</literal> 元素的 <literal>code</literal> 属性指定登录模块实现的类名。 <literal>required</literal> 标记控制验证栈的总体行为。它所允许的值和相应描述是:"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:788
 #, no-c-format
 msgid "<emphasis role=\"bold\">required</emphasis>: The login module is required to succeed for the authentication to be successful. If any required module fails, the authentication will fail. The remaining login modules in the stack will be called regardless of the outcome of the authentication."
-msgstr ""
+msgstr "<emphasis role=\"bold\">required</emphasis>:验证的成功要求这个登录模块运行成功。如果任何模块执行失败,验证将失败。不管验证的结果,栈里其他的登录模块将被调用。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:793
 #, no-c-format
 msgid "<emphasis role=\"bold\">requisite</emphasis>: The login module is required to succeed. If it succeeds, authentication continues down the login stack. If it fails, control immediately returns to the application."
-msgstr ""
+msgstr "<emphasis role=\"bold\">requisite</emphasis>:登录模块必须成功。如果成功,验证将继续执行登录栈。如果失败,应用程序将马山接管控制权。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:798
 #, no-c-format
 msgid "<emphasis role=\"bold\">sufficient</emphasis>: The login module is not required to succeed. If it does succeed, control immediately returns to the application. If it fails, authentication continues down the login stack."
-msgstr ""
+msgstr "<emphasis role=\"bold\">sufficient</emphasis>:不要求登录模块运行成功。如果成功,控制权马上返回应用程序。如果失败,应用程序继续执行登录栈。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:803
 #, no-c-format
 msgid "<emphasis role=\"bold\">optional</emphasis>: The login module is not required to succeed. Authentication still continues to proceed down the login stack regardless of whether the login module succeeds or fails."
-msgstr ""
+msgstr "<emphasis role=\"bold\">optional</emphasis>:不要求这个登录模块成功运行。不管这个登录模块成功与否,验证仍然可以继续。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:808
 #, no-c-format
 msgid "The following example shows the definition of a security domain that uses multiple login modules. Since both modules are marked as sufficient, only one of them need to succeed for login to proceed."
-msgstr ""
+msgstr "下面的例子展示了使用了多个登录模块的安全域。既然这两个模块都标记为 sufficient,登录成功处理只需要其中一个成功。"
 
 #. Tag: programlisting
 #: J2EE_Security_On_JBOSS.xml:811
@@ -2065,13 +2065,13 @@
 #: J2EE_Security_On_JBOSS.xml:812
 #, no-c-format
 msgid "Each login module has its own set of configuration options. These are set as name/value pairs using the <literal>module-option</literal> elements. We&#39;ll cover module options in more depth when we look at the individual login modules available in JBoss AS."
-msgstr ""
+msgstr "每个登录模块都有自己的配置选项集。它们用 <literal>module-option</literal> 元素设置成名称/值对。我们将在介绍 JBoss AS 的单个登录模块时对此进一步讨论。"
 
 #. Tag: title
 #: J2EE_Security_On_JBOSS.xml:816
 #, no-c-format
 msgid "Loading Security Domains"
-msgstr ""
+msgstr "加载安全域"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:817
@@ -2103,13 +2103,13 @@
 #: J2EE_Security_On_JBOSS.xml:826
 #, no-c-format
 msgid "<emphasis role=\"bold\">ConfigURL</emphasis>: specifies the URL of the XML login configuration file that should be loaded by this MBean on startup. This must be a valid URL string representation."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ConfigURL</emphasis>:指定应该被这个 MBean 在启动时加载的 XML 登录配置的 URL。这必须是有效的 URL 字符串。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:831
 #, no-c-format
 msgid "<emphasis role=\"bold\">ConfigResource</emphasis>: specifies the resource name of the XML login configuration file that should be loaded by this MBean on startup. The name is treated as a classpath resource for which a URL is located using the thread context class loader."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ConfigResource</emphasis>:指定这个 MBean 应该在启动时加载的 XML 配置文件的资源名。这个名称被作为 URL 使用线程上下文类加载器定位时使用的 classpath 资源对待。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:836
@@ -2577,7 +2577,7 @@
 #: J2EE_Security_On_JBOSS.xml:1037
 #, no-c-format
 msgid "The following would be equivalent definitions for the <literal>jduke</literal> username:"
-msgstr ""
+msgstr "下面是和 <literal>jduke</literal> 用户名相等的定义:"
 
 #. Tag: programlisting
 #: J2EE_Security_On_JBOSS.xml:1040
@@ -2626,7 +2626,7 @@
 #: J2EE_Security_On_JBOSS.xml:1063
 #, no-c-format
 msgid "The <literal>LdapLoginModule</literal> is a <literal>LoginModule</literal> implementation that authenticates against an LDAP server. You would use the <literal>LdapLoginModule</literal> if your username and credentials are stored in an LDAP server that is accessible using a JNDI LDAP provider."
-msgstr ""
+msgstr "<literal>LdapLoginModule</literal> 是一个根据 LDAP 服务器进行验证的 <literal>LoginModule</literal> 实现。如果你的用户名和 credential 存储在可用 JNDI LDAP 提供者访问的 LDAP服务器里时,你可以使用 <literal>LdapLoginModule</literal>。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:1066
@@ -2662,13 +2662,13 @@
 #: J2EE_Security_On_JBOSS.xml:1091
 #, no-c-format
 msgid "<emphasis role=\"bold\">java.naming.security.principal</emphasis>: The principal for authenticating the caller to the service. This is built from other properties as described below."
-msgstr ""
+msgstr "<emphasis role=\"bold\">java.naming.security.principal</emphasis>:验证调用者使用的 principal。它根据下面的描述的其他属性进行构建。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:1096
 #, no-c-format
 msgid "<emphasis role=\"bold\">java.naming.security.credentials</emphasis>: The value of the property depends on the authentication scheme. For example, it could be a hashed password, clear-text password, key, certificate, and so on."
-msgstr ""
+msgstr "<emphasis role=\"bold\">java.naming.security.credentials</emphasis>:属性的值取决于验证模式。利润,它可以是 hashed 密码、明文密码、密钥、证书等。"
 
 #. Tag: para
 #: J2EE_Security_On_JBOSS.xml:1106




More information about the jboss-cvs-commits mailing list