[jboss-cvs] JBossAS SVN: r100735 - 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 Feb 9 01:04:03 EST 2010
Author: xhuang at jboss.com
Date: 2010-02-09 01:04:02 -0500 (Tue, 09 Feb 2010)
New Revision: 100735
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/Clustering_Guide_Entity_EJBs.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/Architecture.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Architecture.po 2010-02-09 05:51:04 UTC (rev 100734)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Architecture.po 2010-02-09 06:04:02 UTC (rev 100735)
@@ -8,8 +8,8 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:17\n"
-"PO-Revision-Date: 2009-02-02 20:07+1000\n"
-"Last-Translator: Xi HUANG\n"
+"PO-Revision-Date: 2010-02-09 10:34+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"
@@ -17,131 +17,92 @@
"X-Generator: KBabel 1.11.4\n"
#. Tag: title
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBoss Enterprise Application Platform 5 architecture"
-msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
+msgstr "Boss 企业级应用程序平台 5 的架构"
#. Tag: primary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "JBoss Enterprise Application Platform"
-msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
+msgstr "JBoss 企业级应用程序平台"
#. Tag: secondary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "architecture"
-msgstr "服务架构"
+msgstr "架构"
#. Tag: indexterm
#, no-c-format
-msgid ""
-"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 ""
+msgid "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>"
#. 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 ""
+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
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The JBoss Enterprise Application Platform Bootstrap"
-msgstr "用于 JBoss 企业级应用程序平台 4.3 Cumulative Patch 3"
+msgstr "JBoss 企业级应用程序平台的引导"
#. Tag: secondary
#, no-c-format
msgid "bootstrap"
-msgstr ""
+msgstr "bootstrap"
#. 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 ""
+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: secondary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Server interface implementation"
-msgstr "启用了 MTOM 的服务实现"
+msgstr "Server 接口的实现"
#. 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 ""
+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: primary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "ProfileService"
-msgstr "服务"
+msgstr "Profile 服务"
#. 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 ""
+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
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Hot Deployment"
-msgstr "部署"
+msgstr "热部署"
#. Tag: primary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Hot deployment"
-msgstr "部署"
+msgstr "热部署"
#. Tag: secondary
-#, fuzzy, no-c-format
+#, no-c-format
msgid "implementation"
-msgstr "Fragmentation"
+msgstr "实现"
#. 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 ""
+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: secondary
#, no-c-format
msgid "disabling"
-msgstr ""
+msgstr "禁用热部署"
#. Tag: para
#, no-c-format
-msgid ""
-"Disabling hot deployment is achieved by removing the <filename>hdscanner-"
-"jboss-beans.xml</filename> file from deployment."
-msgstr ""
+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> 文件可以禁用热部署。"
+
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-02-09 05:51:04 UTC (rev 100734)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Clustering_Guide_Entity_EJBs.po 2010-02-09 06:04:02 UTC (rev 100735)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:17\n"
-"PO-Revision-Date: 2010-02-02 14:59+1000\n"
+"PO-Revision-Date: 2010-02-09 11:21+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -74,67 +74,67 @@
#. Tag: para
#, no-c-format
msgid "Configuration of a the second-level cache is done via your EJB3 deployment's <filename>persistence.xml</filename>."
-msgstr ""
+msgstr "配置二级缓存是通过你的 EJB3 部署的 <filename>persistence.xml</filename> 来完成的。"
#. Tag: para
#, no-c-format
msgid "e.g."
-msgstr ""
+msgstr "例如"
#. Tag: term
#, no-c-format
msgid "hibernate.cache.use_second_level_cache"
-msgstr ""
+msgstr "hibernate.cache.use_second_level_cache"
#. Tag: para
#, no-c-format
msgid "Enables second-level caching of entities and collections."
-msgstr ""
+msgstr "启用实体和集合的二级缓存。"
#. Tag: term
-#, fuzzy, no-c-format
+#, no-c-format
msgid "hibernate.cache.use_query_cache"
-msgstr "<property name=\"hibernate.cache.use_query_cache\" value=\"true\"/>"
+msgstr "hibernate.cache.use_query_cache"
#. Tag: para
#, no-c-format
msgid "Enables second-level caching of queries."
-msgstr ""
+msgstr "启用二级查询缓存。"
#. Tag: term
#, no-c-format
msgid "hibernate.cache.region.factory_class"
-msgstr ""
+msgstr "hibernate.cache.region.factory_class"
#. 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 ""
+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 ""
+msgstr "共享的 Region 工厂对于所有的缓存 Region 使用相同的缓存 - 这和传统的 CacheProvider 实现很像。"
#. Tag: para
#, no-c-format
msgid "Hibernate ships with 2 shared region factory implementations:"
-msgstr ""
+msgstr "Hibernate 带有两个共享的 Region 工厂实现："
#. Tag: term
#, no-c-format
msgid "org.hibernate.cache.jbc2.SharedJBossCacheRegionFactory"
-msgstr ""
+msgstr "org.hibernate.cache.jbc2.SharedJBossCacheRegionFactory"
#. Tag: para
#, no-c-format
msgid "Uses a single JBoss Cache configuration, from a newly instantiated CacheManager, for all cache regions."
-msgstr ""
+msgstr "对于所有的缓存 Region，它使用新初始化的 CacheManager 里的一个简单的 JBoss 缓存配置。"
#. Tag: title
#, no-c-format
msgid "Additional properties for SharedJBossCacheRegionFactory"
-msgstr ""
+msgstr "SharedJBossCacheRegionFactory 的其他属性"
#. Tag: entry
#, no-c-format
@@ -154,7 +154,7 @@
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.cfg.shared"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.cfg.shared"
#. Tag: entry
#, no-c-format
@@ -164,37 +164,37 @@
#. Tag: entry
#, no-c-format
msgid "The classpath or filesystem resource containing the JBoss Cache configuration settings."
-msgstr ""
+msgstr "包含 JBoss Cache 配置设定的文件系统资源或 classpath。"
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.cfg.jgroups.stacks"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.cfg.jgroups.stacks"
#. Tag: entry
#, no-c-format
msgid "org/hibernate/cache/jbc2/builder/jgroups-stacks.xml"
-msgstr ""
+msgstr "org/hibernate/cache/jbc2/builder/jgroups-stacks.xml"
#. Tag: entry
#, no-c-format
msgid "The classpath or filesystem resource containing the JGroups protocol stack configurations."
-msgstr ""
+msgstr "包含 JGroups 协议栈配置的 classpath 或文件系统。"
#. Tag: term
#, no-c-format
msgid "org.hibernate.cache.jbc2.JndiSharedJBossCacheRegionFactory"
-msgstr ""
+msgstr "org.hibernate.cache.jbc2.JndiSharedJBossCacheRegionFactory"
#. Tag: para
#, no-c-format
msgid "Uses a single JBoss Cache configuration, from an existing CacheManager bound to JNDI, for all cache regions."
-msgstr ""
+msgstr "对于所有的缓存 region，使用绑定到 JNDI 的现有 CacheManager 的单一 JBoss Cache 配置。"
#. Tag: title
#, no-c-format
msgid "Additional properties for JndiSharedJBossCacheRegionFactory"
-msgstr ""
+msgstr "JndiSharedJBossCacheRegionFactory 的其他属性"
#. Tag: entry
#, no-c-format
@@ -204,117 +204,117 @@
#. Tag: entry
#, no-c-format
msgid "JNDI name to which the shared <literal>Cache</literal> instance is bound."
-msgstr ""
+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 ""
+msgstr "多路复用的 region 工厂使用独立的 Cache 实例，它对每个缓存 region 使用优化的配置。"
#. Tag: title
#, no-c-format
msgid "Common properties for multiplexed region factory implementations"
-msgstr ""
+msgstr "多路复用 region 工厂实现的共用属性"
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.cfg.entity"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.cfg.entity"
#. Tag: entry
#, no-c-format
msgid "optimistic-entity"
-msgstr ""
+msgstr "optimistic-entity"
#. 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 ""
+msgstr "用于实体缓存 region 的 JBoss Cache 配置。其他的配置：mvcc-entity、pessimistic-entity、mvcc-entity-repeatable、optimistic-entity-repeatable、pessimistic-entity-repeatable。"
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.cfg.collection"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.cfg.collection"
#. 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 ""
+msgstr "用于集合缓存 Region 的 JBoss Cache 配置。集合缓存 Region 通常使用和实体缓存 Region 相同的配置。"
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.cfg.query"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.cfg.query"
#. Tag: entry
#, no-c-format
msgid "local-query"
-msgstr ""
+msgstr "local-query"
#. 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 ""
+msgstr "用于查询缓存 region 的 JBoss Cache 配置。在缺省情况下，缓存的查询结果不会被复制。替代的配置有：replicated-query。"
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.cfg.ts"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.cfg.ts"
#. Tag: entry
#, no-c-format
msgid "timestamps-cache"
-msgstr ""
+msgstr "timestamps-cache"
#. 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 ""
+msgstr "用于时间戳缓存 Region 的 JBoss Cache 配置。如果使用了查询缓存，对应的时间戳缓存必须进行复制，即使查询缓存没有进行复制。时间戳缓存 region 不能共享和查询缓存相同的缓存。"
#. Tag: term
#, no-c-format
msgid "org.hibernate.cache.jbc2.MultiplexedJBossCacheRegionFactory"
-msgstr ""
+msgstr "org.hibernate.cache.jbc2.MultiplexedJBossCacheRegionFactory"
#. Tag: para
#, no-c-format
msgid "Uses separate JBoss Cache configurations, from a newly instantiated CacheManager, per cache region."
-msgstr ""
+msgstr "在刚初始化的 CacheManager 里，根据每个缓存 Region 使用独立的 JBoss Cache 配置。"
#. Tag: title
#, no-c-format
msgid "Additional properties for MultiplexedJBossCacheRegionFactory"
-msgstr ""
+msgstr "MultiplexedJBossCacheRegionFactory 的其他属性"
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.configs"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.configs"
#. Tag: entry
#, no-c-format
msgid "org/hibernate/cache/jbc2/builder/jbc2-configs.xml"
-msgstr ""
+msgstr "org/hibernate/cache/jbc2/builder/jbc2-configs.xml"
#. Tag: term
#, no-c-format
msgid "org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory"
-msgstr ""
+msgstr "org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory"
#. 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 ""
+msgstr "根据每个 Cache Region 使用 JNDI-bound CacheManager 里独立的 JBoss Cache 配置，请参考 <xref linkend=\"clustering-blocks-jbc-cachemanager\" />。"
#. Tag: title
#, no-c-format
msgid "Additional properties for JndiMultiplexedJBossCacheRegionFactory"
-msgstr ""
+msgstr "JndiMultiplexedJBossCacheRegionFactory 的其他属性"
#. Tag: entry
#, no-c-format
msgid "hibernate.cache.region.jbc2.cachefactory"
-msgstr ""
+msgstr "hibernate.cache.region.jbc2.cachefactory"
#. Tag: entry
#, fuzzy, no-c-format
@@ -372,9 +372,9 @@
msgstr "然后，你创建和实体相关的命名查询，并告诉 Hibernate 你要缓存该查询的结果。"
#. Tag: para
-#, fuzzy, no-c-format
+#, 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 的文档。"
+msgstr "@NamedQueries, @NamedQuery and @QueryHint 注解都在 javax.persistence 包里。关于如何使用 EJB3 查询以及缓存查询结果的更多信息，请参考 Hibernate 和 EJB3 的文档。 "
#. Tag: para
#, fuzzy, no-c-format
@@ -422,7 +422,7 @@
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 有可能把这个模式集成到以后的版本里。）"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
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 engine (see <ulink url=\"http://www.jboss.org/jbossgroup/partners.jsp\" />) provides different kinds of optimistic locking strategies that can work in a JBoss cluster."
-msgstr "如果你正在使用 Bean Managed Persistence (BMP），你将不得不实现自己的同步机制。MVCSoft CMP 2.0 持久化引擎（persistence engine）(请参考 <ulink url=\"http://www.jboss.org/jbossgroup/partners.jsp\"></ulink>）提供可以在 JBoss 群集里使用的各种优化锁定策略。"
+msgstr "如果你正在使用 Bean Managed Persistence (BMP），你将不得不实现自己的同步机制。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/Security.po
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po 2010-02-09 05:51:04 UTC (rev 100734)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/zh-CN/Security.po 2010-02-09 06:04:02 UTC (rev 100735)
@@ -8,7 +8,7 @@
"Project-Id-Version: Clustering_Guide_JNDI\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-12-09T13:49:19\n"
-"PO-Revision-Date: 2010-02-02 14:58+1000\n"
+"PO-Revision-Date: 2010-02-03 10:24+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -119,7 +119,7 @@
#. 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 <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 ""
+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
More information about the jboss-cvs-commits
mailing list