[jboss-cvs] JBossAS SVN: r102496 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Mar 16 22:18:45 EDT 2010
Author: xhuang at jboss.com
Date: 2010-03-16 22:18:44 -0400 (Tue, 16 Mar 2010)
New Revision: 102496
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_JBoss.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Professional_Open_Source.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Architecture.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Author_Group.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po
Log:
update
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_JBoss.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_JBoss.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_JBoss.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:17:59\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-03-17 11:07+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,100 +22,39 @@
msgstr "关于 JBoss"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<indexterm><primary>JBoss</primary><secondary>about</secondary></indexterm> "
-"<indexterm><primary>JBoss</primary><secondary>relation to Red Hat</"
-"secondary></indexterm> 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 <indexterm><primary>Service-"
-"Oriented Architecture</primary><secondary>SOA</secondary></indexterm>Service-"
-"Oriented Architecture (SOA)."
-msgstr ""
-"JBoss，作为红帽的一个部门，是开源中间件软件的全球领导者，它把企业级的 JEMS 开"
-"源软件和行业领先的服务和工具结合在一起，提供了把企业转向面向服务构建"
-"（Service-Oriented Architecture，SOA）的更好途径。"
+#, no-c-format
+msgid "<indexterm><primary>JBoss</primary><secondary>about</secondary></indexterm> <indexterm><primary>JBoss</primary><secondary>relation to Red Hat</secondary></indexterm> 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 <indexterm><primary>Service-Oriented Architecture</primary><secondary>SOA</secondary></indexterm>Service-Oriented Architecture (SOA)."
+msgstr "<indexterm><primary>JBoss</primary><secondary>about</secondary></indexterm> <indexterm><primary>JBoss</primary><secondary>relation to Red Hat</secondary></indexterm>JBoss，作为红帽的一个部门，是开源中间件软件的全球领导者，它把企业级的 JEMS 开源软件和行业领先的服务和工具结合在一起，提供了把企业转向面向服务构建 <indexterm><primary>Service-Oriented Architecture</primary><secondary>SOA</secondary></indexterm>Service-Oriented Architecture (SOA) 的更好途径。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<indexterm><primary>JBoss</primary><secondary>and Professional Open Source</"
-"secondary></indexterm> <indexterm><primary>Professional Open Source</"
-"primary><secondary>JBoss</secondary></indexterm> 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 提倡开创性的专业开源模型，组合最好的开源和私有软件，为企业提供安全的开"
-"源选择 "
+#, no-c-format
+msgid "<indexterm><primary>JBoss</primary><secondary>and Professional Open Source</secondary></indexterm> <indexterm><primary>Professional Open Source</primary><secondary>JBoss</secondary></indexterm> 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 "<indexterm><primary>JBoss</primary><secondary>and Professional Open Source</secondary></indexterm> <indexterm><primary>Professional Open Source</primary><secondary>JBoss</secondary></indexterm> JBoss 提倡开创性的专业开源模型，组合最好的开源和私有软件，为企业提供安全的开源选择。这包括免费软件、透明部署、开源社区以及传统软件供应商所有的责任和专业支持服务。公司寻找具有开创性的开源项目、通过雇用顶尖开发人员（通常是创始者）将其从嗜好转变成专业软件。JBoss 提供资源、核心开发和支持服务以把流行的开源项目扩展为企业级软件。"
#. Tag: para
#, 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."
-msgstr ""
-"<emphasis>覆盖范围</emphasis>：为北美和欧洲提供直接服务，对世界其他地区通过授"
-"权的合作网络提供服务。"
+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
-#, fuzzy, no-c-format
-msgid ""
-"<emphasis>Mission Statement:</emphasis> <indexterm><primary>Mission "
-"Statement</primary></indexterm> JBoss' 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 ""
-"<emphasis>任务宣示：</emphasis> JBoss 的任务是改革企业级中间件软件构建、分发"
-"以及通过专业开源模式进行支持的方式。我们承诺提供富有创新和高品质的技术和服"
-"务，使 JBoss 成为企业和软件供应商的安全选择。"
+#, no-c-format
+msgid "<emphasis>Mission Statement:</emphasis> <indexterm><primary>Mission Statement</primary></indexterm> JBoss' 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 "<emphasis>任务宣示：</emphasis> <indexterm><primary>Mission Statement</primary></indexterm> JBoss 的任务是改革企业级中间件软件构建、分发以及通过专业开源模式进行支持的方式。我们承诺提供富有创新和高品质的技术和服务，使 JBoss 成为企业和软件供应商的安全选择。"
#. Tag: para
#, 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."
-msgstr ""
-"<emphasis>客户：</emphasis> 企业级客户把 JBoss 技术部署在执行关键任务的应用程"
-"序并使用 JBoss 的专业服务，这些客户包括 Aviva Canada、Continental Airlines、"
-"La Quinta、NLG、MCI、Nielsen Media Research 和 Travelocity。关于客户的成功案"
-"例，请访问 <ulink url=\"http://www.jboss.com/customers/index\">Customers</"
-"ulink>。"
+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 "<emphasis>客户：</emphasis> 企业级客户把 JBoss 技术部署在执行关键任务的应用程序并使用 JBoss 的专业服务，这些客户包括 Aviva Canada、Continental Airlines、La Quinta、NLG、MCI、Nielsen Media Research 和 Travelocity。关于客户的成功案例，请访问 <ulink url=\"http://www.jboss.com/customers/index\">Customers</ulink>。"
#. Tag: para
#, 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."
-msgstr ""
-"<emphasis>合作伙伴：</emphasis> JBoss 和软件和硬件供应商、系统集成商、OEM 一"
-"起合作以提供实施服务、前端支持以及嵌入 JBoss 技术的产品的认证。关于 JBoss 认"
-"证合作伙伴计划的详细信息，请访问 <ulink url=\"http://www.jboss.com/partners/"
-"index\">Partners</ulink>。"
+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 "<emphasis>合作伙伴：</emphasis> JBoss 和软件和硬件供应商、系统集成商、OEM 一起合作以提供实施服务、前端支持以及嵌入 JBoss 技术的产品的认证。关于 JBoss 认证合作伙伴计划的详细信息，请访问 <ulink url=\"http://www.jboss.com/partners/index\">Partners</ulink>。"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Professional Open Source™ from JBoss Inc. offers you:"
-msgstr "JBoss Inc. 的 Professional Open Source(tm) 为你提供："
+msgstr "JBoss Inc. 的 Professional Open Source™ 为你提供："
#. Tag: para
#, no-c-format
@@ -134,16 +73,8 @@
#. Tag: para
#, 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 ""
-"完备的服务，包括 <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>"
+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
#, no-c-format
@@ -152,12 +83,8 @@
#. Tag: para
#, no-c-format
-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>组成的遍布全世界的网络。"
+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
#, no-c-format
@@ -211,3 +138,4 @@
#, fuzzy
#~ msgid "<emphasis>Mission Statement:</emphasis>"
#~ msgstr "<emphasis>将终端打包</emphasis>"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Open_Source.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:17:59\n"
-"PO-Revision-Date: 2010-02-10 12:20+1000\n"
+"PO-Revision-Date: 2010-03-17 10:54+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -22,25 +22,9 @@
msgstr "关于开源软件"
#. Tag: para
-#, fuzzy, 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<indexterm><primary>OSI</primary></indexterm> (OSI) web site "
-"provides a number of resources that define the various aspects of Open "
-"Source including an Open Source Definition<indexterm><primary>Open Source "
-"Definition</primary></indexterm> 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 ""
-"开源软件背后的基本逻辑很简单：当程序员可以读取、分发和修改源代码时，软件就会"
-"进步。人们改进它、采用它并修复错误。对于习惯于传统软件开发的慢节奏的人来说，"
-"开源软件的开发速度可能会让人感到惊奇。开源软件通常被误解为免费软件。"
+#, 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<indexterm><primary>OSI</primary></indexterm> (OSI) web site provides a number of resources that define the various aspects of Open Source including an Open Source Definition<indexterm><primary>Open Source Definition</primary></indexterm> 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）<indexterm><primary>OSI</primary></indexterm> (OSI) 的网站提供了大量定义开源软件的资源，其中包括 Open Source Definition<indexterm><primary>Open Source Definition</primary></indexterm>：<ulink url=\"http://www.opensource.org/docs/definition.html\">http://www.opensource.org/docs/definition.html</ulink>。下面对 OSI 主页的引用总结了和 JBoss 相关的关键概念。"
#. Tag: title
#, no-c-format
@@ -49,45 +33,29 @@
#. Tag: para
#, 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."
-msgstr ""
-"我们从开源社区认识到快速改良方式比传统的封闭模式（只有极少的程序员可以看到代"
-"码、而其他人只能盲目的使用一些不透明的模块）能更快的开发软件。"
+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
#, no-c-format
-msgid ""
-"Open Source Initiative exists to make this case to the commercial world."
+msgid "Open Source Initiative exists to make this case to the commercial world."
msgstr "开源促进会使这种方式进入到商业领域。"
#. Tag: para
#, 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's breaking out into the commercial "
-"world, and that'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's breaking out into the commercial world, and that's changing all the rules. Are you ready?"
+msgstr "开源软件的时代最终来临了。二十多年来，它已经成为了构建互联网和万维网的技术文化的里程碑。现在它进入了商业领域并将改变所有规则。你准备好了吗？ "
#~ msgid "OSI"
#~ msgstr "OSI"
-
#~ msgid ""
#~ "(OSI) web site provides a number of resources that define the various "
#~ "aspects of Open Source including an Open Source Definition"
#~ msgstr ""
#~ "(OSI) 网站提供了一些定义不同的开源概念的资源，其终包括 Open Source "
#~ "Definition。"
-
#~ msgid "Open Source Definition"
#~ msgstr "开源软件定义（Open Source Definition）"
-
#~ msgid ""
#~ "at: <ulink url=\"http://www.opensource.org/docs/definition.html\">http://"
#~ "www.opensource.org/docs/definition.html</ulink>. The following quote from "
@@ -97,3 +65,4 @@
#~ "它位于 <ulink url=\"http://www.opensource.org/docs/definition.html"
#~ "\">http://www.opensource.org/docs/definition.html</ulink>。OSI 主页里的以"
#~ "下引用很好地总结了和 JBoss 相关的关键性的内容："
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Professional_Open_Source.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Professional_Open_Source.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/About_Professional_Open_Source.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:17:59\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-03-17 11:07+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,62 +22,36 @@
msgstr "关于专业开源软件"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<indexterm><primary>Professional Open Source</"
-"primary><secondary>methodology</secondary></indexterm> "
-"<indexterm><primary>POS</primary><see>Professional Open Source</see></"
-"indexterm> JBoss is the leader in the second generation of open source, "
-"which we have termed Professional Open Source. The Professional Open Source "
-"methodology is based on the following:"
-msgstr ""
-"JBoss 是第二代开源软件、也就是我们所说的专业开源软件的领导者。专业开源软件的"
-"方法基于："
+#, no-c-format
+msgid "<indexterm><primary>Professional Open Source</primary><secondary>methodology</secondary></indexterm> <indexterm><primary>POS</primary><see>Professional Open Source</see></indexterm> JBoss is the leader in the second generation of open source, which we have termed Professional Open Source. The Professional Open Source methodology is based on the following:"
+msgstr "<indexterm><primary>Professional Open Source</primary><secondary>methodology</secondary></indexterm> <indexterm><primary>POS</primary><see>Professional Open Source</see></indexterm> JBoss 是第二代开源软件、也就是我们所说的专业开源软件的领导者。专业开源软件的方法基于："
#. Tag: para
#, no-c-format
-msgid ""
-"We hire and pay experts in the open source community to write exceptional "
-"and innovative software full-time."
+msgid "We hire and pay experts in the open source community to write exceptional and innovative software full-time."
msgstr "我们雇佣开源社区里的专家以全职编写特别而富有创新的软件。"
#. Tag: para
#, no-c-format
-msgid ""
-"We only use open source licenses that are friendly to end-user IT shops, "
-"independent software vendors, and the community itself."
+msgid "We only use open source licenses that are friendly to end-user IT shops, independent software vendors, and the community itself."
msgstr "我们只使用对于终端用户、独立的软件供应商和社区开放的开源许可证。"
#. Tag: para
#, no-c-format
-msgid ""
-"Directly and through our authorized partners, we deliver the best support "
-"services available; all of which are backed up by the real product experts."
-msgstr ""
-"我们通过所授权的合作伙伴或者直接地提供最好的服务；这些服务都由真正的产品专家"
-"进行支持。"
+msgid "Directly and through our authorized partners, we deliver the best support services available; all of which are backed up by the real product experts."
+msgstr "我们通过所授权的合作伙伴或者直接地提供最好的服务；这些服务都由真正的产品专家进行支持。"
#. Tag: para
#, no-c-format
-msgid ""
-"Unlike first generation open source providers, we control the direction and "
-"source code for our projects. We can ensure that all bug fixes and patches "
-"are rolled into future versions of our products."
-msgstr ""
-"和第一代开源软件的提供者不同，我们控制项目的方向和源代码。我们可以保证所有对"
-"程序错误的修复和补丁可以出现在后续的版本里。"
+msgid "Unlike first generation open source providers, we control the direction and source code for our projects. We can ensure that all bug fixes and patches are rolled into future versions of our products."
+msgstr "和第一代开源软件的提供者不同，我们控制项目的方向和源代码。我们可以保证所有对程序错误的修复和补丁可以出现在后续的版本里。"
#. Tag: para
#, no-c-format
-msgid ""
-"By combining enterprise-proven technology, business-friendly open source "
-"licenses, and world-class support services, we have made Professional Open "
-"Source the safe choice for end-user enterprises and independent software "
-"vendors alike."
-msgstr ""
-"通过组合企业级的技术、开源许可证和世界级的支持服务，我们使得专业开源软件成为"
-"了企业和独立软件供应商的安全的选择。"
+msgid "By combining enterprise-proven technology, business-friendly open source licenses, and world-class support services, we have made Professional Open Source the safe choice for end-user enterprises and independent software vendors alike."
+msgstr "通过组合企业级的技术、开源许可证和世界级的支持服务，我们使得专业开源软件成为了企业和独立软件供应商的安全的选择。"
#, fuzzy
#~ msgid "Professional Open Source"
#~ msgstr "关于专业开源软件"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Architecture.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Architecture.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Architecture.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:17:59\n"
-"PO-Revision-Date: 2010-02-09 10:34+1000\n"
+"PO-Revision-Date: 2010-03-17 10:52+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -22,25 +22,14 @@
msgstr "Boss 企业级应用程序平台 5 的架构"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<indexterm><primary>JBoss Enterprise Application Platform</"
-"primary><secondary>architecture</secondary></indexterm> The following "
-"diagram illustrates an overview of the JBoss Enterprise Application Server "
-"and its components. <inlinemediaobject> <imageobject> <imagedata fileref="
-"\"images/jboss-as-components.png\" /> </imageobject> </inlinemediaobject>"
-msgstr ""
-"下图是对 JBoss 企业级应用服务器及其组件的概述。inlinemediaobject> "
-"<imageobject> <imagedata fileref=\"images/jboss-as-components.png\" /> </"
-"imageobject> </inlinemediaobject>"
+#, no-c-format
+msgid "<indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>architecture</secondary></indexterm> The following diagram illustrates an overview of the JBoss Enterprise Application Server and its components. <inlinemediaobject> <imageobject> <imagedata fileref=\"images/jboss-as-components.png\" /> </imageobject> </inlinemediaobject>"
+msgstr "<indexterm><primary>JBoss Enterprise Application Platform</primary><secondary>architecture</secondary></indexterm> 下图是对 JBoss 企业级应用服务器及其组件的概述。inlinemediaobject> <imageobject> <imagedata fileref=\"images/jboss-as-components.png\" /> </imageobject> </inlinemediaobject>"
#. Tag: para
#, no-c-format
-msgid ""
-"The directory structure of JBoss Enterprise Application Platform 5 resembles "
-"that of the 4.x series with some notable differences:"
-msgstr ""
-"JBoss 企业级应用程序平台 5 的目录结构和 4.x 系列类似但有一些值得注意的区别："
+msgid "The directory structure of JBoss Enterprise Application Platform 5 resembles that of the 4.x series with some notable differences:"
+msgstr "JBoss 企业级应用程序平台 5 的目录结构和 4.x 系列类似但有一些值得注意的区别："
#. Tag: title
#, no-c-format
@@ -49,61 +38,18 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The JBoss Enterprise Application Platform 5 bootstrap is similar to the "
-"JBoss Enterprise Application Platform 4.x versions in that the org.jboss."
-"Main entry point loads an org.jboss.system.server.Server implementation. In "
-"JBoss Enterprise Application Platform 4.x this was a JMX based microkernel. "
-"In JBoss Enterprise Application Platform 5 this is a JBoss Microcontainer."
-msgstr ""
-"根据 org.jboss.Main 入口点加载 org.jboss.system.server.Server 来看，JBoss 企"
-"业级应用程序平台 5 bootstrap 和 4.x 版本的类似。在 4.x 李，这是一个基于 JMX "
-"的微内核。在 JBoss 企业级应用程序平台 5 里就是 JBoss 微容器"
-"（Microcontainer）。"
+msgid "The JBoss Enterprise Application Platform 5 bootstrap is similar to the JBoss Enterprise Application Platform 4.x versions in that the org.jboss.Main entry point loads an org.jboss.system.server.Server implementation. In JBoss Enterprise Application Platform 4.x this was a JMX based microkernel. In JBoss Enterprise Application Platform 5 this is a JBoss Microcontainer."
+msgstr "根据 org.jboss.Main 入口点加载 org.jboss.system.server.Server 来看，JBoss 企业级应用程序平台 5 bootstrap 和 4.x 版本的类似。在 4.x 李，这是一个基于 JMX 的微内核。在 JBoss 企业级应用程序平台 5 里就是 JBoss 微容器（Microcontainer）。"
#. Tag: para
#, no-c-format
-msgid ""
-"The default JBoss Enterprise Application Platform 5 <classname>org.jboss."
-"system.server.Server implementation</classname> is <classname>org.jboss."
-"bootstrap.microcontainer.ServerImpl</classname>. This implementation is an "
-"extension of the kernel basic bootstrap that boots the MC from the bootstrap "
-"beans declared in <filename>{jboss.server.config.url}/bootstrap.xml</"
-"filename> descriptors using a <classname>BasicXMLDeployer</classname>. In "
-"addition, the <classname>ServerImpl</classname> registers install callbacks "
-"for any beans that implement the <classname>org.jboss.bootstrap.spi."
-"Bootstrap</classname> interface. The <filename>bootstrap/profile*.xml</"
-"filename> configurations include a <classname>ProfileServiceBootstrap</"
-"classname> bean that implements the Bootstrap interface."
-msgstr ""
-"缺省的 JBoss 企业级应用程序平台 5 的 <classname>org.jboss.system.server."
-"Server</classname> 实现是 <classname>org.jboss.bootstrap.microcontainer."
-"ServerImpl</classname>。这个实现是引导 <filename>{jboss.server.config.url}/"
-"bootstrap.xml</filename> 里 <classname>BasicXMLDeployer</classname> 声明的 "
-"bootstrap bean 里的 MC 的内核基本 bootstrap 的扩展。此外，"
-"<classname>ServerImpl</classname> 为实现 <classname>org.jboss.bootstrap.spi."
-"Bootstrap</classname> 接口的任何 Bean 注册 install 回调函数。"
-"<filename>bootstrap/profile*.xml</filename> 配置包括了一个 "
-"<classname>ProfileServiceBootstrap</classname> bean，它实现了 Bootstrap 接"
-"口。"
+msgid "The default JBoss Enterprise Application Platform 5 <classname>org.jboss.system.server.Server implementation</classname> is <classname>org.jboss.bootstrap.microcontainer.ServerImpl</classname>. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in <filename>{jboss.server.config.url}/bootstrap.xml</filename> descriptors using a <classname>BasicXMLDeployer</classname>. In addition, the <classname>ServerImpl</classname> registers install callbacks for any beans that implement the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface. The <filename>bootstrap/profile*.xml</filename> configurations include a <classname>ProfileServiceBootstrap</classname> bean that implements the Bootstrap interface."
+msgstr "缺省的 JBoss 企业级应用程序平台 5 的 <classname>org.jboss.system.server.Server</classname> 实现是 <classname>org.jboss.bootstrap.microcontainer.ServerImpl</classname>。这个实现是引导 <filename>{jboss.server.config.url}/bootstrap.xml</filename> 里 <classname>BasicXMLDeployer</classname> 声明的 bootstrap bean 里的 MC 的内核基本 bootstrap 的扩展。此外，<classname>ServerImpl</classname> 为实现 <classname>org.jboss.bootstrap.spi.Bootstrap</classname> 接口的任何 Bean 注册 install 回调函数。<filename>bootstrap/profile*.xml</filename> 配置包括了一个 <classname>ProfileServiceBootstrap</classname> bean，它实现了 Bootstrap 接口。"
#. Tag: para
#, no-c-format
-msgid ""
-"The <classname>org.jboss.system.server.profileservice."
-"ProfileServiceBootstrap</classname> is an implementation of the "
-"<classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface that "
-"loads the deployments associated with the current profile. The <emphasis>"
-"{profile-name}</emphasis> is the name of the profile being loaded and "
-"corresponds to the <code>server -c</code> command line argument. The default "
-"<emphasis>{profile-name}</emphasis> is <emphasis>default</emphasis>. The "
-"deployers, deploy"
-msgstr ""
-"<classname>org.jboss.system.server.profileservice.ProfileServiceBootstrap</"
-"classname> 是 <classname>org.jboss.bootstrap.spi.Bootstrap</classname> 接口的"
-"实现，它加载和当前配置关联的部署。<emphasis>{profile-name}</emphasis> 是正加"
-"载的配置的名称，它对应 <code>server -c</code> 命令行参数。缺省的<emphasis>"
-"{profile-name}</emphasis> 是 <emphasis>default</emphasis>。部署这部署"
+msgid "The <classname>org.jboss.system.server.profileservice.ProfileServiceBootstrap</classname> is an implementation of the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface that loads the deployments associated with the current profile. The <emphasis>{profile-name}</emphasis> is the name of the profile being loaded and corresponds to the <code>server -c</code> command line argument. The default <emphasis>{profile-name}</emphasis> is <emphasis>default</emphasis>. The deployers, deploy"
+msgstr "<classname>org.jboss.system.server.profileservice.ProfileServiceBootstrap</classname> 是 <classname>org.jboss.bootstrap.spi.Bootstrap</classname> 接口的实现，它加载和当前配置关联的部署。<emphasis>{profile-name}</emphasis> 是正加载的配置的名称，它对应 <code>server -c</code> 命令行参数。缺省的<emphasis>{profile-name}</emphasis> 是 <emphasis>default</emphasis>。部署这部署"
#. Tag: title
#, no-c-format
@@ -112,52 +58,28 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Hot deployment in JBoss Enterprise Application Platform 5 is controlled by "
-"the <classname>Profile</classname> implementations associated with the "
-"<classname>ProfileService</classname>. The <classname>HDScanner</classname> "
-"bean deployed via the <filename>deploy/hdscanner-jboss-beans.xml</filename> "
-"MC deployment, queries the profile service for changes in application "
-"directory contents and redeploys updated content, undeploys removed content, "
-"and adds new deployment content to the current profile via the "
-"<classname>ProfileService</classname>."
-msgstr ""
-"JBoss 企业级应用程序平台 5 里的热部署由和 <classname>ProfileService</"
-"classname> 关联的 <classname>Profile</classname> 实现控制。通过 "
-"<filename>deploy/hdscanner-jboss-beans.xml</filename> MC 部署的 "
-"<classname>HDScanner</classname> bean 查询 profile 服务以获取应用程序目录内容"
-"的改动并通过 <classname>ProfileService</classname> 重新部署更新的内容、卸载已"
-"删除的内容、添加新的部署内容。"
+msgid "Hot deployment in JBoss Enterprise Application Platform 5 is controlled by the <classname>Profile</classname> implementations associated with the <classname>ProfileService</classname>. The <classname>HDScanner</classname> bean deployed via the <filename>deploy/hdscanner-jboss-beans.xml</filename> MC deployment, queries the profile service for changes in application directory contents and redeploys updated content, undeploys removed content, and adds new deployment content to the current profile via the <classname>ProfileService</classname>."
+msgstr "JBoss 企业级应用程序平台 5 里的热部署由和 <classname>ProfileService</classname> 关联的 <classname>Profile</classname> 实现控制。通过 <filename>deploy/hdscanner-jboss-beans.xml</filename> MC 部署的 <classname>HDScanner</classname> bean 查询 profile 服务以获取应用程序目录内容的改动并通过 <classname>ProfileService</classname> 重新部署更新的内容、卸载已删除的内容、添加新的部署内容。"
#. Tag: para
#, no-c-format
-msgid ""
-"Disabling hot deployment is achieved by removing the <filename>hdscanner-"
-"jboss-beans.xml</filename> file from deployment."
-msgstr ""
-"从部署里删除 <filename>hdscanner-jboss-beans.xml</filename> 文件可以禁用热部"
-"署。"
+msgid "Disabling hot deployment is achieved by removing the <filename>hdscanner-jboss-beans.xml</filename> file from deployment."
+msgstr "从部署里删除 <filename>hdscanner-jboss-beans.xml</filename> 文件可以禁用热部署。"
#~ msgid "JBoss Enterprise Application Platform"
#~ msgstr "JBoss 企业级应用程序平台"
-
#~ msgid "architecture"
#~ msgstr "架构"
-
#~ msgid "bootstrap"
#~ msgstr "bootstrap"
-
#~ msgid "Server interface implementation"
#~ msgstr "Server 接口的实现"
-
#~ msgid "ProfileService"
#~ msgstr "Profile 服务"
-
#~ msgid "Hot deployment"
#~ msgstr "热部署"
-
#~ msgid "implementation"
#~ msgstr "实现"
-
#~ msgid "disabling"
#~ msgstr "禁用热部署"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Author_Group.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Author_Group.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -1,9 +1,21 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"POT-Creation-Date: \n"
+"PO-Revision-Date: \n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=iso-8859-1\n"
+"Content-Transfer-Encoding: 8bit\n"
+
#. Tag: firstname
#, no-c-format
msgid "JBoss"
-msgstr ""
+msgstr "JBoss"
#. Tag: firstname
#, no-c-format
msgid "Isaac"
-msgstr ""
+msgstr "Isaac"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_EJBs.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:18:00\n"
-"PO-Revision-Date: 2010-03-09 12:22+1000\n"
+"PO-Revision-Date: 2010-03-17 11:00+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -147,14 +147,9 @@
msgstr "<literal>maxSize</literal> 指定缓存在用 LRU 算法钝化 bean 之前，可以缓存的 bean 的最大数目。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"<literal>idleTimeoutSeconds</literal> specifies the max period of time a "
-"bean can go unused before the cache should passivate it (regardless of "
-"whether maxSize beans are cached.)"
-msgstr ""
-"<literal>idleTimeoutSeconds</literal> 指定缓存在钝化 bean 之前（不管是否已经"
-"缓存了 maxSize 个 bean），这个 bean 可以空闲的最长时间。"
+#, no-c-format
+msgid "<literal>idleTimeoutSeconds</literal> specifies the max period of time a bean can go unused before the cache should passivate it (regardless of whether maxSize beans are cached.)"
+msgstr "<literal>idleTimeoutSeconds</literal> 指定缓存在钝化 bean 之前（不管是否已经缓存了 maxSize 个 bean），这个 bean 可以空闲的最长时间。 "
#. Tag: para
#, no-c-format
@@ -228,12 +223,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Using buddy replication, state is replicated to a configurable number of "
-"backup servers in the cluster (a.k.a. buddies), rather than to all servers "
-"in the cluster. To enable buddy replication, adjust the following properties "
-"in the <literal>buddyReplicationConfig</literal> property bean:"
-msgstr ""
+msgid "Using buddy replication, state is replicated to a configurable number of backup servers in the cluster (a.k.a. buddies), rather than to all servers in the cluster. To enable buddy replication, adjust the following properties in the <literal>buddyReplicationConfig</literal> property bean:"
+msgstr "如果使用 buddy 复制，状态将被复制到群集中可配置数目的备份服务器，而不是所有的服务器上。要启用 buddy 复制，你可以调整 <literal>buddyReplicationConfig</literal> property bean 里的下列属性："
#. Tag: para
#, no-c-format
@@ -311,21 +302,9 @@
msgstr "因为复制过程是很消耗资源的，为了优化这个过程，你可以选择性地在你的 bean 类里实现有下面的签名的方法："
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Before replicating your bean, the container will detect if your bean "
-"implements this method. If your bean does, the container calls the "
-"<literal>isModified()</literal> method and it only replicates the bean when "
-"the method returns <literal>true</literal>. If the bean has not been "
-"modified (or not enough to require replication, depending on your own "
-"preferences), you can return <literal>false</literal> and the replication "
-"would not occur."
-msgstr ""
-"在复制你的 bean 之前，容器（container）将检测 bean 是否实现了这个方法。如果"
-"是，容器会调用 <literal>isModified()</literal> 方法并只在方法返回 "
-"<literal>true</literal> 时复制这个 bean。如果 bean 还没被更改(或者还不够来请"
-"求复制，这取决于你的喜好，你可以返回 <literal>false</literal>，这样复制就不会"
-"发生。"
+#, no-c-format
+msgid "Before replicating your bean, the container will detect if your bean implements this method. If your bean does, the container calls the <literal>isModified()</literal> method and it only replicates the bean when the method returns <literal>true</literal>. If the bean has not been modified (or not enough to require replication, depending on your own preferences), you can return <literal>false</literal> and the replication would not occur."
+msgstr "在复制你的 bean 之前，容器（container）将检测 bean 是否实现了这个方法。如果是，容器会调用 <literal>isModified()</literal> 方法并只在方法返回 <literal>true</literal> 时复制这个 bean。如果 bean 还没被更改（或者还不够来请求复制，这取决于你的喜好），你可以返回 <literal>false</literal>，这样复制就不会发生。"
#. Tag: title
#, no-c-format
@@ -333,13 +312,9 @@
msgstr "HASessionStateService 配置"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The <literal>HASessionStateService</literal> bean is defined in the "
-"<code><profile>/deploy/cluster/ha-legacy-jboss-beans.xml</code> file."
-msgstr ""
-"<code>all/deploy/cluster-service.xml</code> 文件定义了 "
-"<literal>HASessionState</literal> 服务 MBean。"
+#, no-c-format
+msgid "The <literal>HASessionStateService</literal> bean is defined in the <code><profile>/deploy/cluster/ha-legacy-jboss-beans.xml</code> file."
+msgstr "<code><profile>/deploy/cluster/ha-legacy-jboss-beans.xml</code> 文件定义了 <literal>HASessionStateService</literal> 服务 MBean。"
#. Tag: para
#, no-c-format
@@ -367,34 +342,14 @@
msgstr "处理群集系统重启 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"We have covered the HA smart client architecture in <xref linkend="
-"\"clustering-concepts-arch-proxy\" />. The default HA smart proxy client can "
-"only failover as long as one node in the cluster exists. If there is a "
-"complete cluster shutdown, the proxy becomes orphaned and loses knowledge of "
-"the available nodes in the cluster. There is no way for the proxy to recover "
-"from this. The proxy needs to look up a fresh set of targets out of JNDI/HA-"
-"JNDI when the nodes are restarted."
-msgstr ""
-"我们已经在“客户端拦截器架构”章节介绍了 HA 智能客户端架构。缺省的 HA 智能代理"
-"客户端只能在群集里一个节点故障时进行失效切换（failover）。如果整个群集都关闭"
-"了，代理（proxy）将失去所有群集里可用节点的信息。在这种情况下，代理没有什么办"
-"法来恢复系统。当节点重启时，需要在 JNDI/HAJNDI 之外查找一系列全新的目标。"
+#, no-c-format
+msgid "We have covered the HA smart client architecture in <xref linkend=\"clustering-concepts-arch-proxy\" />. The default HA smart proxy client can only failover as long as one node in the cluster exists. If there is a complete cluster shutdown, the proxy becomes orphaned and loses knowledge of the available nodes in the cluster. There is no way for the proxy to recover from this. The proxy needs to look up a fresh set of targets out of JNDI/HA-JNDI when the nodes are restarted."
+msgstr "我们已经在“客户端拦截器架构”章节（<xref linkend=\"clustering-concepts-arch-proxy\" />）介绍了 HA 智能客户端架构。缺省的 HA 智能代理客户端只能在群集里一个节点故障时进行失效切换（failover）。如果整个群集都关闭了，代理（proxy）将失去所有群集里可用节点的信息。在这种情况下，代理没有什么办法来恢复系统。当节点重启时，需要在 JNDI/HAJNDI 之外查找一系列全新的目标。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"RetryInterceptor can be added to the proxy client side interceptor stack to "
-"allow for a transparent recovery from such a restart failure. To enable it "
-"for an EJB, setup an invoker-proxy-binding that includes the "
-"RetryInterceptor. Below is an example jboss.xml configuration."
-msgstr ""
-"3.2.7+/4.0.2+ 版本包含了 <literal>RetryInterceptor</literal>，它可以加入到代"
-"理客户端拦截器栈里，允许在这样的重启故障后进行透明恢复（transparent "
-"recovery）。为了启用这个机制，你可以设立包含 <literal>RetryInterceptor</"
-"literal> 的 <literal>invoker-proxy-binding</literal>。下面是 <literal>jboss."
-"xml</literal> 配置的一个示例。 "
+#, no-c-format
+msgid "RetryInterceptor can be added to the proxy client side interceptor stack to allow for a transparent recovery from such a restart failure. To enable it for an EJB, setup an invoker-proxy-binding that includes the RetryInterceptor. Below is an example jboss.xml configuration."
+msgstr "literal>RetryInterceptor</literal> 可以加入到代理客户端拦截器栈里，允许在这样的重启故障后进行透明恢复（transparent recovery）。为了启用这个机制，你可以设立包含 <literal>RetryInterceptor</literal> 的 <literal>invoker-proxy-binding</literal>。下面是 <literal>jboss.xml</literal> 配置的一个示例。 "
#. Tag: title
#, no-c-format
@@ -407,18 +362,9 @@
msgstr "为了恢复 HA 代理，RetryInterceptor 将查找 JNDI。这意味着它会在内部创建一个新的 InitialContext 并进行 JNDI 查找。但是，为了使查找成功，你需要正确配置 InitialContext 才能找到命名服务器。RetryInterceptor 将执行下列步骤来决定正确的命名环境属性："
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"It will check its own static retryEnv field. This field can be set by client "
-"code via a call to RetryInterceptor.setRetryEnv(Properties). This approach "
-"to configuration has two downsides: first, it reduces portability by "
-"introducing JBoss-specific calls to the client code; and second, since a "
-"static field is used only a single configuration per VM is possible."
-msgstr ""
-"它将检查自己的静态 retryEnv 字段。这个字段可以通过调用 RetryInterceptor."
-"setRetryEnv(Properties) 的客户端代码来设置。这个方法有两个缺点：首先，它在代"
-"码里引入了 JBoss 专有的调用，降低了可移植性；其次，既然使用了静态字段，那么每"
-"个 JVM 都只能有一个配置。"
+#, no-c-format
+msgid "It will check its own static retryEnv field. This field can be set by client code via a call to RetryInterceptor.setRetryEnv(Properties). This approach to configuration has two downsides: first, it reduces portability by introducing JBoss-specific calls to the client code; and second, since a static field is used only a single configuration per VM is possible."
+msgstr "它将检查自己的静态 retryEnv 字段。这个字段可以通过调用 RetryInterceptor.setRetryEnv(Properties) 的客户端代码来设置。这个方法有两个缺点：首先，它在代码里引入了 JBoss 专有的调用，降低了可移植性；其次，既然使用了静态字段，那么每个 JVM 都只能有一个配置。 "
#. Tag: para
#, no-c-format
@@ -426,18 +372,9 @@
msgstr "如果 retryEnv 字段为空，它将检查任何通过 org.jboss.naming.NamingContextFactory 类绑定到 ThreadLocal 的环境属性。要把这个类作为命名上下文工厂使用，你要在 jndi.properties 里设置属性 java.naming.factory.initial=org.jboss.naming.NamingContextFactory。这个方法的优点是对 org.jboss.naming.NamingContextFactory 的使用仅需要对 jndi.properties 文件进行配置，从而不会影响到你的 Java 代码。缺点是命名属性存储在 ThreadLocal 里，因此只对于原来创建 InitialContext 的线程可见。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"If neither of the above approaches yield a set of naming environment "
-"properties, a default InitialContext is used. If the attempt to contact a "
-"naming server is unsuccessful, by default the InitialContext will attempt to "
-"fall back on multicast discovery to find an HA-JNDI naming server. See <xref "
-"linkend=\"clustering-jndi\" /> for more on multicast discovery of HA-JNDI."
-msgstr ""
-"如果上述两种都没给出一系列命名环境属性，缺省的 InitialContext 将被使用。如果"
-"连接命名服务器没有成功，InitialContext 缺省将通过多点传送发现（multicast "
-"discovery）来寻找 HA-JNDI 命名服务器。关于 HA-JNDI 的多点传送发现的更多信息，"
-"请参考“群集的 JNDI 服务”章节。"
+#, no-c-format
+msgid "If neither of the above approaches yield a set of naming environment properties, a default InitialContext is used. If the attempt to contact a naming server is unsuccessful, by default the InitialContext will attempt to fall back on multicast discovery to find an HA-JNDI naming server. See <xref linkend=\"clustering-jndi\" /> for more on multicast discovery of HA-JNDI."
+msgstr "如果上述两种都没给出一系列命名环境属性，缺省的 InitialContext 将被使用。如果连接命名服务器没有成功，InitialContext 缺省将通过多点传送发现（multicast discovery）来寻找 HA-JNDI 命名服务器。关于 HA-JNDI 的多点传送发现的更多信息，请参考“群集的 JNDI 服务”（<xref linkend=\"clustering-jndi\" />）章节。"
#. Tag: title
#, no-c-format
@@ -450,30 +387,14 @@
msgstr "在很多情况下 RetryInterceptor 都很有用，但缺点是它会持续地在 JNDI 里重新查找 HA 代理直到成功。如果由于某种原因不能成功，这个过程将一直进行，因此触发 RetryInterceptor 的 EJB 调用将永远无法返回。对于多数客户端应用程序来说，这样的情形是无法被接受的。因此，JBoss 没有把 RetryInterceptor 作为其群集 EJB 的客户端连接器栈的一部分。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"In a previous release, a new flavor of retry interceptor was introduced, the "
-"org.jboss.proxy.ejb.SingleRetryInterceptor. This version works like the "
-"RetryInterceptor, but only makes a single attempt to re-lookup the HA proxy "
-"in JNDI. If this attempt fails, the EJB call will fail just as if no retry "
-"interceptor was used. The SingleRetryInterceptor is now part of the default "
-"client interceptor stacks for clustered EJBs."
-msgstr ""
-"在 4.0.4.RC1 版本里引入了新的重试拦截器：org.jboss.proxy.ejb."
-"SingleRetryInterceptor。这个版本和RetryInterceptor 类似，但在 JNDI 里对 HA 代"
-"理的重新查找只进行一次。如果这次失败了，EJB 调用就会失败，就好像没有使用重试"
-"拦截器一样。从 4.0.4.CR2 开始，SingleRetryInterceptor 已经是群集 EJB 的客户端"
-"连接器栈的一部分了。"
+#, no-c-format
+msgid "In a previous release, a new flavor of retry interceptor was introduced, the org.jboss.proxy.ejb.SingleRetryInterceptor. This version works like the RetryInterceptor, but only makes a single attempt to re-lookup the HA proxy in JNDI. If this attempt fails, the EJB call will fail just as if no retry interceptor was used. The SingleRetryInterceptor is now part of the default client interceptor stacks for clustered EJBs."
+msgstr "在以前的版本里引入了新的重试拦截器：org.jboss.proxy.ejb.SingleRetryInterceptor。这个版本和RetryInterceptor 类似，但在 JNDI 里对 HA 代理的重新查找只进行一次。如果这次失败了，EJB 调用就会失败，就好像没有使用重试拦截器一样。从 4.0.4.CR2 开始，SingleRetryInterceptor 已经是群集 EJB 的客户端连接器栈的一部分了。"
#. Tag: para
#, no-c-format
-msgid ""
-"The downside of the SingleRetryInterceptor is that if the retry attempt is "
-"made during a portion of a cluster restart where no servers are available, "
-"the retry will fail and no further attempts will be made."
-msgstr ""
-"SingleRetryInterceptor 的缺点是如果重试是在群集重启的过程中进行，因为此时没有"
-"可用的服务器，这个重试将失败且不会进行再次尝试。"
+msgid "The downside of the SingleRetryInterceptor is that if the retry attempt is made during a portion of a cluster restart where no servers are available, the retry will fail and no further attempts will be made."
+msgstr "SingleRetryInterceptor 的缺点是如果重试是在群集重启的过程中进行，因为此时没有可用的服务器，这个重试将失败且不会进行再次尝试。"
#, fuzzy
#~ msgid ""
@@ -491,3 +412,4 @@
#~ "<literal>true</literal> 时复制这个 bean。如果 bean 还没被更改(或者还不够来"
#~ "请求复制，这取决于你的喜好，你可以返回 <literal>false</literal>，这样复制"
#~ "就不会发生。"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:18:00\n"
-"PO-Revision-Date: 2010-02-10 12:15+1000\n"
+"PO-Revision-Date: 2010-03-17 10:51+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -23,13 +23,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"In a JBoss Enterprise Application Platform cluster, entity bean instance "
-"caches need to be kept in sync across all nodes. If an entity bean provides "
-"remote services, the service methods need to be load balanced as well."
-msgstr ""
-"在 JBoss AS 群集系统里，entity bean 实例需要在所有节点间保持同步。如果某个 "
-"entity bean 提供了远程服务，那么该服务的方法也需要进行负载平衡。 "
+msgid "In a JBoss Enterprise Application Platform cluster, entity bean instance caches need to be kept in sync across all nodes. If an entity bean provides remote services, the service methods need to be load balanced as well."
+msgstr "在 JBoss AS 群集系统里，entity bean 实例需要在所有节点间保持同步。如果某个 entity bean 提供了远程服务，那么该服务的方法也需要进行负载平衡。 "
#. Tag: title
#, no-c-format
@@ -38,15 +33,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"In EJB 3.0, entity beans primarily serve as a persistence data model. They "
-"do not provide remote services. Hence, the entity bean clustering service in "
-"EJB 3.0 primarily deals with distributed caching and replication, instead of "
-"load balancing."
-msgstr ""
-"在 EJB 3.0 里，entity beans 主要以持久化数据模型出现。它们不提供远程服务。因"
-"此，EJB 3.0 里的 entity bean 群集服务主要处理分布式缓存和复制，而不是负载平"
-"衡。 "
+msgid "In EJB 3.0, entity beans primarily serve as a persistence data model. They do not provide remote services. Hence, the entity bean clustering service in EJB 3.0 primarily deals with distributed caching and replication, instead of load balancing."
+msgstr "在 EJB 3.0 里，entity beans 主要以持久化数据模型出现。它们不提供远程服务。因此，EJB 3.0 里的 entity bean 群集服务主要处理分布式缓存和复制，而不是负载平衡。 "
#. Tag: title
#, no-c-format
@@ -55,72 +43,38 @@
#. Tag: para
#, no-c-format
-msgid ""
-"To avoid round trips to the database, you can use a cache for your entities. "
-"JBoss EJB 3.0 entity beans are implemented by Hibernate, which has support "
-"for a second-level cache. The second-level cache provides the following "
-"functionalities:"
-msgstr ""
-"为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 "
-"Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 "
-"JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能： "
+msgid "To avoid round trips to the database, you can use a cache for your entities. JBoss EJB 3.0 entity beans are implemented by Hibernate, which has support for a second-level cache. The second-level cache provides the following functionalities:"
+msgstr "为了避免多次访问数据库，你可以为你的 entities 使用缓存。JBoss EJB 3.0 是用 Hibernate 实现的，它支持两级缓存。用于 JBoss EJB 3.0 实现的 Hibernate 把 JBoss Cache 当作底层缓存实现使用。这个缓存提供了下面的功能： "
#. Tag: para
#, no-c-format
-msgid ""
-"If you persist a cache-enabled entity bean instance to the database via the "
-"entity manager, the entity will be inserted into the cache."
-msgstr ""
-"如果你通过 entity manager 来使应用缓存的 entity bean 的实例持久化，这个 "
-"entity 会被储存到缓存里。 "
+msgid "If you persist a cache-enabled entity bean instance to the database via the entity manager, the entity will be inserted into the cache."
+msgstr "如果你通过 entity manager 来使应用缓存的 entity bean 的实例持久化，这个 entity 会被储存到缓存里。 "
#. Tag: para
#, no-c-format
-msgid ""
-"If you update an entity bean instance, and save the changes to the database "
-"via the entity manager, the entity will be updated in the cache."
-msgstr ""
-"如果你通过 entity manager 更新 entity bean 实例并把更改保存到数据库里，缓存里"
-"的这个 entity 将被更新。 "
+msgid "If you update an entity bean instance, and save the changes to the database via the entity manager, the entity will be updated in the cache."
+msgstr "如果你通过 entity manager 更新 entity bean 实例并把更改保存到数据库里，缓存里的这个 entity 将被更新。 "
#. Tag: para
#, no-c-format
-msgid ""
-"If you remove an entity bean instance from the database via the entity "
-"manager, the entity will be removed from the cache."
-msgstr ""
-"如果你通过 entity manager 把 entity bean 实例从数据库里删除，这个 entity 也将"
-"从缓存里删除。 "
+msgid "If you remove an entity bean instance from the database via the entity manager, the entity will be removed from the cache."
+msgstr "如果你通过 entity manager 把 entity bean 实例从数据库里删除，这个 entity 也将从缓存里删除。 "
#. Tag: para
#, no-c-format
-msgid ""
-"If loading a cached entity from the database via the entity manager, and "
-"that entity does not exist in the database, it will be inserted into the "
-"cache."
-msgstr ""
-"如果你通过 entity manager 从数据库里载入缓存的 entity，而这个这个 entity 并不"
-"在缓存里，这个 entity 会被插入到缓存里。"
+msgid "If loading a cached entity from the database via the entity manager, and that entity does not exist in the database, it will be inserted into the cache."
+msgstr "如果你通过 entity manager 从数据库里载入缓存的 entity，而这个这个 entity 并不在缓存里，这个 entity 会被插入到缓存里。"
#. Tag: para
#, no-c-format
-msgid ""
-"As well as a region for caching entities, the second-level cache also "
-"contains regions for caching collections, queries, and timestamps. The "
-"Hibernate setup used for the JBoss EJB 3.0 implementation uses JBoss Cache "
-"as its underlying second-level cache implementation."
-msgstr ""
-"除了缓存实体的 region，两级缓存也包含缓存集合、查询和时间戳的 region。用于 "
-"JBoss EJB 3.0 实现的 Hibernate 使用 JBoss Cache 作为其底层的二级缓存实现。"
+msgid "As well as a region for caching entities, the second-level cache also contains regions for caching collections, queries, and timestamps. The Hibernate setup used for the JBoss EJB 3.0 implementation uses JBoss Cache as its underlying second-level cache implementation."
+msgstr "除了缓存实体的 region，两级缓存也包含缓存集合、查询和时间戳的 region。用于 JBoss EJB 3.0 实现的 Hibernate 使用 JBoss Cache 作为其底层的二级缓存实现。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"Configuration of a the second-level cache is done via your EJB3 deployment's "
-"<filename>persistence.xml</filename>, like so:"
-msgstr ""
-"配置二级缓存是通过你的 EJB3 部署的 <filename>persistence.xml</filename> 来完"
-"成的。"
+#, no-c-format
+msgid "Configuration of a the second-level cache is done via your EJB3 deployment's <filename>persistence.xml</filename>, like so:"
+msgstr "配置二级缓存是通过你的 EJB3 部署的 <filename>persistence.xml</filename> 来完成的，例如："
#. Tag: term
#, no-c-format
@@ -149,23 +103,13 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Defines the <literal>RegionFactory</literal> implementation that dictates "
-"region-specific caching behavior. Hibernate ships with 2 types of JBoss "
-"Cache-based second-level caches: shared and multiplexed."
-msgstr ""
-"定义指明 Region 专有的缓存行为的 <literal>RegionFactory</literal> 实现。"
-"Hibernate 带有两种类型的基于 JBoss Cache 的二级缓存：共享的（shared）和多路复"
-"用的（multiplexed）。"
+msgid "Defines the <literal>RegionFactory</literal> implementation that dictates region-specific caching behavior. Hibernate ships with 2 types of JBoss Cache-based second-level caches: shared and multiplexed."
+msgstr "定义指明 Region 专有的缓存行为的 <literal>RegionFactory</literal> 实现。Hibernate 带有两种类型的基于 JBoss Cache 的二级缓存：共享的（shared）和多路复用的（multiplexed）。"
#. Tag: para
#, no-c-format
-msgid ""
-"A shared region factory uses the same Cache for all cache regions - much "
-"like the legacy CacheProvider implementation in older Hibernate versions."
-msgstr ""
-"共享的 Region 工厂对于所有的缓存 Region 使用相同的缓存 - 这和传统的 "
-"CacheProvider 实现很像。"
+msgid "A shared region factory uses the same Cache for all cache regions - much like the legacy CacheProvider implementation in older Hibernate versions."
+msgstr "共享的 Region 工厂对于所有的缓存 Region 使用相同的缓存 - 这和传统的 CacheProvider 实现很像。"
#. Tag: para
#, no-c-format
@@ -179,12 +123,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses a single JBoss Cache configuration, from a newly instantiated "
-"CacheManager, for all cache regions."
-msgstr ""
-"对于所有的缓存 Region，它使用新初始化的 CacheManager 里的一个简单的 JBoss 缓"
-"存配置。"
+msgid "Uses a single JBoss Cache configuration, from a newly instantiated CacheManager, for all cache regions."
+msgstr "对于所有的缓存 Region，它使用新初始化的 CacheManager 里的一个简单的 JBoss 缓存配置。"
#. Tag: title
#, no-c-format
@@ -218,9 +158,7 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The classpath or filesystem resource containing the JBoss Cache "
-"configuration settings."
+msgid "The classpath or filesystem resource containing the JBoss Cache configuration settings."
msgstr "包含 JBoss Cache 配置设定的文件系统资源或 classpath。"
#. Tag: entry
@@ -235,9 +173,7 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The classpath or filesystem resource containing the JGroups protocol stack "
-"configurations."
+msgid "The classpath or filesystem resource containing the JGroups protocol stack configurations."
msgstr "包含 JGroups 协议栈配置的 classpath 或文件系统。"
#. Tag: term
@@ -247,12 +183,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses a single JBoss Cache configuration, from an existing CacheManager bound "
-"to JNDI, for all cache regions."
-msgstr ""
-"对于所有的缓存 region，使用绑定到 JNDI 的现有 CacheManager 的单一 JBoss "
-"Cache 配置。"
+msgid "Uses a single JBoss Cache configuration, from an existing CacheManager bound to JNDI, for all cache regions."
+msgstr "对于所有的缓存 region，使用绑定到 JNDI 的现有 CacheManager 的单一 JBoss Cache 配置。"
#. Tag: title
#, no-c-format
@@ -266,18 +198,13 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"JNDI name to which the shared <literal>Cache</literal> instance is bound."
+msgid "JNDI name to which the shared <literal>Cache</literal> instance is bound."
msgstr "共享的 <literal>Cache</literal> 实现绑定的 JNDI 名称。"
#. Tag: para
#, no-c-format
-msgid ""
-"A multiplexed region factory uses separate Cache instances, using optimized "
-"configurations for each cache region."
-msgstr ""
-"多路复用的 region 工厂使用独立的 Cache 实例，它对每个缓存 region 使用优化的配"
-"置。"
+msgid "A multiplexed region factory uses separate Cache instances, using optimized configurations for each cache region."
+msgstr "多路复用的 region 工厂使用独立的 Cache 实例，它对每个缓存 region 使用优化的配置。"
#. Tag: title
#, no-c-format
@@ -296,14 +223,8 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the entity cache region. Alternative "
-"configurations: mvcc-entity, pessimistic-entity, mvcc-entity-repeatable, "
-"optimistic-entity-repeatable, pessimistic-entity-repeatable"
-msgstr ""
-"用于实体缓存 region 的 JBoss Cache 配置。其他的配置：mvcc-entity、"
-"pessimistic-entity、mvcc-entity-repeatable、optimistic-entity-repeatable、"
-"pessimistic-entity-repeatable。"
+msgid "The JBoss Cache configuration used for the entity cache region. Alternative configurations: mvcc-entity, pessimistic-entity, mvcc-entity-repeatable, optimistic-entity-repeatable, pessimistic-entity-repeatable"
+msgstr "用于实体缓存 region 的 JBoss Cache 配置。其他的配置：mvcc-entity、pessimistic-entity、mvcc-entity-repeatable、optimistic-entity-repeatable、pessimistic-entity-repeatable。"
#. Tag: entry
#, no-c-format
@@ -312,13 +233,8 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the collection cache region. The "
-"collection cache region typically uses the same configuration as the entity "
-"cache region."
-msgstr ""
-"用于集合缓存 Region 的 JBoss Cache 配置。集合缓存 Region 通常使用和实体缓存 "
-"Region 相同的配置。"
+msgid "The JBoss Cache configuration used for the collection cache region. The collection cache region typically uses the same configuration as the entity cache region."
+msgstr "用于集合缓存 Region 的 JBoss Cache 配置。集合缓存 Region 通常使用和实体缓存 Region 相同的配置。"
#. Tag: entry
#, no-c-format
@@ -332,13 +248,8 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the query cache region. By default, "
-"cached query results are not replicated. Alternative configurations: "
-"replicated-query"
-msgstr ""
-"用于查询缓存 region 的 JBoss Cache 配置。在缺省情况下，缓存的查询结果不会被复"
-"制。替代的配置有：replicated-query。"
+msgid "The JBoss Cache configuration used for the query cache region. By default, cached query results are not replicated. Alternative configurations: replicated-query"
+msgstr "用于查询缓存 region 的 JBoss Cache 配置。在缺省情况下，缓存的查询结果不会被复制。替代的配置有：replicated-query。"
#. Tag: entry
#, no-c-format
@@ -352,15 +263,8 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"The JBoss Cache configuration used for the timestamp cache region. If query "
-"caching is used, the corresponding timestamp cache must be replicating, even "
-"if the query cache is non-replicating. The timestamp cache region must never "
-"share the same cache as the query cache."
-msgstr ""
-"用于时间戳缓存 Region 的 JBoss Cache 配置。如果使用了查询缓存，对应的时间戳缓"
-"存必须进行复制，即使查询缓存没有进行复制。时间戳缓存 region 不能共享和查询缓"
-"存相同的缓存。"
+msgid "The JBoss Cache configuration used for the timestamp cache region. If query caching is used, the corresponding timestamp cache must be replicating, even if the query cache is non-replicating. The timestamp cache region must never share the same cache as the query cache."
+msgstr "用于时间戳缓存 Region 的 JBoss Cache 配置。如果使用了查询缓存，对应的时间戳缓存必须进行复制，即使查询缓存没有进行复制。时间戳缓存 region 不能共享和查询缓存相同的缓存。"
#. Tag: term
#, no-c-format
@@ -369,12 +273,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses separate JBoss Cache configurations, from a newly instantiated "
-"CacheManager, per cache region."
-msgstr ""
-"在刚初始化的 CacheManager 里，根据每个缓存 Region 使用独立的 JBoss Cache 配"
-"置。"
+msgid "Uses separate JBoss Cache configurations, from a newly instantiated CacheManager, per cache region."
+msgstr "在刚初始化的 CacheManager 里，根据每个缓存 Region 使用独立的 JBoss Cache 配置。"
#. Tag: title
#, no-c-format
@@ -398,13 +298,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Uses separate JBoss Cache configurations, from a JNDI-bound CacheManager, "
-"see <xref linkend=\"clustering-blocks-jbc-cachemanager\" />, per cache "
-"region."
-msgstr ""
-"根据每个 Cache Region 使用 JNDI-bound CacheManager 里独立的 JBoss Cache 配"
-"置，请参考 <xref linkend=\"clustering-blocks-jbc-cachemanager\" />。"
+msgid "Uses separate JBoss Cache configurations, from a JNDI-bound CacheManager, see <xref linkend=\"clustering-blocks-jbc-cachemanager\" />, per cache region."
+msgstr "根据每个 Cache Region 使用 JNDI-bound CacheManager 里独立的 JBoss Cache 配置，请参考 <xref linkend=\"clustering-blocks-jbc-cachemanager\" />。"
#. Tag: title
#, no-c-format
@@ -418,19 +313,13 @@
#. Tag: entry
#, no-c-format
-msgid ""
-"JNDI name to which the <literal>CacheManager</literal> instance is bound."
+msgid "JNDI name to which the <literal>CacheManager</literal> instance is bound."
msgstr "<literal>CacheManager</literal> 实例绑定的 JNDI 名称。"
#. Tag: para
#, no-c-format
-msgid ""
-"Now, we have JBoss Cache configured to support distributed caching of EJB "
-"3.0 entity beans. We still have to configure individual entity beans to use "
-"the cache service."
-msgstr ""
-"现在，我们配置了 JBoss Cache 来支持 EJB 3.0 entity beans 的分布式缓存。我们仍"
-"不得不配置单个的 entity bean 来使用这个缓存服务。"
+msgid "Now, we have JBoss Cache configured to support distributed caching of EJB 3.0 entity beans. We still have to configure individual entity beans to use the cache service."
+msgstr "现在，我们配置了 JBoss Cache 来支持 EJB 3.0 entity beans 的分布式缓存。我们仍不得不配置单个的 entity bean 来使用这个缓存服务。"
#. Tag: title
#, no-c-format
@@ -439,53 +328,18 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Next we need to configure which entities to cache. The default is to not "
-"cache anything, even with the settings shown above. We use the <literal>@org."
-"hibernate.annotations.Cache</literal> annotation to tag entity beans that "
-"needs to be cached."
-msgstr ""
-"下一步我们需要配置哪些实体被缓存。就像上面所展示的样，缺省是什么都不缓存。我"
-"们使用 <literal>@org.hibernate.annotations.Cache</literal> 注解来标记需要缓存"
-"的 entity bean。 "
+msgid "Next we need to configure which entities to cache. The default is to not cache anything, even with the settings shown above. We use the <literal>@org.hibernate.annotations.Cache</literal> annotation to tag entity beans that needs to be cached."
+msgstr "下一步我们需要配置哪些实体被缓存。就像上面所展示的样，缺省是什么都不缓存。我们使用 <literal>@org.hibernate.annotations.Cache</literal> 注解来标记需要缓存的 entity bean。 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"A very simplified rule of thumb is that you will typically want to do "
-"caching for objects that rarely change, and which are frequently read. You "
-"can fine tune the cache for each entity bean in the appropriate JBoss Cache "
-"configuration file, e.g. <filename>jboss-cache-manager-jboss-beans.xml</"
-"filename>. For instance, you can specify the size of the cache. If there are "
-"too many objects in the cache, the cache can evict the oldest or least used "
-"objects, depending on configuration, to make room for new objects. Assuming "
-"the region_prefix specified in <literal>persistence.xml</literal> was "
-"<literal>myprefix</literal>, the default name of the cache region for the "
-"<literal>com.mycompany.entities.Account</literal> entity bean would be "
-"<literal>/myprefix/com/mycompany/entities/Account</literal>."
-msgstr ""
-"一个简单的原则就是，你应该对很少变动和频繁使用的对象进行缓存.你可以在 "
-"<literal>ejb3-entity-cache-service.xml</literal> 配置文件里为每个 entity "
-"bean 微调缓存设置。例如，你可以指定缓存的大小。如果缓存里的对象太多，缓存有可"
-"能挤掉最老的对象（或者最少用的对象，依你的配置而定）来给新对象留出空间。假设 "
-"<literal>persistence.xml</literal> 里指定的 region_prefix 是 myprefix，"
-"entity bean 的<literal>com.mycompany.entities.Account</literal> 缺省的缓存 "
-"region 是 <literal>/myprefix/com/mycompany/entities/Account</literal>。 "
+#, no-c-format
+msgid "A very simplified rule of thumb is that you will typically want to do caching for objects that rarely change, and which are frequently read. You can fine tune the cache for each entity bean in the appropriate JBoss Cache configuration file, e.g. <filename>jboss-cache-manager-jboss-beans.xml</filename>. For instance, you can specify the size of the cache. If there are too many objects in the cache, the cache can evict the oldest or least used objects, depending on configuration, to make room for new objects. Assuming the region_prefix specified in <literal>persistence.xml</literal> was <literal>myprefix</literal>, the default name of the cache region for the <literal>com.mycompany.entities.Account</literal> entity bean would be <literal>/myprefix/com/mycompany/entities/Account</literal>."
+msgstr "一个简单的原则就是，你应该对很少变动和频繁使用的对象进行缓存.你可以在 <filename>jboss-cache-manager-jboss-beans.xml</filename> 配置文件里为每个 entity bean 微调缓存设置。例如，你可以指定缓存的大小。如果缓存里的对象太多，缓存有可能挤掉最老的对象（或者最少用的对象，依你的配置而定）来给新对象留出空间。假设 <literal>persistence.xml</literal> 里指定的 region_prefix 是 myprefix，entity bean 的<literal>com.mycompany.entities.Account</literal> 缺省的缓存 region 是 <literal>/myprefix/com/mycompany/entities/Account</literal>。 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"If you do not specify a cache region for an entity bean class, all instances "
-"of this class will be cached using the <literal>defaultEvictionRegionConfig</"
-"literal> as defined above. The @Cache annotation exposes an optional "
-"attribute \"region\" that lets you specify the cache region where an entity "
-"is to be stored, rather than having it be automatically be created from the "
-"fully-qualified class name of the entity class."
-msgstr ""
-"如果你没有为 entity bean 类指定缓存区（cache region），这个类的所有实例将象上"
-"面定义的一样缓存在 <literal>defaultEvictionRegionConfig</literal> 区里。"
-"@Cache 注解开放一个可选的属性“region”，它让你指定实体所存储的缓存区，而不是根"
-"据实体类的全限定名自动创建。"
+#, no-c-format
+msgid "If you do not specify a cache region for an entity bean class, all instances of this class will be cached using the <literal>defaultEvictionRegionConfig</literal> as defined above. The @Cache annotation exposes an optional attribute \"region\" that lets you specify the cache region where an entity is to be stored, rather than having it be automatically be created from the fully-qualified class name of the entity class."
+msgstr "如果你没有为 entity bean 类指定缓存区（cache region），这个类的所有实例将象上面定义的一样缓存在 <literal>defaultEvictionRegionConfig</literal> 区里。@Cache 注解开放一个可选的属性 \"region\" ，它让你指定实体所存储的缓存区，而不是根据实体类的全限定名自动创建。"
#. Tag: para
#, no-c-format
@@ -499,68 +353,33 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The EJB3 Query API also provides means for you to save the results (i.e., "
-"collections of primary keys of entity beans, or collections of scalar "
-"values) of specified queries in the second-level cache. Here we show a "
-"simple example of annotating a bean with a named query, also providing the "
-"Hibernate-specific hints that tells Hibernate to cache the query."
-msgstr ""
-"EJB3 Query API 也为你提供了把查询结果（如 entity bean 的主键集合或标量结果的"
-"集合）保存在二级缓存里的方法。在这里我们演示了一个简单的例子，它注解了带有命"
-"名查询的 bean，且提供 Hibernate 专有的指令来让 Hibernate 缓存这个查询。 "
+msgid "The EJB3 Query API also provides means for you to save the results (i.e., collections of primary keys of entity beans, or collections of scalar values) of specified queries in the second-level cache. Here we show a simple example of annotating a bean with a named query, also providing the Hibernate-specific hints that tells Hibernate to cache the query."
+msgstr "EJB3 Query API 也为你提供了把查询结果（如 entity bean 的主键集合或标量结果的集合）保存在二级缓存里的方法。在这里我们演示了一个简单的例子，它注解了带有命名查询的 bean，且提供 Hibernate 专有的指令来让 Hibernate 缓存这个查询。 "
#. Tag: para
#, no-c-format
-msgid ""
-"First, in persistence.xml you need to tell Hibernate to enable query caching:"
+msgid "First, in persistence.xml you need to tell Hibernate to enable query caching:"
msgstr "首先，在 persistence.xml 里，你需要告诉 Hibernate 启用查询缓存："
#. Tag: para
#, no-c-format
-msgid ""
-"Next, you create a named query associated with an entity, and tell Hibernate "
-"you want to cache the results of that query:"
-msgstr ""
-"然后，你创建和实体相关的命名查询，并告诉 Hibernate 你要缓存该查询的结果。"
+msgid "Next, you create a named query associated with an entity, and tell Hibernate you want to cache the results of that query:"
+msgstr "然后，你创建和实体相关的命名查询，并告诉 Hibernate 你要缓存该查询的结果。"
#. Tag: para
#, no-c-format
-msgid ""
-"The @NamedQueries, @NamedQuery and @QueryHint annotations are all in the "
-"javax.persistence package. See the Hibernate and EJB3 documentation for more "
-"on how to use EJB3 queries and on how to instruct EJB3 to cache queries."
-msgstr ""
-"@NamedQueries, @NamedQuery and @QueryHint 注解都在 javax.persistence 包里。关"
-"于如何使用 EJB3 查询以及缓存查询结果的更多信息，请参考 Hibernate 和 EJB3 的文"
-"档。 "
+msgid "The @NamedQueries, @NamedQuery and @QueryHint annotations are all in the javax.persistence package. See the Hibernate and EJB3 documentation for more on how to use EJB3 queries and on how to instruct EJB3 to cache queries."
+msgstr "@NamedQueries, @NamedQuery and @QueryHint 注解都在 javax.persistence 包里。关于如何使用 EJB3 查询以及缓存查询结果的更多信息，请参考 Hibernate 和 EJB3 的文档。 "
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"By default, Hibernate stores query results in JBoss Cache in a region named "
-"<region_prefix>/org/hibernate/cache/StandardQueryCache. Based on this, "
-"you can set up separate eviction handling for your query results. So, if the "
-"region prefix were set to myprefix in <filename>persistence.xml</filename>, "
-"you could, for example, create this sort of eviction handling:"
-msgstr ""
-"在缺省情况下，Hibernate 把查询结果存储在 JBoss Cache 的名为 {region_prefix}/"
-"org/hibernate/cache/StandardQueryCache 区里。基于此点，你可以为查询结果设立单"
-"独的逐出处理过程。所以，如果在 <filename>persistence.xml</filename> 里把区前"
-"缀设置为 myprefix，你可以创建这样的逐出处理过程："
+#, no-c-format
+msgid "By default, Hibernate stores query results in JBoss Cache in a region named <region_prefix>/org/hibernate/cache/StandardQueryCache. Based on this, you can set up separate eviction handling for your query results. So, if the region prefix were set to myprefix in <filename>persistence.xml</filename>, you could, for example, create this sort of eviction handling:"
+msgstr "在缺省情况下，Hibernate 把查询结果存储在 JBoss Cache 的名为 <region_prefix>/org/hibernate/cache/StandardQueryCache 区里。基于此点，你可以为查询结果设立单独的逐出处理过程。所以，如果在 <filename>persistence.xml</filename> 里把区前缀设置为 myprefix，你可以创建这样的逐出处理过程："
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The @NamedQuery.hints attribute shown above takes an array of vendor-"
-"specific @QueryHints as a value. Hibernate accepts the \"org.hibernate."
-"cacheRegion\" query hint, where the value is the name of a cache region to "
-"use instead of the default /org/hibernate/cache/StandardQueryCache. For "
-"example:"
-msgstr ""
-"上面的 @NamedQuery.hints 采用一个供应商专有的 @QueryHints 队列。Hibernate 接"
-"受“org.hibernate.cacheRegion”，它的值是所使用的缓存区的名称，而不是缺省的 /"
-"org/hibernate/cache/StandardQueryCache。例如："
+#, no-c-format
+msgid "The @NamedQuery.hints attribute shown above takes an array of vendor-specific @QueryHints as a value. Hibernate accepts the \"org.hibernate.cacheRegion\" query hint, where the value is the name of a cache region to use instead of the default /org/hibernate/cache/StandardQueryCache. For example:"
+msgstr "上面的 @NamedQuery.hints 采用一个供应商专有的 @QueryHints 队列。Hibernate 接受 \"org.hibernate.cacheRegion\"，它的值是所使用的缓存区的名称，而不是缺省的 /org/hibernate/cache/StandardQueryCache。例如："
#. Tag: para
#, no-c-format
@@ -573,91 +392,37 @@
msgstr "EJB 2.x 里的 Entity Bean"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"First of all, it is worth noting that clustering 2.x entity beans is a bad "
-"thing to do. Its exposes elements that generally are too fine grained for "
-"use as remote objects to clustered remote objects and introduces data "
-"synchronization problems that are non-trivial. Do NOT use EJB 2.x entity "
-"bean clustering unless you fit into the special case situation of read-only, "
-"or one read-write node with read-only nodes synchronized with the cache "
-"invalidation services."
-msgstr ""
-"首先，值得注意的是使用群集 2.x 的 entity bean 并非好主意。它向群集的远程对象"
-"开放（exposes）通常过于细颗粒度的元素（elements），导致了严重的数据同步问题。"
-"除非你遇到特殊的情况，如只读或者只写的节点和使用缓存失效服务（cache "
-"invalidation services）的只读节点同步，否则不要使用 EJB 2.x entity bean 的群"
-"集。"
+#, no-c-format
+msgid "First of all, it is worth noting that clustering 2.x entity beans is a bad thing to do. Its exposes elements that generally are too fine grained for use as remote objects to clustered remote objects and introduces data synchronization problems that are non-trivial. Do NOT use EJB 2.x entity bean clustering unless you fit into the special case situation of read-only, or one read-write node with read-only nodes synchronized with the cache invalidation services."
+msgstr "首先，值得注意的是使用群集 2.x 的 entity bean 并非好主意。它向群集的远程对象开放（exposes）通常过于细颗粒度的元素（elements），导致了严重的数据同步问题。除非你遇到特殊的情况，如只读或者只写的节点和使用缓存失效服务（cache invalidation services）的只读节点同步，否则不要使用 EJB 2.x entity bean 的群集。 "
#. Tag: para
#, no-c-format
-msgid ""
-"To use a clustered entity bean, the application does not need to do anything "
-"special, except for looking up EJB 2.x remote bean references from the "
-"clustered HA-JNDI."
-msgstr ""
-"为了使用群集的 entity bean，应用程序不需要做任何特殊的事情，除了从群集的 HA-"
-"JNDI 里查找 EJB 2.x bean 的远程引用。"
+msgid "To use a clustered entity bean, the application does not need to do anything special, except for looking up EJB 2.x remote bean references from the clustered HA-JNDI."
+msgstr "为了使用群集的 entity bean，应用程序不需要做任何特殊的事情，除了从群集的 HA-JNDI 里查找 EJB 2.x bean 的远程引用。"
#. Tag: para
#, no-c-format
-msgid ""
-"To cluster EJB 2.x entity beans, you need to add the <literal><"
-"clustered></literal> element to the application's <literal>jboss.xml</"
-"literal> descriptor file. Below is a typical <literal>jboss.xml</literal> "
-"file."
-msgstr ""
-"要群集 EJB 2.x entity beans，你需要把 <literal><clustered></literal> 元"
-"素加入到应用程序的 <literal>jboss.xml</literal> 描述符文件里。下面是一个典型"
-"的 <literal>jboss.xml</literal> 文件。"
+msgid "To cluster EJB 2.x entity beans, you need to add the <literal><clustered></literal> element to the application's <literal>jboss.xml</literal> descriptor file. Below is a typical <literal>jboss.xml</literal> file."
+msgstr "要群集 EJB 2.x entity beans，你需要把 <literal><clustered></literal> 元素加入到应用程序的 <literal>jboss.xml</literal> 描述符文件里。下面是一个典型的 <literal>jboss.xml</literal> 文件。"
#. Tag: para
#, no-c-format
-msgid ""
-"The EJB 2.x entity beans are clustered for load balanced remote invocations. "
-"All the bean instances are synchronized to have the same contents on all "
-"nodes."
-msgstr ""
-"为了平衡远程调用的负载，我们群集 EJB 2.x entity beans。所有的 bean 实例都实现"
-"同步，具有所有节点上的相同内容。"
+msgid "The EJB 2.x entity beans are clustered for load balanced remote invocations. All the bean instances are synchronized to have the same contents on all nodes."
+msgstr "为了平衡远程调用的负载，我们群集 EJB 2.x entity beans。所有的 bean 实例都实现同步，具有所有节点上的相同内容。"
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"However, clustered EJB 2.x Entity Beans do not have a distributed locking "
-"mechanism or a distributed cache. They can only be synchronized by using row-"
-"level locking at the database level (see <literal><row-lock></literal> "
-"in the CMP specification) or by setting the Transaction Isolation Level of "
-"your JDBC driver to be <literal>TRANSACTION_SERIALIZABLE</literal>. Because "
-"there is no supported distributed locking mechanism or distributed cache "
-"Entity Beans use Commit Option \"B\" by default (see <literal>standardjboss."
-"xml</literal> and the container configurations Clustered CMP 2.x EntityBean, "
-"Clustered CMP EntityBean, or Clustered BMP EntityBean). It is not "
-"recommended that you use Commit Option \"A\" unless your Entity Bean is read-"
-"only."
-msgstr ""
-"然而，群集的 EJB 2.x Entity Beans 没有分布式的锁定机制或是缓存。它们只能用数"
-"据库层面的行级锁定（请参考 CMP 规范的<literal><row-lock></literal>）或"
-"是把 JDBC 驱动的事务隔离（Transaction Isolation）级别设为 "
-"<literal>TRANSACTION_SERIALIZABLE</literal> 来实现同步。因为缺乏分布式的锁定"
-"机制或是缓存支持，Entity Beans 缺省使用提交选项 \"B\"（请参考 "
-"<literal>standardjboss.xml</literal> 和 the container configurations "
-"Clustered CMP 2.x EntityBean，Clustered CMP EntityBean，或 Clustered BMP "
-"EntityBean）。我们不推荐你使用提交选项 \"A\"，除非你的 Entity Bean 是只读的。"
-"（有些设计模式允许你把提交选项\"A\" 用于 read-mostly beans。你也可以看看 "
-"Seppuku 模式：<ulink url=\"http://dima.dhs.org/misc/readOnlyUpdates.html\"></"
-"ulink>。JBoss 有可能把这个模式集成到以后的版本里。） "
+#, no-c-format
+msgid "However, clustered EJB 2.x Entity Beans do not have a distributed locking mechanism or a distributed cache. They can only be synchronized by using row-level locking at the database level (see <literal><row-lock></literal> in the CMP specification) or by setting the Transaction Isolation Level of your JDBC driver to be <literal>TRANSACTION_SERIALIZABLE</literal>. Because there is no supported distributed locking mechanism or distributed cache Entity Beans use Commit Option \"B\" by default (see <literal>standardjboss.xml</literal> and the container configurations Clustered CMP 2.x EntityBean, Clustered CMP EntityBean, or Clustered BMP EntityBean). It is not recommended that you use Commit Option \"A\" unless your Entity Bean is read-only."
+msgstr "然而，群集的 EJB 2.x Entity Beans 没有分布式的锁定机制或是缓存。它们只能用数据库层面的行级锁定（请参考 CMP 规范的<literal><row-lock></literal>）或是把 JDBC 驱动的事务隔离（Transaction Isolation）级别设为 <literal>TRANSACTION_SERIALIZABLE</literal> 来实现同步。因为缺乏分布式的锁定机制或是缓存支持，Entity Beans 缺省使用提交选项 \"B\"（请参考 <literal>standardjboss.xml</literal> 和容器配置的群集 CMP 2.x EntityBean，Clustered CMP EntityBean，或 Clustered BMP EntityBean）。我们不推荐你使用提交选项 \"A\"，除非你的 Entity Bean 是只读的。"
#. Tag: para
#, no-c-format
-msgid ""
-"If you are using Bean Managed Persistence (BMP), you are going to have to "
-"implement synchronization on your own."
-msgstr ""
+msgid "If you are using Bean Managed Persistence (BMP), you are going to have to implement synchronization on your own."
+msgstr "如果你在使用 Bean Managed Persistence (BMP)，你得自己部署同步机制。"
#~ msgid "e.g."
#~ msgstr "例如"
-
#~ msgid ""
#~ "If you are using Bean Managed Persistence (BMP), you are going to have to "
#~ "implement synchronization on your own. The MVCSoft CMP 2.0 persistence "
@@ -669,3 +434,4 @@
#~ "制。MVCSoft CMP 2.0 持久化引擎（persistence engine）(请参考 <ulink url="
#~ "\"http://www.jboss.org/jbossgroup/partners.jsp\"></ulink>）提供可以在 "
#~ "JBoss 群集里使用的各种优化锁定策略。 "
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Messaging.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:18:00\n"
-"PO-Revision-Date: 2010-03-03 11:13+1000\n"
+"PO-Revision-Date: 2010-03-17 10:55+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -23,20 +23,13 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The most current information about using JBoss Messaging is always available "
-"from the relevant <citetitle>JBoss Messaging User Guide</citetitle> at "
-"<ulink url=\"http://www.redhat.com/docs/en-US/"
-"JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/docs/en-US/"
-"JBoss_Enterprise_Application_Platform/</ulink>."
-msgstr ""
+msgid "The most current information about using JBoss Messaging is always available from the relevant <citetitle>JBoss Messaging User Guide</citetitle> at <ulink url=\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+msgstr "使用 JBoss Messaging 的最新信息总是位于 <ulink url=\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> 上的<citetitle>《JBoss Messaging 用户指南》</citetitle>里。"
#~ msgid "about"
#~ msgstr "关于"
-
#~ msgid "JMS"
#~ msgstr "JMS"
-
#~ msgid ""
#~ "JBoss Messaging is the new enterprise messaging system from JBoss. It is "
#~ "a complete rewrite of JBossMQ, the legacy JBoss JMS provider. It is the "
@@ -46,30 +39,23 @@
#~ msgstr ""
#~ "JBoss Messaging 是 JBoss 的新的企业级消息系统。它完全重写了旧的 JMS 提供"
#~ "者 JBossMQ。它是企业级应用程序平台 5 的缺省 JMS 提供者。"
-
#~ msgid ""
#~ "JBoss Messaging is a high Performance JMS 1.1 compliant implementation "
#~ "integrated with JBoss Transactions. It also offers:"
#~ msgstr ""
#~ "JBoss Messaging 是一个高性能的兼容 JMS 1.1 的集成 JBoss Transactions 实"
#~ "现。它也提供："
-
#~ msgid "Clustered Queues and Topics by Default"
#~ msgstr "群集队列和缺省主题"
-
#~ msgid "Intelligent Message Redistributions"
#~ msgstr "只能消息分发"
-
#~ msgid "Transparent Failover"
#~ msgstr "透明的失效切换"
-
#~ msgid "In memory message Replication"
#~ msgstr "In memory 消息复制"
-
#~ msgid ""
#~ "JBoss Messaging is an integral part of Red Hat's strategy for messaging."
#~ msgstr "JBoss Messaging 是红帽消息系统不可或缺的一部分。"
-
#~ msgid ""
#~ "JBoss Messaging provides an open source and standards-based messaging "
#~ "platform that brings enterprise-class messaging to the mass market. It "
@@ -82,7 +68,6 @@
#~ "级的消息机制。它也实现了高性能、稳定的消息核心部件以支持规模最大、利用率最"
#~ "高的 SOA、企业服务总线（Enterprise Service Buses，ESB）和满足简单到复杂网"
#~ "络的集成需要。"
-
#~ msgid ""
#~ "It allows you to smoothly distribute your application load across your "
#~ "cluster, intelligently balancing and utilizing each nodes CPU cycles, "
@@ -91,7 +76,6 @@
#~ msgstr ""
#~ "它允许你把应用程序负载流畅地分布在群集里，智能地平衡和利用每个 CPU 周期，"
#~ "且不会出现单点故障。这提供了一个具有高可扩充性和性能的群集实现。"
-
#~ msgid ""
#~ "JBoss Messaging includes a JMS front-end to deliver messaging in a "
#~ "standards-based format as well as being designed to be able to support "
@@ -99,10 +83,8 @@
#~ msgstr ""
#~ "JBoss Messaging 包括了一个 JMS 前端来以标准格式递送消息，将来它也能够支持"
#~ "其他消息协议。"
-
#~ msgid "Configuring JBoss Messaging"
#~ msgstr "配置 JBoss Messaging"
-
#~ msgid ""
#~ "The JBoss Messaging service configuration is spread among several "
#~ "configuration files. Depending on the functionality provided by the "
@@ -120,17 +102,14 @@
#~ "service.xml, destinations-service.xml 和 xxx-persistence-service.xml</"
#~ "filename> 里（这里的 <literal>xxx</literal> 是数据库的名称）。 hsqldb 数据"
#~ "库的缺省值是 <filename>hsqldb-persistence-service.xml</filename>。"
-
#~ msgid "Configuring the SecurityStore"
#~ msgstr "配置 SecurityStore"
-
#~ msgid ""
#~ "SecurityStore is a pluggable object, and it has a default implementation "
#~ "in <filename>messaging-service.xml</filename>:"
#~ msgstr ""
#~ "SecurityStore 是一个可插拔的对象，它在 <filename>messaging-service.xml</"
#~ "filename> 里有一个缺省的实现："
-
#~ msgid ""
#~ "This implementation points the ServerPeer to <code>jboss.messaging:"
#~ "service=SecurityStore</code>, which is defined in the <filename>messaging-"
@@ -139,20 +118,16 @@
#~ "这个实现把 ServerPeer 指向 <code>jboss.messaging:service=SecurityStore</"
#~ "code>，这是在 <filename>messaging-jboss-beans.xml</filename> 文件李定义"
#~ "的。"
-
#~ msgid "SecurityStore Attributes"
#~ msgstr "SecurityStore 属性"
-
#~ msgid ""
#~ "The following are SecurityStore attributes from the <filename>messaging-"
#~ "jboss-beans.xml</filename> file above."
#~ msgstr ""
#~ "下面是 <filename>messaging-jboss-beans.xml</filename> 文件里的 "
#~ "SecurityStore 属性："
-
#~ msgid "DefaultSecurityConfig"
#~ msgstr "DefaultSecurityConfig"
-
#~ msgid ""
#~ "Default security configuration is used when the security configuration "
#~ "for a specific queue or topic has not been overridden in the "
@@ -161,7 +136,6 @@
#~ msgstr ""
#~ "当没有在目的地的部署描述符里覆盖特殊队列或主题的安全配置时，缺省的安全配置"
#~ "将被使用。它和在 JBossMQ 里一样具有相同的语法和语义。"
-
#~ msgid ""
#~ "The DefaultSecurityConfig attribute element should contain one <"
#~ "security> element. The <security> element can contain multiple "
@@ -171,7 +145,6 @@
#~ "DefaultSecurityConfig 属性元素应该包含一个 <security> 元素。<"
#~ "security> 元素可以包含多个 <role> 元素。每个 <role> 元素定"
#~ "义了对特定角色的缺省访问。"
-
#~ msgid ""
#~ "If the read attribute is true then that role will be able to read (create "
#~ "consumers, receive messaages or browse) destinations by default. If the "
@@ -184,26 +157,20 @@
#~ "消息）。如果 write 属性为 true，则该角色缺省可以写入目的地（创建生产者或发"
#~ "送消息）。如果 create 属性为 true，那么该角色缺省可以在主题上创建可持久的"
#~ "订阅（durable subscription）。"
-
#~ msgid "SecurityDomain"
#~ msgstr "SecurityDomain"
-
#~ msgid "The JAAS security domain to be used by this server peer."
#~ msgstr "这个服务器端使用的 JAAS 安全域。"
-
#~ msgid "SuckerPassword"
#~ msgstr "SuckerPassword"
-
#~ msgid ""
#~ "This defines how the SecurityStore will authenticate the sucker user "
#~ "(<literal>JBM.SUCKER</literal>)."
#~ msgstr ""
#~ "这定义了 SecurityStore 如何验证 sucker 用户（<literal>JBM.SUCKER</"
#~ "literal>）。"
-
#~ msgid "Configuring the ServerPeer"
#~ msgstr "配置 ServerPeer"
-
#~ msgid ""
#~ "The <classname>ServerPeer</classname> is the heart of the JBoss Messaging "
#~ "JMS. All JBoss Messaging services are rooted at the server peer and the "
@@ -216,16 +183,12 @@
#~ "JBoss Messaging 服务都位于服务器端点的根目录下且服务的配置处于 "
#~ "<filename>messaging-service.xml</filename> 配置文件里。下面是一个服务器端"
#~ "点（Server Peer）的配置，在这个例子里并没有列出所有的属性值。"
-
#~ msgid "Server Attributes"
#~ msgstr "服务器属性"
-
#~ msgid "This section discusses the MBean attributes of the ServerPeer MBean."
#~ msgstr "本部分讨论了 ServerPeer MBean 的 MBean 属性。"
-
#~ msgid "ServerPeerID"
#~ msgstr "ServerPeerID"
-
#~ msgid ""
#~ "The <classname>ServerPeerID</classname> is the unique ID of the server "
#~ "peer that every node you deploy <emphasis>must</emphasis> have. This "
@@ -235,34 +198,27 @@
#~ "classname>ServerPeerID</classname> 是你部署的每个节点都<emphasis>必须</"
#~ "emphasis>具有的唯一的服务器端点 ID。无论是群集里的还是通过消息桥链接的不同"
#~ "节点，这都适用。这个 ID 必须是一个有效的整数。"
-
#~ msgid ""
#~ "The scope of <classname>ServerPeerID</classname> is currently from 0 to "
#~ "255. <!-- Future releases will see this enlarged to 1023 -->"
#~ msgstr ""
#~ "<classname>ServerPeerID</classname> 的范围是 0 到 255（以后版本会改为 0 "
#~ "到 1023）。"
-
#~ msgid "DefaultQueueJNDIContext"
#~ msgstr "DefaultQueueJNDIContext"
-
#~ msgid ""
#~ "The default JNDI context to use when binding queues. Defaults to "
#~ "<literal>/queue</literal>."
#~ msgstr ""
#~ "绑定队列时使用的缺省 JNDI 上下文。缺省为 <literal>/queue</literal>。"
-
#~ msgid "DefaultTopicJNDIContext"
#~ msgstr "DefaultTopicJNDIContext"
-
#~ msgid ""
#~ "The default JNDI context to use when binding topics.wa Defaults to "
#~ "<literal>/topic</literal>."
#~ msgstr "绑定主题时使用的缺省 JNDI。缺省为 <literal>/topic</literal>。"
-
#~ msgid "PostOffice"
#~ msgstr "PostOffice"
-
#~ msgid ""
#~ "This is the post office that the ServerPeer uses. You will not normally "
#~ "need to change this attribute. The post office is responsible for routing "
@@ -271,10 +227,8 @@
#~ msgstr ""
#~ "这是 ServerPeer 使用的邮局。你通常不需要修改这个属性。邮局负责把消息路由到"
#~ "队列并维护地址和队列间的映射。"
-
#~ msgid "DefaultDLQ"
#~ msgstr "DefaultDLQ"
-
#~ msgid ""
#~ "This is the name of the default DLQ (Dead Letter Queue) the server peer "
#~ "will use for destinations. The DLQ can be overridden on a per destination "
@@ -293,24 +247,19 @@
#~ "如果没有指定 DLQ，那么在尝试指定的次数后消息将被删除。递送的最多尝试次数可"
#~ "以用 DefaultMaxDeliveryAttempts 来指定，这可以作为全局缺省值或者是对于每个"
#~ "目的地进行设置。"
-
#~ msgid "DefaultMaxDeliveryAttempts"
#~ msgstr "DefaultMaxDeliveryAttempts"
-
#~ msgid ""
#~ "The default for the maximum number of times delivery of a message will be "
#~ "attempted before sending the message to the DLQ, if configured."
#~ msgstr ""
#~ "如果进行了配置，在发往 DLQ 之前，消息将进行所指定的最多次数的递送尝试。"
-
#~ msgid ""
#~ "The default value is 10.This value can also be overridden on a per "
#~ "destination basis."
#~ msgstr "缺省值是10。这个值也可以根据每个目的地进行覆盖。"
-
#~ msgid "DefaultExpiryQueue"
#~ msgstr "DefaultExpiryQueue"
-
#~ msgid ""
#~ "This is the name of the default expiry queue the server peer will use for "
#~ "destinations. The expiry can be overridden on a per destination basis - "
@@ -325,10 +274,8 @@
#~ "特殊的目的地，当消息过期时就会被送到这里。消息是否过期是由 Message::"
#~ "getJMSExpiration() 的值决定的，如果没有指定 expiry 队列，消息在过期后将被"
#~ "删除。"
-
#~ msgid "DefaultRedeliveryDelay"
#~ msgstr "DefaultRedeliveryDelay"
-
#~ msgid ""
#~ "When redelivering a message after failure of previous delivery it is "
#~ "often beneficial to introduce a delay perform redelivery in order to "
@@ -336,42 +283,32 @@
#~ msgstr ""
#~ "当在前次递送失败后再重新递送消息时，引入一个延迟机制以防止递送失败的拥塞通"
#~ "常是有益的。"
-
#~ msgid "The default value is 0 which means there will be no delay."
#~ msgstr "缺省值是 0，表示没有延迟。"
-
#~ msgid ""
#~ "Change this if your application could benefit with a delay before "
#~ "redelivery. This value can also be overridden on a per destination basis."
#~ msgstr ""
#~ "如果你的应用程序可以受益于在重新递送前采用延迟，你可以修改它。这个值也可以"
#~ "根据每个目的地进行设置。"
-
#~ msgid "MessageCounterSamplePeriod"
#~ msgstr "MessageCounterSamplePeriod"
-
#~ msgid ""
#~ "Periodically the server will query each queue to gets its statistics. "
#~ "This is the period."
#~ msgstr "服务器将定期查询每个队列以获取统计信息。这里是时间间隔。"
-
#~ msgid "The default value is 10000 milliseconds."
#~ msgstr "缺省值是 10000 毫秒。"
-
#~ msgid "FailoverStartTimeout"
#~ msgstr "FailoverStartTimeout"
-
#~ msgid ""
#~ "The maximum number of milliseconds the client will wait for failover to "
#~ "start on the server side when a problem is detected."
#~ msgstr "当检测到问题时，客户等待失效切换启动的时间，以毫秒未单位。"
-
#~ msgid "The default value is 60000 (one minute)."
#~ msgstr "缺省值是 60000（1分钟）。"
-
#~ msgid "FailoverCompleteTimeout"
#~ msgstr "FailoverCompleteTimeout"
-
#~ msgid ""
#~ "The maximum number of milliseconds the client will wait for failover to "
#~ "complete on the server side after it has started. The default value is "
@@ -379,10 +316,8 @@
#~ msgstr ""
#~ "客户等待服务器端的失效切换完成前所等待的最长时间（毫秒）。缺省值是 30000"
#~ "（5分钟）。"
-
#~ msgid "DefaultMessageCounterHistoryDayLimit"
#~ msgstr "DefaultMessageCounterHistoryDayLimit"
-
#~ msgid ""
#~ "JBoss Messaging provides a message counter history which shows the number "
#~ "of messages arriving on each queue of a certain number of days. This "
@@ -392,10 +327,8 @@
#~ "JBoss Messaging 提供了一个消息计数器历史，它显示了一段时间里消息到达每个队"
#~ "列的消息数量。这个属性代表了存储消息技术器历史的最大天数。它可以根据每个目"
#~ "的地进行覆盖。"
-
#~ msgid "ClusterPullConnectionFactory"
#~ msgstr "ClusterPullConnectionFactory"
-
#~ msgid ""
#~ "The name of the connection factory to use for pulling messages between "
#~ "nodes. If you wish to turn off message sucking between queues altogether, "
@@ -403,20 +336,16 @@
#~ msgstr ""
#~ "在节点获取消息所使用的连接工厂的名称。如果你想关闭队列间的消息停留而保持失"
#~ "效切换，你可以忽略这个属性。"
-
#~ msgid "DefaultPreserveOrdering"
#~ msgstr "DefaultPreserveOrdering"
-
#~ msgid ""
#~ "If true, then strict JMS ordering is preserved in the cluster. See the "
#~ "cluster configurations section for more details. Default is false."
#~ msgstr ""
#~ "如果未 true，那么群集里将实行严格的 JMS 顺序。更多细节请参考群集配置部分的"
#~ "内容。它缺省为 false。"
-
#~ msgid "RecoverDeliveriesTimeout"
#~ msgstr "RecoverDeliveriesTimeout"
-
#~ msgid ""
#~ "When failover occurs, already delivered messages will be kept aside, "
#~ "waiting for clients to reconnect. In the case that clients never "
@@ -427,7 +356,6 @@
#~ "当失效切换发生时，已经递送的消息将被放到一旁，等待客户的重新连接。如果客户"
#~ "不再进行连接（也就是客户端已经终止），那么这些消息最终会超时并加入到队列"
#~ "里。它的值以毫秒为单位，缺省未 5 毫秒。"
-
#~ msgid ""
#~ "JBoss Messaging internally makes connections between nodes in order to "
#~ "redistribute messages between clustered destinations. These connections "
@@ -442,10 +370,8 @@
#~ "SecurityStore <literal>mbean</literal> 配置文件（<filename>messaging-"
#~ "jboss-beans.xml</filename>）里配置 sucker 密码，而 ServerPeer Sucker 密码"
#~ "将被忽略。"
-
#~ msgid "Warning"
#~ msgstr "警告"
-
#~ msgid ""
#~ "This must be specified at install time, or the default password will be "
#~ "used. Any one who then knows the default password will be able to gain "
@@ -455,61 +381,45 @@
#~ "这必须在安装时指定，或者使用缺省的密码。任何知道缺省密码的人的都可以访问服"
#~ "务器上的任何目的地。这个值 <emphasis>must</emphasis> 必须在安装时进行修"
#~ "改。"
-
#~ msgid "StrictTCK"
#~ msgstr "StrictTCK"
-
#~ msgid "Set to true if you want strict JMS TCK semantiocs"
#~ msgstr "如果你想要严格的 JMS TCK 模式，把它设置为 true。"
-
#~ msgid "Destinations"
#~ msgstr "目的地"
-
#~ msgid ""
#~ "Returns a list of the destinations (queues and topics) currently deployed."
#~ msgstr "返回当前部署的一个目的地（队列和主题）的列表。"
-
#~ msgid "MessageCounters"
#~ msgstr "MessageCounters"
-
#~ msgid "JBoss Messaging provides a message counter for each queue."
#~ msgstr "JBoss Messaging 未每个对列提供了一个消息计数器。"
-
#~ msgid "MessageStatistics"
#~ msgstr "MessageStatistics"
-
#~ msgid ""
#~ "JBoss Messaging provides statistics for each message counter for each "
#~ "queue."
#~ msgstr "JBoss Messaging 为每个队列都提供消息的统计。"
-
#~ msgid "SupportsFailover"
#~ msgstr "SupportsFailover"
-
#~ msgid ""
#~ "Set to false to prevent server side failover occurring in a cluster when "
#~ "a node crashes."
#~ msgstr "设置为 false 可以防止在节点崩溃时服务器端失效切换的发生。"
-
#~ msgid "PersistenceManager"
#~ msgstr "PersistenceManager"
-
#~ msgid ""
#~ "This is the persistence manager that the ServerPeer uses. You will not "
#~ "normally need to change this attribute."
#~ msgstr "这是 ServerPeer 使用的持久化管理者。通常你不需要修改这个属性。"
-
#~ msgid "JMSUserManager"
#~ msgstr "JMSUserManager"
-
#~ msgid ""
#~ "This is the JMS user manager that the ServerPeer uses. You will not "
#~ "normally need to change this attribute."
#~ msgstr "这是 ServerPeer 使用的 JMS 用户管理者。通常你不需要修改这个属性。"
-
#~ msgid "SecurityStore"
#~ msgstr "SecurityStore"
-
#~ msgid ""
#~ "This is the pluggable SecurityStore. If you redefine this SecurityStore, "
#~ "notice it will need to authenticate the MessageSucker user (\"JBM.SUCKER"
@@ -518,13 +428,10 @@
#~ "这是可插拔的 SecurityStore。如果你重新定义了这个SecurityStore，请注意它将"
#~ "需要用群集所要求的所有特殊权限来验证 MessageSucker 用户（\"JBM.SUCKER"
#~ "\"）。"
-
#~ msgid "MBean operations of the ServerPeer MBean"
#~ msgstr "ServerPeer MBean 的操作。"
-
#~ msgid "DeployQueue"
#~ msgstr "DeployQueue"
-
#~ msgid ""
#~ "This operation lets you programmatically deploy a queue. There are two "
#~ "overloaded versions of this operation. If the queue already exists but is "
@@ -540,7 +447,6 @@
#~ "部署的目的地的名称。<literal>jndiName</literal> 参数（可选）代表绑定目的地"
#~ "的完整 JNDI 名称。如果没有指定，那么目的地将绑定到 <literal><"
#~ "DefaultQueueJNDIContext>/<name></literal>。"
-
#~ msgid ""
#~ "The first version of this operation deploys the destination with the "
#~ "default paging parameters. The second overloaded version deploys the "
@@ -550,10 +456,8 @@
#~ msgstr ""
#~ "这个操作的第一个版本用缺省的页面参数部署目的地。第二个重载版本用指定的页面"
#~ "参数部署目的地。请参考配置目的地章节关于页面参数含义的部分。"
-
#~ msgid "UndeployQueue"
#~ msgstr "UndeployQueue"
-
#~ msgid ""
#~ "This operation lets you programmatically undeploy a queue. The queue is "
#~ "undeployed but is NOT removed from persistent storage. This operation "
@@ -562,44 +466,34 @@
#~ msgstr ""
#~ "这个操作让你在程序里卸载队列。这个队列被卸载但没有从持久性存储里移除。如果"
#~ "队列成功地卸载，这个操作返回 true。否则它返回 false。"
-
#~ msgid "DestroyQueue"
#~ msgstr "DestroyQueue"
-
#~ msgid ""
#~ "This operation lets you programmatically destroy a queue. The queue is "
#~ "undeployed and then all its data is destroyed from the database."
#~ msgstr ""
#~ "这个操作让你可以在程序里销毁一个队列。这个队列被卸载且所有数据都从数据库里"
#~ "销毁。"
-
#~ msgid ""
#~ "Be cautious when using this method since it will delete all data for the "
#~ "queue."
#~ msgstr "使用这个方法要谨慎，因为它将删除队列里的所有数据。"
-
#~ msgid ""
#~ "This operation returns true if the queue was successfully destroyed. "
#~ "otherwise it returns false."
#~ msgstr "如果队列被成功销毁，这个操作返回 true，否则返回 false。"
-
#~ msgid "DeployTopic"
#~ msgstr "DeployTopic"
-
#~ msgid "This operation lets you programmatically deploy a topic."
#~ msgstr "这个操作让你可以在程序里销毁一个主题。"
-
#~ msgid "There are two overloaded versions of this operation."
#~ msgstr "这个操作有两个重载版本。"
-
#~ msgid ""
#~ "If the topic already exists but is undeployed it is deployed. Otherwise "
#~ "it is created and deployed."
#~ msgstr "如果这个主题已经存在但已经卸载则进行部署。否则创建并部署它。"
-
#~ msgid "The name parameter represents the name of the destination to deploy."
#~ msgstr "name 参数代表了要部署的目的地的名称。"
-
#~ msgid ""
#~ "The jndiName parameter (optional) represents the full jndi name where to "
#~ "bind the destination. If this is not specified then the destination will "
@@ -607,10 +501,8 @@
#~ msgstr ""
#~ "jndiName 参数（可选）代表绑定目的地的完整的 JNDI 名称。如果没有指定，那么"
#~ "目的地将绑定在 <DefaultTopicJNDIContext>/<name>。"
-
#~ msgid "UndeployTopic"
#~ msgstr "UndeployTopic"
-
#~ msgid ""
#~ "This operation lets you programmatically undeploy a topic. The queue is "
#~ "undeployed but is NOT removed from persistent storage. This operation "
@@ -619,73 +511,57 @@
#~ msgstr ""
#~ "这个操作让你在程序里卸载主题。这个队列被卸载但没有从持久性存储里移除。如果"
#~ "主题被成功卸载这个操作返回 true，否则返回 false。"
-
#~ msgid "DestroyTopic"
#~ msgstr "DestroyTopic"
-
#~ msgid "This operation lets you programmatically destroy a topic."
#~ msgstr "这个操作让你在程序里销毁主题。"
-
#~ msgid ""
#~ "The topic is undeployed and then all its data is destroyed from the "
#~ "database."
#~ msgstr "主题被卸载且所有数据从数据库里销毁。"
-
#~ msgid ""
#~ "Be careful when using this method since it will delete all data for the "
#~ "topic."
#~ msgstr "使用这个方法要小心，因为它将删除主题的所有数据。"
-
#~ msgid ""
#~ "This operation returns true if the topic was successfully destroyed. "
#~ "otherwise it returns false."
#~ msgstr "如果主题被成功销毁，这个操作将返回 true，否则返回 false。"
-
#~ msgid "ListMessageCountersAsHTML"
#~ msgstr "ListMessageCountersAsHTML"
-
#~ msgid ""
#~ "This operation returns message counters in an easy to display HTML format."
#~ msgstr "这个操作以 HTML 格式返回消息计数。"
-
#~ msgid "ResetAllMesageCounters"
#~ msgstr "ResetAllMesageCounters"
-
#~ msgid "This operation resets all message counters to zero."
#~ msgstr "这个操作把所有消息计数器重置为零。"
-
#~ msgid "EnableMessageCounters"
#~ msgstr "EnableMessageCounters"
-
#~ msgid ""
#~ "This operation enables all message counters for all destinations. Message "
#~ "counters are disabled by default."
#~ msgstr ""
#~ "这个操作启用了所有目的地上的所有消息计数器。消息计数器缺省是被禁用的。"
-
#~ msgid "DisableMessageCounters"
#~ msgstr "DisableMessageCounters"
-
#~ msgid ""
#~ "This operation disables all message counters for all destinations. "
#~ "Message counters are disabled by default."
#~ msgstr ""
#~ "这个操作禁用了所有目的地上的所有消息计数器。消息计数器缺省是被禁用的。"
-
#~ msgid "RetrievePreparedTransactions"
#~ msgstr "RetrievePreparedTransactions"
-
#~ msgid ""
#~ "Retrieves a list of the Xids for all transactions currently in a prepared "
#~ "state on the node."
#~ msgstr "获取节点上当前处于 prepared 状态的所有事务的 XID 列表。"
-
#~ msgid "ShowPreparedTransactionsAsHTML"
#~ msgstr "ShowPreparedTransactionsAsHTML"
-
#~ msgid ""
#~ "Retrieves a list of the Xids for all transactions currently in a prepared "
#~ "state on the node in an easy to display HTML format."
#~ msgstr ""
#~ "获取节点上当前处于 prepared 状态的所有事务的 XID 列表，并以 HTML 格式显"
#~ "示。"
+
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po 2010-03-17 01:31:08 UTC (rev 102495)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po 2010-03-17 02:18:44 UTC (rev 102496)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-03-09T00:18:00\n"
-"PO-Revision-Date: 2010-02-03 10:24+1000\n"
+"PO-Revision-Date: 2010-03-17 10:46+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -23,29 +23,13 @@
#. Tag: para
#, no-c-format
-msgid ""
-"The JBoss security framework default implementation is based on JAAS. It "
-"implements standard J2EE authentication and authorization but also supports "
-"extended security models with <ulink url=\"http://wiki.jboss.org/wiki/Edit."
-"jsp?page=SecurityProxy\">SecurityProxy?</ulink> and <ulink url=\"http://wiki."
-"jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</"
-"ulink> implementations."
-msgstr ""
-"JBoss 安全框架的缺省实现基于 JAAS。它实现了标准的 J2EE 验证和授权，它也用 "
-"<ulink url=\"http://wiki.jboss.org/wiki/Edit.jsp?page=SecurityProxy"
-"\">SecurityProxy?</ulink> 和 <ulink url=\"http://wiki.jboss.org/wiki/Wiki."
-"jsp?page=SecurityAssociation\">SecurityAssociation</ulink> 实现来支持扩展的安"
-"全模型。"
+msgid "The JBoss security framework default implementation is based on JAAS. It implements standard J2EE authentication and authorization but also supports extended security models with <ulink url=\"http://wiki.jboss.org/wiki/Edit.jsp?page=SecurityProxy\">SecurityProxy?</ulink> and <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</ulink> implementations."
+msgstr "JBoss 安全框架的缺省实现基于 JAAS。它实现了标准的 J2EE 验证和授权，它也用 <ulink url=\"http://wiki.jboss.org/wiki/Edit.jsp?page=SecurityProxy\">SecurityProxy?</ulink> 和 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</ulink> 实现来支持扩展的安全模型。"
#. Tag: para
#, no-c-format
-msgid ""
-"JAAS based implementation enables pluggable authentication modules (PAMs) "
-"which is a way to integrate with existing authentication frameworks in your "
-"enterprise."
-msgstr ""
-"基于 JAAS 的实现启用了可插拔的验证模块（PAM），这是一种集成企业里现有验证框架"
-"的方法。"
+msgid "JAAS based implementation enables pluggable authentication modules (PAMs) which is a way to integrate with existing authentication frameworks in your enterprise."
+msgstr "基于 JAAS 的实现启用了可插拔的验证模块（PAM），这是一种集成企业里现有验证框架的方法。"
#. Tag: title
#, no-c-format
@@ -59,14 +43,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Previously the server.xml of the tomcat service contained either the "
-"JaasSecurityMgrRealm? or JaccAuthorizationRealm? (for JACC) in the "
-"<filename>server.xml</filename> Starting JBoss5, we have consolidated the "
-"realms into one \"org.jboss.web.tomcat.security.JBossWebRealm?\". The "
-"Authorization Framework is used to plugin default, jacc or xacml "
-"authorization modes."
-msgstr ""
+msgid "Previously the server.xml of the tomcat service contained either the JaasSecurityMgrRealm? or JaccAuthorizationRealm? (for JACC) in the <filename>server.xml</filename> Starting JBoss5, we have consolidated the realms into one \"org.jboss.web.tomcat.security.JBossWebRealm?\". The Authorization Framework is used to plugin default, jacc or xacml authorization modes."
+msgstr "之前的 Tomat 服务的 <filename>server.xml</filename> 包含 JaasSecurityMgrRealm? 或 JaccAuthorizationRealm?（用于 JACC），从 JBoss5 开始，我们将其合并为 \"org.jboss.web.tomcat.security.JBossWebRealm?\"。授权框架（Authorization Framework）用于 plugin default、jacc 或 xacml 授权模式。"
#. Tag: title
#, no-c-format
@@ -75,17 +53,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"We are making an effort to get away from the previous <ulink url=\"http://"
-"wiki.jboss.org/wiki/Wiki.jsp?page=JaasSecurityManagerService"
-"\">JaasSecurityManagerService</ulink> MBean service configuration in conf/"
-"jboss-service.xml. We are trying to introduce POJO beans such as the ones "
-"defined in deployers/security-deployer-beans.xml."
-msgstr ""
-"我们正在努力取消以前的 conf/jboss-service.xml 里的 <ulink url=\"http://wiki."
-"jboss.org/wiki/Wiki.jsp?page=JaasSecurityManagerService"
-"\">JaasSecurityManagerService</ulink> MBean 服务配置。我们正在尝试引入在 "
-"deployers/security-deployer-beans.xml 里定义的 POJO bean。"
+msgid "We are making an effort to get away from the previous <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JaasSecurityManagerService\">JaasSecurityManagerService</ulink> MBean service configuration in conf/jboss-service.xml. We are trying to introduce POJO beans such as the ones defined in deployers/security-deployer-beans.xml."
+msgstr "我们正在努力取消以前的 conf/jboss-service.xml 里的 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JaasSecurityManagerService\">JaasSecurityManagerService</ulink> MBean 服务配置。我们正在尝试引入在 deployers/security-deployer-beans.xml 里定义的 POJO bean。"
#. Tag: title
#, no-c-format
@@ -94,39 +63,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"We have the concept of <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
-"page=SecurityContext\">SecurityContext</ulink> to replace the legacy <ulink "
-"url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation"
-"\">SecurityAssociation</ulink>. Now it is possible to inject custom "
-"securitycontext objects by providing the FQN of it in the ejb2/web "
-"deployers. In the file: <filename>deployers/ejb-deployer-beans.xml</"
-"filename> <programlisting><bean name=\"EJB2xDeployer\" class=\"org.jboss."
-"ejb.deployers.EjbDeployer\"> ... <!-- Specify an unauthenticated "
-"identity --> <property name=\"unauthenticatedIdentity\">"
-"anonymous</property> <!-- Specify a SecurityManagement Wrapper --"
-"> <property name=\"securityManagement\"> <inject bean="
-"\"JNDIBasedSecurityManagement\"/> </property> <!-- Specify a "
-"SecurityContext FQN class name --> <property name="
-"\"securityContextClassName\">org.jboss.security.plugins."
-"JBossSecurityContext </property> <!-- Specify a SecurityDomain as "
-"fallback --> <property name=\"defaultSecurityDomain\">jboss-ejb-"
-"policy</property></programlisting> For the web deployer: In the file: "
-"<filename>deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml</"
-"filename> <programlisting><!-- The WebMetaData to service mbean deployer "
-"--> <bean name=\"WarDeployer\" class=\"org.jboss.web.tomcat.service."
-"deployers.TomcatDeployer\"> ... <!-- The JAAS security domain to use "
-"in the absense of an explicit security-domain specification in the war WEB-"
-"INF/jboss-web.xml --> <property name=\"defaultSecurityDomain\">"
-"java:/jaas/jboss-web-policy</property> <property name="
-"\"securityManagerService\"> <inject bean=\"jboss.security:"
-"service=JaasSecurityManager\" /> </property> <!-- Specify a "
-"SecurityManagement Wrapper --> <property name=\"securityManagement"
-"\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </"
-"property> <!-- Specify a SecurityContext FQN class name --> <"
-"property name=\"securityContextClassName\"> org.jboss.security.plugins."
-"JBossSecurityContext</property></programlisting>"
-msgstr ""
+msgid "We have the concept of <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityContext\">SecurityContext</ulink> to replace the legacy <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</ulink>. Now it is possible to inject custom securitycontext objects by providing the FQN of it in the ejb2/web deployers. In the file: <filename>deployers/ejb-deployer-beans.xml</filename> <programlisting><bean name=\"EJB2xDeployer\" class=\"org.jboss.ejb.deployers.EjbDeployer\"> ... <!-- Specify an unauthenticated identity --> <property name=\"unauthenticatedIdentity\">anonymous</property> <!-- Specify a SecurityManagement Wrapper --> <property name=\"securityManagement\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </property> <!-- Specify a SecurityContext FQN class name --> <property name=\"securityContextClassName\">org.jboss.security.plugins.JBossSecurityContext <!
;/property> <!-- Specify a SecurityDomain as fallback --> <property name=\"defaultSecurityDomain\">jboss-ejb-policy</property></programlisting> For the web deployer: In the file: <filename>deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml</filename> <programlisting><!-- The WebMetaData to service mbean deployer --> <bean name=\"WarDeployer\" class=\"org.jboss.web.tomcat.service.deployers.TomcatDeployer\"> ... <!-- The JAAS security domain to use in the absense of an explicit security-domain specification in the war WEB-INF/jboss-web.xml --> <property name=\"defaultSecurityDomain\">java:/jaas/jboss-web-policy</property> <property name=\"securityManagerService\"> <inject bean=\"jboss.security:service=JaasSecurityManager\" /> </property> <!-- Specify a SecurityManagement Wrapper --> <property name=\"securityManagement\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </property&!
gt; <!-- Specify a SecurityContext FQN class name --> &l!
t;proper
ty name=\"securityContextClassName\"> org.jboss.security.plugins.JBossSecurityContext</property></programlisting>"
+msgstr "我们用 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityContext\">SecurityContext</ulink> 概念来替代旧的<ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAssociation\">SecurityAssociation</ulink>。请注意，通过提供 FQN 在 ejb2/web 部署者里注入自定义的 securitycontext 对象是又可能的。在 <filename>deployers/ejb-deployer-beans.xml</filename> <programlisting><bean name=\"EJB2xDeployer\" class=\"org.jboss.ejb.deployers.EjbDeployer\"> ... <!-- Specify an unauthenticated identity --> <property name=\"unauthenticatedIdentity\">anonymous</property> <!-- Specify a SecurityManagement Wrapper --> <property name=\"securityManagement\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </property> <!-- Specify a SecurityContext FQN class name --> <property name=\"securityContextClassName\">org.jboss.security.plugins.JBossSecurityContext </property> <!--!
Specify a SecurityDomain as fallback --> <property name=\"defaultSecurityDomain\">jboss-ejb-policy</property></programlisting> For the web deployer: In the file: <filename>deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml</filename> <programlisting><!-- The WebMetaData to service mbean deployer --> <bean name=\"WarDeployer\" class=\"org.jboss.web.tomcat.service.deployers.TomcatDeployer\"> ... <!-- The JAAS security domain to use in the absense of an explicit security-domain specification in the war WEB-INF/jboss-web.xml --> <property name=\"defaultSecurityDomain\">java:/jaas/jboss-web-policy</property> <property name=\"securityManagerService\"> <inject bean=\"jboss.security:service=JaasSecurityManager\" /> </property> <!-- Specify a SecurityManagement Wrapper --> <property name=\"securityManagement\"> <inject bean=\"JNDIBasedSecurityManagement\"/> </property> <!-- Specify a !
SecurityContext FQN class name --> <property name=\"secu!
rityCont
extClassName\"> org.jboss.security.plugins.JBossSecurityContext</property></programlisting>"
#. Tag: title
#, no-c-format
@@ -135,11 +73,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"We have defined application policies \"jboss-ejb-policy\" and \"jboss-web-"
-"policy\" as the fall back security domains for the ejb and web layers. These "
-"are defined in deploy/security-policies-service.xml"
-msgstr ""
+msgid "We have defined application policies \"jboss-ejb-policy\" and \"jboss-web-policy\" as the fall back security domains for the ejb and web layers. These are defined in deploy/security-policies-service.xml"
+msgstr "我们已经把应用程序策略 \"jboss-ejb-policy\" 和 \"jboss-web-policy\" 定义为用于 ejb 和 web 层的 fall back 安全域。这些是在 deploy/security-policies-service.xml 文件里进行定义的。"
#. Tag: title
#, no-c-format
@@ -148,20 +83,8 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Securing web resources basically involves setting some stuff in the web "
-"deployment descriptor, and in jboss-web.xml. You also have to do a little "
-"prep work to the server itself to configure a security domain for JBoss SX. "
-"These instructions assume that you have JBoss AS installed, and you have a "
-"server instance created with at least Tomcat included. The \"default\" "
-"instance is a good choice here. The variable ${JBOSS_HOME} refers to the "
-"location you extracted/installed JBoss AS to, and ${server_configuration} "
-"corresponds to the name of the server instance you are configuring for "
-"security. The first part of these instructions refers to setting up JBoss SX "
-"for security, and the second part deals with setting up the web application "
-"for security using basic authentication. You can access the instructions in "
-"the following section."
-msgstr ""
+msgid "Securing web resources basically involves setting some stuff in the web deployment descriptor, and in jboss-web.xml. You also have to do a little prep work to the server itself to configure a security domain for JBoss SX. These instructions assume that you have JBoss AS installed, and you have a server instance created with at least Tomcat included. The \"default\" instance is a good choice here. The variable ${JBOSS_HOME} refers to the location you extracted/installed JBoss AS to, and ${server_configuration} corresponds to the name of the server instance you are configuring for security. The first part of these instructions refers to setting up JBoss SX for security, and the second part deals with setting up the web application for security using basic authentication. You can access the instructions in the following section."
+msgstr "设置 web 资源通常需要设置 web 部署描述符和 jboss-web.xml 里的某些内容。你也得在服务器上做一些准备工作来配置 JBoss SX 的安全域。这些说明都假设你已经安装了 JBoss AS，你也创建了一个服务器实例并带有 Tomcat。\"default\" 实例是个不错的选择。变量 ${JBOSS_HOME} 指的是解压/安装 JBoss AS 的位置，${server_configuration} 对应你在进行配置的服务器实例的名称。这些说明的第一部分指的是设立 JBoss SX 的安全性，第二部分用基本的验证处理 Web 应用程序的安全性。你可以在下面的部分看到这些说明。"
#. Tag: title
#, no-c-format
@@ -170,155 +93,31 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Setting up a security domain is simple with JBoss SX. The following "
-"instructions are a step by step methodology for creating a simple domain "
-"that uses two properties files to hold user ids, passwords, and roles for "
-"those users."
-msgstr ""
-"设置 JBoss SX 的安全域是很简单的。下面的说明是创建一个简单的安全域的逐步的方"
-"法，它使用两个属性文件来保存用户 ID、密码和角色。"
+msgid "Setting up a security domain is simple with JBoss SX. The following instructions are a step by step methodology for creating a simple domain that uses two properties files to hold user ids, passwords, and roles for those users."
+msgstr "设置 JBoss SX 的安全域是很简单的。下面的说明是创建一个简单的安全域的逐步的方法，它使用两个属性文件来保存用户 ID、密码和角色。"
#. Tag: para
#, no-c-format
-msgid ""
-"Open the <filename> ${JBOSS_HOME}/server/${server_configuration}/conf/login-"
-"config.xml</filename> file. This file sets up the configuration for the "
-"security domains available to applications running in the server. The file "
-"already has a few domains in there for some example/default resources, so "
-"you might want to look to those for inspiration. JBoss SX uses JAAS for the "
-"underlying security infrastructure, and JAAS uses a class called a \"login "
-"module\" to interact with a security store for authenticating credentials. "
-"This file basically hooks up a security domain (just a name really) to a "
-"JAAS login module. JBoss Enterprise Application Platform comes packed with a "
-"few different login modules which you can find more information about on the "
-"JBoss SX wiki page at JBossSX."
-msgstr ""
-"打开 <filename> ${JBOSS_HOME}/server/${server_configuration}/conf/login-"
-"config.xml</filename> 文件。这个文件对服务器里运行的应用程序可用的安全域进行"
-"配置。它也包含一些用于示例/缺省资源的域，所以你可以查看这些域以获取灵感。"
-"JBoss SX 使用 JAAS 作为底层的安全基础结构，JAAS 使用一个名为“登录模块”的类来"
-"和安全库（security store）进行交互以进行验证。这个文件基本上安全域（实际上是"
-"其名称）和 JAAS 登录模块对应起来。JBoss 企业级应用程序平台带有一些不同的登录"
-"模块，你可以在 JBoss SX 维基页面种找到更多的信息。"
+msgid "Open the <filename> ${JBOSS_HOME}/server/${server_configuration}/conf/login-config.xml</filename> file. This file sets up the configuration for the security domains available to applications running in the server. The file already has a few domains in there for some example/default resources, so you might want to look to those for inspiration. JBoss SX uses JAAS for the underlying security infrastructure, and JAAS uses a class called a \"login module\" to interact with a security store for authenticating credentials. This file basically hooks up a security domain (just a name really) to a JAAS login module. JBoss Enterprise Application Platform comes packed with a few different login modules which you can find more information about on the JBoss SX wiki page at JBossSX."
+msgstr "打开 <filename> ${JBOSS_HOME}/server/${server_configuration}/conf/login-config.xml</filename> 文件。这个文件对服务器里运行的应用程序可用的安全域进行配置。它也包含一些用于示例/缺省资源的域，所以你可以查看这些域以获取灵感。JBoss SX 使用 JAAS 作为底层的安全基础结构，JAAS 使用一个名为“登录模块”的类来和安全库（security store）进行交互以进行验证。这个文件基本上安全域（实际上是其名称）和 JAAS 登录模块对应起来。JBoss 企业级应用程序平台带有一些不同的登录模块，你可以在 JBoss SX 维基页面种找到更多的信息。"
#. Tag: para
#, no-c-format
-msgid ""
-"The easiest login module to start with is the <ulink url=\"http://wiki.jboss."
-"org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</"
-"ulink>. This login module allows you to specify user names, passwords and "
-"roles in a simple property file. Obviously, this module isn't one of the "
-"more secure modules, so you probably would want to use something like LDAP "
-"to store/lookup credentials in production."
-msgstr ""
+msgid "The easiest login module to start with is the <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</ulink>. This login module allows you to specify user names, passwords and roles in a simple property file. Obviously, this module isn't one of the more secure modules, so you probably would want to use something like LDAP to store/lookup credentials in production."
+msgstr "最简单的登录模块是 <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</ulink>。这个登录模块允许你在一个简单的属性文件里指定用户名、密码和角色。很显然，这个模块不是最安全的模块之一，所以在产品环境里，你可能希望使用 LDAP 之类的技术来存储/查找 credential。"
#. Tag: para
#, no-c-format
-msgid ""
-"Copy the \"jmx-console\" domain policy as a starting point. The \"jmx-console"
-"\" security domain policy contains the basics for configuring a "
-"UsersRolesLoginModule based security domain. Here is a copy of that section: "
-"<programlisting><application-policy name = \"jmx-console\"> <"
-"authentication> <login-module code=\"org.jboss.security.auth.spi."
-"UsersRolesLoginModule\" flag = \"required\"> <module-option name="
-"\"usersProperties\"> props/jmx-console-users.properties </module-"
-"option> <module-option name=\"rolesProperties\"> props/jmx-console-"
-"roles.properties </module-option> </login-module> </"
-"authentication> </application-policy></programlisting> Copy this "
-"section to the bottom of the file, and change the \"name\" attribute on the "
-"application-policy attribute to \"my-web\". Also, change the \"userProperties"
-"\" module-option text value to be \"props/my-web-users.properties\", and the "
-"\"roleProperties\" module-option text value to be \"props/my-web-roles."
-"properties\". Save the login-config.xml file. The \"name\" attribute on the "
-"\"application-policy\" element specifies the name of the security domain. "
-"This name is important because it is what will be used to tie the security "
-"domain to the web application later. The \"login-module\" element specifies "
-"the login module that this domain will use. You can actually have multiple "
-"\"login-module\" elements to have multi-level authentication, but we'll "
-"stick to one for this simple case. The \"flag\" attribute on the login-"
-"module element specifies how to handle failed authentications from this "
-"module, and how it interacts with other modules. The \"required\" value is "
-"what you would want for a single login module, but you can refer to the DTD "
-"for the login-config.xml file for more info about the other options. "
-"Finally, the \"module-option\" elements specify some values to pass into the "
-"login module's \"initialize\" method. These values are passed in as a name-"
-"value map to that method. In the case of the <ulink url=\"http://wiki.jboss."
-"org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</"
-"ulink>, we need to tell the module what properties files to use for looking "
-"up user information (usersProperties), and what file to use for looking up "
-"role information (rolesProperties). These paths are relative to the "
-"${JBOSS_HOME}/server/${server_configuration}/conf directory."
-msgstr ""
-"复制 \"jmx-console\" 域策略以之为起点。\"jmx-console\" 域策略包含配置基于 "
-"UsersRolesLoginModule 的安全域的基本信息。下面是该部分的内容："
-"<programlisting><application-policy name = \"jmx-console\"> <"
-"authentication> <login-module code=\"org.jboss.security.auth.spi."
-"UsersRolesLoginModule\" flag = \"required\"> <module-option name="
-"\"usersProperties\"> props/jmx-console-users.properties </module-"
-"option> <module-option name=\"rolesProperties\"> props/jmx-console-"
-"roles.properties </module-option> </login-module> </"
-"authentication> </application-policy></programlisting> Copy this "
-"section to the bottom of the file, and change the \"name\" attribute on the "
-"application-policy attribute to \"my-web\". Also, change the \"userProperties"
-"\" module-option text value to be \"props/my-web-users.properties\", and the "
-"\"roleProperties\" module-option text value to be \"props/my-web-roles."
-"properties\". 保存 login-config.xml 文件。\"application-policy\" 元素的 "
-"\"name\" 属性指定了安全域的名称。This name is important because it is what "
-"will be used to tie the security domain to the web application later. The "
-"\"login-module\" element specifies the login module that this domain will "
-"use. You can actually have multiple \"login-module\" elements to have multi-"
-"level authentication, but we'll stick to one for this simple case. The \"flag"
-"\" attribute on the login-module element specifies how to handle failed "
-"authentications from this module, and how it interacts with other modules. "
-"The \"required\" value is what you would want for a single login module, but "
-"you can refer to the DTD for the login-config.xml file for more info about "
-"the other options. Finally, the \"module-option\" elements specify some "
-"values to pass into the login module's \"initialize\" method. These values "
-"are passed in as a name-value map to that method. In the case of the <ulink "
-"url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=UsersRolesLoginModule"
-"\">UsersRolesLoginModule</ulink>, we need to tell the module what properties "
-"files to use for looking up user information (usersProperties), and what "
-"file to use for looking up role information (rolesProperties). These paths "
-"are relative to the ${JBOSS_HOME}/server/${server_configuration}/conf "
-"directory."
+msgid "Copy the \"jmx-console\" domain policy as a starting point. The \"jmx-console\" security domain policy contains the basics for configuring a UsersRolesLoginModule based security domain. Here is a copy of that section: <programlisting><application-policy name = \"jmx-console\"> <authentication> <login-module code=\"org.jboss.security.auth.spi.UsersRolesLoginModule\" flag = \"required\"> <module-option name=\"usersProperties\"> props/jmx-console-users.properties </module-option> <module-option name=\"rolesProperties\"> props/jmx-console-roles.properties </module-option> </login-module> </authentication> </application-policy></programlisting> Copy this section to the bottom of the file, and change the \"name\" attribute on the application-policy attribute to \"my-web\". Also, change the \"userProperties\" module-option text value to be \"props/my-web-users.properties\", and the \"roleProperties\" module-option !
text value to be \"props/my-web-roles.properties\". Save the login-config.xml file. The \"name\" attribute on the \"application-policy\" element specifies the name of the security domain. This name is important because it is what will be used to tie the security domain to the web application later. The \"login-module\" element specifies the login module that this domain will use. You can actually have multiple \"login-module\" elements to have multi-level authentication, but we'll stick to one for this simple case. The \"flag\" attribute on the login-module element specifies how to handle failed authentications from this module, and how it interacts with other modules. The \"required\" value is what you would want for a single login module, but you can refer to the DTD for the login-config.xml file for more info about the other options. Finally, the \"module-option\" elements specify some values to pass into the login module's \"initialize\" method. These values are passed !
in as a name-value map to that method. In the case of the <uli!
nk url=\
"http://wiki.jboss.org/wiki/Wiki.jsp?page=UsersRolesLoginModule\">UsersRolesLoginModule</ulink>, we need to tell the module what properties files to use for looking up user information (usersProperties), and what file to use for looking up role information (rolesProperties). These paths are relative to the ${JBOSS_HOME}/server/${server_configuration}/conf directory."
+msgstr "复制 \"jmx-console\" 域策略以之为起点。\"jmx-console\" 域策略包含配置基于 UsersRolesLoginModule 的安全域的基本信息。下面是该部分的内容：<programlisting><application-policy name = \"jmx-console\"> <authentication> <login-module code=\"org.jboss.security.auth.spi.UsersRolesLoginModule\" flag = \"required\"> <module-option name=\"usersProperties\"> props/jmx-console-users.properties </module-option> <module-option name=\"rolesProperties\"> props/jmx-console-roles.properties </module-option> </login-module> </authentication> </application-policy></programlisting> Copy this section to the bottom of the file, and change the \"name\" attribute on the application-policy attribute to \"my-web\". Also, change the \"userProperties\" module-option text value to be \"props/my-web-users.properties\", and the \"roleProperties\" module-option text value to be \"props/my-web-roles.pro!
perties\". 保存 login-config.xml 文件。\"application-policy\" 元素的 \"name\" 属性指定了安全域的名称。This name is important because it is what will be used to tie the security domain to the web application later. The \"login-module\" element specifies the login module that this domain will use. You can actually have multiple \"login-module\" elements to have multi-level authentication, but we'll stick to one for this simple case. The \"flag\" attribute on the login-module element specifies how to handle failed authentications from this module, and how it interacts with other modules. The \"required\" value is what you would want for a single login module, but you can refer to the DTD for the login-config.xml file for more info about the other options. Finally, the \"module-option\" elements specify some values to pass into the login module's \"initialize\" method. These values are passed in as a name-value map to that method. In the case of the <ulink u!
rl=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=UsersRolesLoginM!
odule\">
UsersRolesLoginModule</ulink>, we need to tell the module what properties files to use for looking up user information (usersProperties), and what file to use for looking up role information (rolesProperties). These paths are relative to the ${JBOSS_HOME}/server/${server_configuration}/conf directory."
#. Tag: para
#, no-c-format
-msgid ""
-"In the ${JBOSS_HOME}/server/conf/props directory, copy the jmx-console-users."
-"properties into a new file called my-web-users.properties, and copy the jmx-"
-"console-roles.properties into a new file called my-web-roles.properties. "
-"Opening the my-web-users.properties file, you will see a single entry like "
-"this: \"admin=admin\". When a user logs into this security domain, the login "
-"module will examine the properties data in this file for known users. The "
-"structure of the entries in this file is \"username=password\". Let's add a "
-"new entry to the file for your own user by pasting \"chris=secure\" on a new "
-"line below the \"admin=admin\" line in the file. Save this file. Next, open "
-"the <filename>my-web-roles.properties</filename> file, and you should see an "
-"line like the following: \"<emphasis>admin=JBossAdmin,HttpInvoker</emphasis>"
-"\". The entries in this file define what roles a user has associated with "
-"their account when they login. The form of these entries is \"username=Role1,"
-"Role2,...\" where the username is the user you wish to assign roles to, and "
-"the Roles entries are a comma separated list of roles to assign to that "
-"user. Add a new entry to this file by pasting \"chris=WebAppUser\" on a new "
-"line below the \"admin=....\" line. Save this file."
-msgstr ""
-"在 ${JBOSS_HOME}/server/conf/props 目录里，把 jmx-console-users.properties 复"
-"制为一个名为 my-web-users.properties 的文件，并把 jmx-console-roles."
-"properties 复制为 my-web-roles.properties。打开 my-web-users.properties 文"
-"件，你将看到一个类似 \"admin=admin\" 的条目。当用户登录到这个安全域时，登录模"
-"块将检查这个文件李的属性数据来确认已知用户。这个文件里的条目的结构是 "
-"\"username=password\"。让我们在 \"admin=admin\" 下面添加一个自己的新条目 "
-"\"chris=secure\"。然后，打开 <filename>my-web-roles.properties</filename> 文"
-"件，你应该看到 \"<emphasis>admin=JBossAdmin,HttpInvoker</emphasis>\"。这个外"
-"键里的条目定义了用户相关联的角色。这些条目的格式是 \"username=Role1,Role2,..."
-"\"，这里的 username 你要分配角色的用户，而角色条目是一个以逗号隔开的角色列"
-"表。在 \"admin=....\" 下面添加一条 \"chris=WebAppUser\" 的条目。保存这个文"
-"件。"
+msgid "In the ${JBOSS_HOME}/server/conf/props directory, copy the jmx-console-users.properties into a new file called my-web-users.properties, and copy the jmx-console-roles.properties into a new file called my-web-roles.properties. Opening the my-web-users.properties file, you will see a single entry like this: \"admin=admin\". When a user logs into this security domain, the login module will examine the properties data in this file for known users. The structure of the entries in this file is \"username=password\". Let's add a new entry to the file for your own user by pasting \"chris=secure\" on a new line below the \"admin=admin\" line in the file. Save this file. Next, open the <filename>my-web-roles.properties</filename> file, and you should see an line like the following: \"<emphasis>admin=JBossAdmin,HttpInvoker</emphasis>\". The entries in this file define what roles a user has associated with their account when they login. The form of these entries is \"username=Ro!
le1,Role2,...\" where the username is the user you wish to assign roles to, and the Roles entries are a comma separated list of roles to assign to that user. Add a new entry to this file by pasting \"chris=WebAppUser\" on a new line below the \"admin=....\" line. Save this file."
+msgstr "在 ${JBOSS_HOME}/server/conf/props 目录里，把 jmx-console-users.properties 复制为一个名为 my-web-users.properties 的文件，并把 jmx-console-roles.properties 复制为 my-web-roles.properties。打开 my-web-users.properties 文件，你将看到一个类似 \"admin=admin\" 的条目。当用户登录到这个安全域时，登录模块将检查这个文件李的属性数据来确认已知用户。这个文件里的条目的结构是 \"username=password\"。让我们在 \"admin=admin\" 下面添加一个自己的新条目 \"chris=secure\"。然后，打开 <filename>my-web-roles.properties</filename> 文件，你应该看到 \"<emphasis>admin=JBossAdmin,HttpInvoker</emphasis>\"。这个外键里的条目定义了用户相关联的角色。这些条目的格式是 \"username=Role1,Role2,...\"，这里的 username 你要分配角色的用户，而角色条目是一个以逗号隔开的角色列表。在 \"admin=....\" 下面添加一条 \"chris=WebAp!
pUser\" 的条目。保存这个文件。"
#~ msgid "JBossAS"
#~ msgstr "JBossAS"
-
#~ msgid "JBoss Enterprise Application Platform"
#~ msgstr "JBoss 企业级应用程序平台"
+
More information about the jboss-cvs-commits
mailing list