[jboss-cvs] JBossAS SVN: r93057 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.

Tue Sep 1 00:34:04 EDT 2009

Author: xhuang at jboss.com
Date: 2009-09-01 00:34:03 -0400 (Tue, 01 Sep 2009)
New Revision: 93057

Modified:
   projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po
Log:
update

Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po
===================================================================

--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po	2009-09-01 03:30:23 UTC (rev 93056)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/Web_Services.po	2009-09-01 04:34:03 UTC (rev 93057)
@@ -9,7 +9,7 @@
 "Project-Id-Version: Web_Services\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-08-28 20:04+1000\n"
+"PO-Revision-Date: 2009-09-01 14:33+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -335,7 +335,7 @@
 #: Web_Services.xml:73
 #, no-c-format
 msgid "SOAP encodeding style is defined by the infamous <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383512\">chapter 5</ulink> of the <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/\">SOAP-1.1</ulink> specification. It has inherent interoperability issues that cannot be fixed. The <ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html\">Basic Profile-1.0</ulink> prohibits this encoding style in <ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072\">4.1.7 SOAP encodingStyle Attribute</ulink>. JBossWS has basic support for rpc/encoded that is provided as is for simple interop scenarios with SOAP stacks that do not support literal encoding. Specifically, JBossWS does not support:-"
-msgstr ""
+msgstr "SOAP 编码风格是由 <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/\">SOAP-1.1</ulink> 规格的 <ulink url=\"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383512\">chapter 5</ulink> 定义的。它天生具有互用性的问题而无法解决。<ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html\">Basic Profile-1.0</ulink> 禁止 <ulink url=\"http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072\">4.1.7 SOAP encodingStyle Attribute</ulink> 里的这个编码风格。JBossWS 具有对 rpc/encoded 的基本支持，它作为简单的带有不支持 literal 编码的 SOAP 栈的互用模式。特别是，JBossWS 不支持："
 
 #. Tag: para
 #: Web_Services.xml:76
@@ -2297,13 +2297,13 @@
 #: Web_Services.xml:799
 #, no-c-format
 msgid "This will internally invoke <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink>, which will generate the WSDL. If deployment was successful, and you are using the default settings, it should be available here: <ulink url=\"http://localhost:8080/echo/Echo?wsdl\">http://localhost:8080/echo/Echo?wsdl</ulink>"
-msgstr ""
+msgstr "这将在内部调用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink>，它会生成 WSDL。如果部署成功，且你正在使用缺省设置，它应该可以这样访问：<ulink url=\"http://localhost:8080/echo/Echo?wsdl\">http://localhost:8080/echo/Echo?wsdl</ulink>。"
 
 #. Tag: para
 #: Web_Services.xml:802
 #, no-c-format
 msgid "For a portable JAX-WS deployment, the wrapper classes generated earlier could be added to the deployment."
-msgstr ""
+msgstr "对于可移植的 JAX-WS 部署，早前生成的 wrapper 类可以添加到部署里："
 
 #. Tag: title
 #: Web_Services.xml:808
@@ -2327,7 +2327,7 @@
 #: Web_Services.xml:820
 #, no-c-format
 msgid "Using the WSDL file from the bottom-up example, a new Java implementation that adheres to this service can be generated. The \"-k\" option is passed to <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink> to preserve the Java source files that are generated, instead of providing just classes:"
-msgstr ""
+msgstr "使用 bottom-up 例子里的 WSDL 文件，就可以生成依附于这个服务的新的 Java 实现。\"-k\" 选项被传递给 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume\">wsconsume</ulink> 以保存所生成的 Java 源文件，而不是只提供类："
 
 #. Tag: programlisting
 #: Web_Services.xml:823
@@ -2347,6 +2347,19 @@
 "echo/ObjectFactory.java\n"
 "echo/package-info.java"
 msgstr ""
+"$ wsconsume -k EchoService.wsdl\n"
+"echo/Echo.java\n"
+"echo/EchoResponse.java\n"
+"echo/EchoService.java\n"
+"echo/Echo_Type.java\n"
+"echo/ObjectFactory.java\n"
+"echo/package-info.java\n"
+"echo/Echo.java\n"
+"echo/EchoResponse.java\n"
+"echo/EchoService.java\n"
+"echo/Echo_Type.java\n"
+"echo/ObjectFactory.java\n"
+"echo/package-info.java"
 
 #. Tag: para
 #: Web_Services.xml:824
@@ -2520,7 +2533,7 @@
 #: Web_Services.xml:932
 #, no-c-format
 msgid "Let&#39;s repeat the process of the top-down section, although using the deployed WSDL, instead of the one generated offline by <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink>. The reason why we do this is just to get the right value for soap:address. This value must be computed at deploy time, since it is based on container configuration specifics. You could of course edit the WSDL file yourself, although you need to ensure that the path is correct."
-msgstr ""
+msgstr "让我们重复 top-down 章节里的过程，虽然这是通过所部署的 WSDL 而不是用 <ulink url=\"http://jbws.dyndns.org/mediawiki/index.php?title=Wsprovide\">wsprovide</ulink> 脱线生成的那个。我们要这样做的原因是获取正确的 soap:address 值。既然这个值是基于容器配置的，它必须在部署时进行计算。你当然可以自己编辑 WSDL 文件，但你需要确保路径是正确的。"
 
 #. Tag: para
 #: Web_Services.xml:935
@@ -2592,7 +2605,7 @@
 #: Web_Services.xml:947
 #, no-c-format
 msgid "The one class that was not examined in the top-down section, was EchoService.java. Notice how it stores the location the WSDL was obtained from."
-msgstr ""
+msgstr "top-down 部分没有讨论的类是 EchoService.java。请注意它是怎样存储 WSDL 所处的位置的。"
 
 #. Tag: programlisting
 #: Web_Services.xml:950
@@ -2649,7 +2662,7 @@
 #: Web_Services.xml:962
 #, no-c-format
 msgid "All that is left to do, is write and compile the client:"
-msgstr ""
+msgstr "剩下的就是编写和编译客户端："
 
 #. Tag: programlisting
 #: Web_Services.xml:965


