WSDL to Java
wsdl2java - takes a WSDL document and generates fully annotated Java code from which to implement a service.
wsdl2java takes a WSDL document and generates fully annotated Java code from which to implement a service. The WSDL document must have a valid
portType element, but it does not need to contain a binding element or a service element. Using the optional arguments you can customize the generated code. In addition, wsdl2java can generate an Ant based makefile to build your application.
The options used to validate WSDL file are reviewed in the following table.
Displays the online help for this utility and exits.
Specifies the frontend. Default is JAXWS. Currently supports only JAXWS frontend and a "jaxws21" frontend to generate JAX-WS 2.1 compliant code.
Specifies the databinding. Default is jaxb. Currently supports jaxb, xmlbeans, sdo (sdo-static and sdo-dynamic), and jibx.
Specifies the wsdl version .Default is WSDL1.1. Currently suppports only WSDL1.1 version.
Specifies zero, or more, package names to use for the generated code. Optionally specifies the WSDL namespace to package name mapping.
The WSDL service name to use for the generated code.
Specifies JAXWS or JAXB binding files or XMLBeans context files. Use multiple -b flags to specify multiple entries.
Specify catalog file to map the imported wsdl/schema
Specifies the directory into which the generated code files are written.
Compiles generated Java files.
Specifies the directory into which the compiled class files are written.
Generates starting point code for a client mainline.
Generates the jar file which contains all the client classes and wsdl;the specified wsdlLocation won't work when the -clientJar is defined.
Generates starting point code for a server mainline.
Generates starting point code for an implementation object.
Generates all starting point code: types, service proxy, service interface, server mainline, client mainline, implementation object, and an Ant
Specify to generate an Ant
Automatically resolve naming conflicts without requiring the use of binding customizations.
Specifies that default values are generated for the impl and client. You can also provide a custom default value provider. The default provider is
Ignore the specified WSDL schema namespace when generating code. This option may be specified multiple times. Also, optionally specifies the Java package name used by types described in the excluded namespace(s).
Enables or disables processing of implicit SOAP headers (i.e. SOAP headers defined in the wsdl:binding but not wsdl:portType section.) Processing the SOAP headers requires the SOAP binding jars available on the classpath which was not the default in CXF 2.4.x and older. You may need to add a dependency to cxf-rt-binding-soap for this flag to work. Default is false.
Enables or disables the loading of the default namespace package name mapping. Default is true and http://www.w3.org/2005/08/addressing=org.apache.cxf.ws.addressing namespace package mapping will be enabled.
Enables or disables the loading of the default excludes namespace mapping. Default is true.
Enables validating the WSDL before generating the code.
Specifies that the code generator will not overwrite any preexisting files. You will be responsible for resolving any resulting compilation issues.
Specifies the value of the @WebServiceClient annotation's wsdlLocation property.
Specifies a comma separated list of arguments that are passed directly to the XJC processor when using the JAXB databinding. A list of available XJC plugins can be obtained using
For compatibility with CXF 2.0, this flag directs the code generator to generate the older CXF proprietary WS-Addressing types instead of the JAX-WS 2.1 compliant WS-Addressing types.
Displays the version number for the tool.
Displays comments during the code generation process.
Suppresses comments during the code generation process.
superclass for fault beans generated from wsdl:fault elements (defaults to java.lang.Exception)
Used with -autoNameResolution, defines a class names for wsdl-to-java not to use when generating classes. Use this option multiple times for multiple classes.
(or -aer) If true, disregards the rule given in section 126.96.36.199(v) of the JAX-WS 2.2 specification disallowing element references when using wrapper-style mapping.
List of subsequently generated Java class methods to allow for client-side asynchronous calls, similar to enableAsyncMapping in a JAX-WS binding file.
List of subsequently generated Java class methods to have wrapper style (see below), similar to enableWrapperStyle in JAX-WS binding file.
List of subsequently generated Java class methods to enable mime:content mapping, similar to enableMIMEContent in JAX-WS binding file.
How to generate suid of fault exceptions. Use NONE, TIMESTAMP, FQCN, or a specific number. Default is NONE.
Adds the @Generated annotation to classes generated.
|Suppresses writing the current timestamp in the generated file (since CXF version 3.2.2)|
|-maxExtensionStackDepth <int>||The maximum stack depth allowed when parsing schema extensions. The default is 5. (since CXF 3.3.4 )|
The path and name of the WSDL file to use in generating the code.
You must specify the absolute or relative path to the WSDL document as the last argument.
wsdl2java -p com.mycompany.greeting Greeting.wsdl
wsdl2java -client HelloWorld.wsdl
Using wsdl2java with Ant
The wsdl2java command can be wrapped inside an Ant target as shown below:
Make sure you set the "fork=true" attribute for the <java/> task as shown above. Also, remember to keep each word or flag within the command line options in its own <arg/> element (e.g., do not use <arg value="-d src"/>, but split them up into two <arg/> elements as done here.)
Although we would recommend using Maven, see the antbuild sample in the CXF distribution for an example of using Ant to create a CXF project.
The default JAX-WS frontend created by wsdl2java can be customized by using a customization binding file. For an example, see the async_binding.xml file in samples/jaxws_async – if specified when running wsdl2java, it will generate asynchronous methods in the SEI.
Q: What if I want to change the generated SEI name?
A: We don't have a command-line option to do this, but you can have a binding file like the following snippet to achieve this goal
Q: How do I pass the binding file to wsdl2java?
A: If you are using wsdl2java via command line tool:
wsdl2java HelloWorld.wsdl -b my_binding.xml
For Ant, follow the example above on how to add "-b" and "my_binding.xml" as arg elements.
For Maven see cxf-codegen-plugin
Q: How to map xsd:dateTime to java.util.Date?
Well, people don't like the XMLGregorianCalendar which is the default mapping from the xsd:dateTime (xsd:time and xsd:date as well),
We can use the jaxws customization to change the default mapping, here are some sample binding files
If you have schema inside the wsdl, here is the binding file you can use:
This requires an additional dependency:
If you want to use java.util.Calendar, just change the org.apache.cxf.xjc.runtime.DataTypeAdapter to javax.xml.bind.DatatypeConverter, and change the name value to "java.util.Calendar"
If your schema is out of wsdl, here is an example you can try:
Q: How can I switch my generated web service method calls from wrapper style to non wrapper-style (or vice-versa)?
A: Create an external binding file and set the value of <enableWrapperStyle/> to true or false as desired:
Alternatively you can embed this instruction within the WSDL file directly, as the immediate child of the wsdl:portType:
Note: The meaning of "wrapper-style" and "non-wrapper style" as defined in the JAX-WS 2.1 specification can be counterintuitive. Wrapper-style indicates that each data element within the request message gets its own Java parameter, while non-wrapper style means that a single Java object containing all the data elements serves as the lone parameter to the web service method call. (See Figure 2.2 of the specification for an example.) Also, note the wrapper style is not always available, the WSDL criteria specified in Section 188.8.131.52 ("Wrapper Style") of the specification must be met or only non-wrapper style will be generated.
Q: What else can I change with the JAXWS customization binding file?
A: You can find the full list of customization items in Chapter 8 of the JAX-WS Specification.