这是来自 oracle 的javaee 教程的链接:
generate-wsdl 任务 generate-wsdl 任务运行 wscompile,它创建 WSDL 和映射文件。WSDL 文件描述 Web 服务并用于在静态存根客户端中生成客户端存根。映射文件包含与 Java 接口和 WSDL 定义之间的映射相关的信息。它是可移植的,因此任何符合 J2EE 的部署工具都可以使用此信息以及 WSDL 文件和 Java 接口来为已部署的 Web 服务生成存根和关联。
The files created in this example are MyHelloService.wsdl and mapping.xml. The generate-wsdl task runs wscompile with the following arguments:
wscompile -define -mapping build/mapping.xml -d build -nd build
-classpath build config-interface.xml
The -classpath flag instructs wscompile to read the SEI in the build directory, and the -define flag instructs wscompile to create WSDL and mapping files. The -mapping flag specifies the mapping file name. The -d and -nd flags tell the tool to write class and WSDL files to the build subdirectory.
The wscompile tool reads an interface configuration file that specifies information about the SEI. In this example, the configuration file is named config-interface.xml and contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service
name="MyHelloService"
targetNamespace="urn:Foo"
typeNamespace="urn:Foo"
packageName="helloservice">
<interface name="helloservice.HelloIF"/>
</service>
</configuration>
This configuration file tells wscompile to create a WSDL file named MyHello
Service.wsdl with the following information:
•The service name is MyHelloService.
•The WSDL target and type namespace is urn:Foo. The choice for what to use for the namespaces is up to you. The role of the namespaces is similar to the use of Java package names--to distinguish names that might otherwise conflict. For example, a company can decide that all its Java code should be in the package com.wombat.*. Similarly, it can also decide to use the namespace http://wombat.com.
•The SEI is helloservice.HelloIF.
The packageName attribute instructs wscompile to put the service classes into the helloservice package.