[jboss-cvs] JBossAS SVN: r95552 - projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Oct 26 00:47:00 EDT 2009
Author: xhuang at jboss.com
Date: 2009-10-26 00:46:59 -0400 (Mon, 26 Oct 2009)
New Revision: 95552
Modified:
projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/Server_Configurations.po
Log:
update
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/Server_Configurations.po
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/Server_Configurations.po 2009-10-26 04:30:16 UTC (rev 95551)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/Server_Configurations.po 2009-10-26 04:46:59 UTC (rev 95552)
@@ -10,7 +10,7 @@
"Project-Id-Version: Server_Configurations\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-09-14 00:28+0000\n"
-"PO-Revision-Date: 2009-10-21 12:11+1000\n"
+"PO-Revision-Date: 2009-10-26 11:42+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -68,9 +68,9 @@
#. Tag: para
#: Server_Configurations.xml:33
-#, fuzzy, no-c-format
+#, no-c-format
msgid "is a base Java EE 5 server profile containing a default set of services. It has the most frequently used services required to deploy a Java EE application. It does not include the JAXR service, the IIOP service, or any of the clustering services."
-msgstr "这是包含缺省服务集的基本的 J2EE 1.4 服务器配置。它有部署 J2EE 应用程序所需的最常用的服务。但它不包括 JAXR 服务、IIOP 服务或任何群集服务。请注意虽然这个配置被称为“default”，但服务器的实际缺省配置是“production”配置。"
+msgstr "这是包含缺省服务集的基本的 Java EE 5 服务器配置。它有部署 Java EE 应用程序所需的最常用的服务。但它不包括 JAXR 服务、IIOP 服务或任何群集服务。"
#. Tag: term
#: Server_Configurations.xml:39
@@ -80,9 +80,9 @@
#. Tag: para
#: Server_Configurations.xml:41
-#, fuzzy, no-c-format
+#, no-c-format
msgid "is based on the <literal>all</literal> profile, tuned for production; with log verbosity reduced, deployment scanning every 60 seconds, and memory usage tuned to accomodate production deployment requirements, among other things. This is the configuration that will be used by the server when it is started, if no other configuration is specified."
-msgstr "它基于 \"all\" 配置，但根据产品进行了调整 - 减少了冗余日志、每 60 秒进行部署扫描，它也调整了内存使用来符合产品部署的需要。如果没有指定其他配置，这是服务器启动时使用的配置。"
+msgstr "它基于 <literal>all</literal> 配置，但根据产品进行了调整 - 减少了冗余日志、每 60 秒进行部署扫描，它也调整了内存使用来符合产品部署的需要。如果没有指定其他配置，这是服务器启动时使用的配置。"
#. Tag: term
#: Server_Configurations.xml:47
@@ -92,15 +92,15 @@
#. Tag: para
#: Server_Configurations.xml:49
-#, fuzzy, no-c-format
+#, no-c-format
msgid "has a minimal configuration; the bare minimum services required to start JBoss. It starts the logging service, a JNDI server and a URL deployment scanner to find new deployments. This is what you would use if you want to use JMX/JBoss to start your own services without any other Java EE 5 technologies. This is just the bare server. There is no web container, no EJB or JMS support."
-msgstr "具有最小的配置 - 启动 JBoss 所需的最少服务。此配置仅仅启动日志服务、JNDI 服务器和用来发现新部署的 URL 部署扫描器。如果你想用 JMX/JBoss 来启动自己的服务而不使用任何 J2EE 技术的话，此配置就是合适的选择。使用本配置的服务器仅仅是一个“裸”服务器，没有 web 容器，不支持 EJB 或 JMS。它不是兼容 J2EE 1.4 的配置。"
+msgstr "具有最小的配置 - 启动 JBoss 所需的最少服务。此配置仅仅启动日志服务、JNDI 服务器和用来发现新部署的 URL 部署扫描器。如果你想用 JMX/JBoss 来启动自己的服务而不使用任何 Java EE 5 技术的话，此配置就是合适的选择。它没有 web 容器，不支持 EJB 或 JMS。"
#. Tag: term
#: Server_Configurations.xml:55
-#, fuzzy, no-c-format
+#, no-c-format
msgid "standard"
-msgstr "standardjaws.xml"
+msgstr "standard"
#. Tag: para
#: Server_Configurations.xml:57
@@ -110,9 +110,9 @@
#. Tag: term
#: Server_Configurations.xml:63
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<term>web</term>"
-msgstr "<term>all</term>"
+msgstr "<term>web</term>"
#. Tag: para
#: Server_Configurations.xml:65
@@ -158,6 +158,39 @@
"jmx-remoting.sar\n"
"</programlisting> while the web profile deployers and deploy directory contents are:"
msgstr ""
+"If you want to know which services are configured in each of these instances, the primary differences will be in the <filename class=\"directory\"><JBoss_Home>/server/<instance-name>/deployers/</filename> directory and also the services deployments in the <filename class=\"directory\"><JBoss_Home>/server/<instance-name>/deploy</filename> directory. For example, the default profile deployers and deploy directory contents are: <programlisting>\n"
+"[usr at localhost <JBoss_Home>]$<literal>ls server/default/deployers </literal>\n"
+"alias-deployers-jboss-beans.xml jboss-aop-jboss5.deployer\n"
+"bsh.deployer jboss-jca.deployer\n"
+"clustering-deployer-jboss-beans.xml jbossweb.deployer\n"
+"dependency-deployers-jboss-beans.xml jbossws.deployer\n"
+"directory-deployer-jboss-beans.xml j sr77-deployers-jboss-beans.xml\n"
+"ear-deployer-jboss-beans.xml metadata-deployer-jboss-beans.xml\n"
+"ejb-deployer-jboss-beans.xml seam.deployer\n"
+"ejb3.deployer security-deployer-jboss-beans.xml\n"
+"hibernate-deployer-jboss-beans.xml\n"
+"[usr at localhost <JBoss_Home>]$<literal>ls server/default/deploy </literal>\n"
+"ROOT.war jsr88-service.xml\n"
+"cache-invalidation-service.xml legacy-invokers-service.xml\n"
+"ejb2-container-jboss-beans.xml mail-ra.rar\n"
+"ejb2-timer-service.xml mail-service.xml\n"
+"ejb3-connectors-jboss-beans.xml management\n"
+"ejb3-container-jboss-beans.xml messaging\n"
+"ejb3-interceptors-aop.xml monitoring-service.xml\n"
+"ejb3-timer-service.xml profileservice-jboss-beans.xml\n"
+"hdscanner-jboss-beans.xml properties-service.xml\n"
+"hsqldb-ds.xml quartz-ra.rar\n"
+"http-invoker.sar remoting-jboss-beans.xml\n"
+"jboss-local-jdbc.rar schedule-manager-service.xml\n"
+"jboss-xa-jdbc.rar scheduler-service.xml\n"
+"jbossweb.sar security\n"
+"jbossws.sar sqlexception-service.xml\n"
+"jca-jboss-beans.xml transaction-jboss-beans.xml\n"
+"jms-ra.rar transaction-service.xml\n"
+"jmx-console.war uuid-key-generator.sar\n"
+"jmx-invoker-service.xml vfs-jboss-beans.xml\n"
+"jmx-remoting.sar\n"
+"</programlisting> while the web profile deployers and deploy directory contents are:"
#. Tag: programlisting
#: Server_Configurations.xml:76
@@ -177,24 +210,37 @@
"jboss-local-jdbc.rar transaction-jboss-beans.xml\n"
"jboss-xa-jdbc.rar"
msgstr ""
+"[usr at localhost <JBoss_Home>]$<literal>ls server/web/deployers </literal>\n"
+"alias-deployers-jboss-beans.xml jbossweb.deployer\n"
+"ejb3.deployer metadata-deployer-jboss-beans.xml\n"
+"jboss-aop-jboss5.deployer security-deployer-jboss-beans.xml\n"
+"jboss-jca.deployer\n"
+"[usr at localhost <JBoss_Home>]$<literal>ls server/web/deployers </literal>\n"
+"ROOT.war jbossweb.sar\n"
+"ejb3-container-jboss-beans.xml jca-jboss-beans.xml\n"
+"hdscanner-jboss-beans.xml jmx-console.war\n"
+"hsqldb-ds.xml jmx-invoker-service.xml\n"
+"http-invoker.sar security\n"
+"jboss-local-jdbc.rar transaction-jboss-beans.xml\n"
+"jboss-xa-jdbc.rar"
#. Tag: title
#: Server_Configurations.xml:79
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Adding Your Own Profile"
-msgstr "添加你自己的配置"
+msgstr "添加你自己的配置 "
#. Tag: para
#: Server_Configurations.xml:80
-#, fuzzy, no-c-format
+#, no-c-format
msgid "You can add your own profiles too. The best way to do this is to copy an existing one that is closest to your needs and modify the contents. For example, if you weren’t interested in using messaging, you could copy the production directory, renaming it as myconfig, remove the messaging subdirectory from the deploy folder and then start JBoss with the new profile using the command:"
-msgstr "你也可以添加自己的配置。最好的办法就是：复制把最贴近你需要的现有配置并进行修改。例如，如果对 messaging 不感兴趣，你可以复制 <literal>production</literal> 目录，将其命名为 <literal>myconfig</literal>，然后删除 <literal>jms</literal> 子目录并用这个新配置启动服务器。"
+msgstr "你也可以添加自己的配置。最好的办法就是：复制把最贴近你需要的现有配置并进行修改。例如，如果对 messaging 不感兴趣，你可以复制 production 目录，将其命名为 myconfig，然后删除 messaging 子目录并用这个新配置启动服务器："
#. Tag: programlisting
#: Server_Configurations.xml:82
#, no-c-format
msgid "run -c myconfig"
-msgstr ""
+msgstr "run -c myconfig"
#. Tag: para
#: Server_Configurations.xml:86
@@ -204,27 +250,27 @@
#. Tag: para
#: Server_Configurations.xml:89
-#, fuzzy, no-c-format
+#, no-c-format
msgid "To start the server using an alternate profile refer to <xref linkend=\"Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration\"/>."
msgstr "要用其他配置启动服务器，请参考 <xref linkend=\"Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration\"/>。"
#. Tag: title
#: Server_Configurations.xml:94
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Server Directory Structure"
-msgstr "目录结构"
+msgstr "服务器目录结构"
#. Tag: para
#: Server_Configurations.xml:95
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Installing JBoss Enterprise Application Platform creates a top level directory, which will be named <filename>jboss-eap-<version></filename> if you used the zip installation method, and will be named according to your specification if you used the GUI installer. Throughout this guide we refer to this top-level directory as the <filename>JBOSS_DIST</filename> directory."
-msgstr "如果你使用 zip 安装方法，安装 JBoss 企业级应用程序平台时会创建一个名为 <filename class=\"directory\">jboss-eap-<replaceable><version></replaceable></filename> 的顶层目录；如果你使用图形界面的安装方法，你就可以根据需要来命名。在这本指南里我们都将这个目录称为 <literal>JBOSS_DIST</literal>。在它下面有 4 个子目录："
+msgstr "如果你使用 zip 安装方法，安装 JBoss 企业级应用程序平台时会创建一个名为 <filename>jboss-eap-<version></filename> 的顶层目录；如果你使用图形界面的安装方法，你就可以根据需要来命名。在这本指南里我们都将这个目录称为 <literal>JBOSS_DIST</literal>。"
#. Tag: title
#: Server_Configurations.xml:100
-#, fuzzy, no-c-format
+#, no-c-format
msgid "<filename>JBOSS_DIST/jboss-as</filename> directory structure"
-msgstr "JBOSS_DIST/jboss-as 目录结构"
+msgstr "<filename>JBOSS_DIST/jboss-as</filename> 目录结构"
#. Tag: entry
#: Server_Configurations.xml:106
@@ -250,19 +296,19 @@
#: Server_Configurations.xml:112
#, no-c-format
msgid "Important Notes"
-msgstr ""
+msgstr "重要注意事项"
#. Tag: entry
#: Server_Configurations.xml:119
#, no-c-format
msgid "<entry>bin</entry>"
-msgstr ""
+msgstr "<entry>bin</entry>"
#. Tag: entry
#: Server_Configurations.xml:122
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Contains startup, shutdown and other system-specific scripts. Basically all the entry point JARs and start scripts included with the JBoss distribution are located in the bin directory. It also contains the configuration scripts which can be used to configure the JVM parameters."
-msgstr "包含启动、关闭和其他系统相关的脚本。基本上 JBoss 发行版本所包括的所有的入口 JAR 文件和启动脚本都位于 <filename class=\"directory\">bin</filename> 目录里。"
+msgstr "包含启动、关闭和其他系统相关的脚本。基本上 JBoss 发行版本所包括的所有的入口 JAR 文件和启动脚本都位于 <filename class=\"directory\">bin</filename> 目录里。它也包括用于配置 JVM 参数的配置脚本。"
#. Tag: entry
#: Server_Configurations.xml:129
@@ -280,25 +326,25 @@
#: Server_Configurations.xml:135
#, no-c-format
msgid "Unlike the earlier 4.x versions of the JBoss Enterprise Application Platform, the <filename>jbossall-client.jar</filename> is now a <filename>MANIFEST</filename> only JAR file. So if the client application copies over the <filename>jbossall-client.jar</filename> to its classpath, then it also has to copy over all the other jar files listed in the <filename>META-INF/MANIFEST.MF</filename> file of <filename>jbossall-client.jar</filename>. Furthermore, all these JARs, including the <filename>jbossall-client.jar</filename>, must be placed in the same folder in the client classpath."
-msgstr ""
+msgstr "不象 JBoss 企业级应用程序平台的早期 4.x 版本，<filename>jbossall-client.jar</filename> 现在是一个只使用 <filename>MANIFEST</filename> 的 JAR 文件。如果客户端程序把 <filename>jbossall-client.jar</filename> 复制到其 classpath 下，它就必须复制 <filename>jbossall-client.jar</filename> 里的 <filename>META-INF/MANIFEST.MF</filename> 列出的所有 JAR 文件。而且，所有这些 JAR 文件，包括 <filename>jbossall-client.jar</filename> 都必须置于客户端 classpath 里的相同文件夹里。"
#. Tag: entry
#: Server_Configurations.xml:140
-#, fuzzy, no-c-format
+#, no-c-format
msgid "common"
-msgstr "conf"
+msgstr "common"
#. Tag: entry
#: Server_Configurations.xml:143
#, no-c-format
msgid "This directory is meant to contains all the configurations and JAR files which are common for all the server configuration sets. The <filename>lib</filename> sub-directory within this <filename>common</filename> directory, contains all the JAR files which are common to the server configuration sets. The intention of having these JAR files in this one place, instead of the <filename>lib</filename> folder of each of the server configuration sets, is to reduce the size of the server. It also helps in maintainance; the lower the number of files to maintain, the better it is."
-msgstr ""
+msgstr "这个目录的目的是包含所有服务器配置集共用的配置和 JAR 文件。<filename>common</filename> 目录里的 <filename>lib</filename> 子目录包含所有服务器配置集共用的 JAR 文件。把这些 JAR 文件置于同一地方而不是 <filename>lib</filename> 目录的目的是减少服务器的大小。它也有助于维护，维护更少的文件自然更为容易。"
#. Tag: entry
#: Server_Configurations.xml:146
#, no-c-format
msgid "Like some of the other JBoss server configuration paths, this <filename>common</filename> and the <filename>common/lib</filename> directories are available as the system properties <filename>jboss.common.base.url</filename> (This holds the URL to <filename>JBOSS_DIST/common</filename> directory) and <filename>jboss.common.lib.url</filename> (This holds the URL to <filename>JBOSS_DIST/common/lib</filename> directory)."
-msgstr ""
+msgstr "象其他 JBoss 服务器配置路径一样，这个 <filename>common</filename> 和 <filename>common/lib</filename> 目录也可通过系统属性 <filename>jboss.common.base.url</filename>（指向 <filename>JBOSS_DIST/common</filename> 目录）和 <filename>jboss.common.lib.url</filename>（指向 <filename>JBOSS_DIST/common/lib</filename> 目录）来访问。"
#. Tag: entry
#: Server_Configurations.xml:151
@@ -308,21 +354,21 @@
#. Tag: entry
#: Server_Configurations.xml:154
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Contains the XML DTDs, schemas used in JBoss for reference (these are also a useful source of documentation on JBoss configuration specifics). There are also example JCA (Java Connector Architecture) configuration files for setting up datasources for different databases (such as MySQL, Oracle, Postgres)."
-msgstr "包含 JBoss 用来作为引用的 XML DTD（这也是 JBoss 特定配置的有用的文档）。这里也有设置不同数据库（如 MySQL、Oracle 和 Postgres）的数据源的示例 JCA（Java Connector Architecture）配置文件。"
+msgstr "包含 JBoss 用来作为引用的 XML DTD（这也是 JBoss 特定配置的有用的文档）。这里也有设置不同数据库（如 MySQL、Oracle 和 Postgres）的数据源的示例 JCA（Java Connector Architecture）配置文件。 "
#. Tag: entry
#: Server_Configurations.xml:161
#, no-c-format
msgid "<entry>lib</entry>"
-msgstr ""
+msgstr "<entry>lib</entry>"
#. Tag: entry
#: Server_Configurations.xml:164
#, no-c-format
msgid "Contains startup JARs used by JBoss. There is also an <emphasis>endorsed</emphasis> sub-directory within this lib directory, which is used as one of the Java Endorsed directories. See the <ulink url=\"http://java.sun.com/javase/6/docs/technotes/guides/standards/\">Java Endorsed Standards</ulink> for more details. Do not place your own JAR files in these directories."
-msgstr ""
+msgstr "包含 JBoss 使用的启动 JAR 文件。lib 下也有一个 <emphasis>endorsed</emphasis> 子目录，它用于 Java Endorsed 目录。更多细节请参考 <ulink url=\"http://java.sun.com/javase/6/docs/technotes/guides/standards/\">Java Endorsed Standards</ulink>。请不要把自己的 JAR 文件放在这个目录里。"
#. Tag: entry
#: Server_Configurations.xml:171
@@ -332,15 +378,15 @@
#. Tag: entry
#: Server_Configurations.xml:174
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Contains the JBoss server configuration sets. Each of the subdirectories in here is a different server configuration. JBoss ships with minimal, default, production, standard, web and all configuration sets. The subdirectories and key configuration files contained in the <literal>default</literal> configuration set are discussed in more detail in subsequent sections."
-msgstr "包含 JBoss 服务配置集。这里的每个子目录都是一个不同的服务器配置。JBoss 带有 <literal>minimal</literal>、<literal>default</literal>、<literal>production</literal> 和 <literal>all</literal> 配置集。<literal>default</literal> 配置集包含的子目录和关键的配置文件将在随后的章节里进行详细讨论。"
+msgstr "包含 JBoss 服务配置集。这里的每个子目录都是一个不同的服务器配置。JBoss 带有 minimal、default、production、standard、web 和 all 配置集。<literal>default</literal> 配置集包含的子目录和关键的配置文件将在随后的章节里进行详细讨论。"
#. Tag: para
#: Server_Configurations.xml:185
#, no-c-format
msgid "Do not remove any configuration or JRA files from the <filename>common</filename> directory location. You may add your own JAR files in the <filename>common/lib</filename> directory <emphasis>if</emphasis> those JAR files are meant to be used by all the server configuration sets. If you want the JAR files to be available for all the applications deployed in a single server configuration set (for example, the <literal>production</literal> configuration), then the best location to place these JARs is the <filename>JBOSS_DIST/server/<server-configuration-set>/lib</filename> directory."
-msgstr ""
+msgstr "请勿删除 <filename>common</filename> 目录里的任何配置或 JAR 文件。你可以在 <filename>common/lib</filename> 目录里添加自己的 JAR 文件，<emphasis>如果</emphasis>这些 JAR 文件是为所有服务器配置集使用的话。"
#. Tag: title
#: Server_Configurations.xml:191
More information about the jboss-cvs-commits
mailing list