cxf &   Leave a comment

WSDL to Java


wsdl2java -fe <frontend name>* -db <data binding name>* -wv <[wsdl version]>*
-p <[wsdl namespace =]Package Name>* -sn <service-name> -b <binding-name>*
-catalog <catalog-file-name> -d <output-directory> -compile
-classdir <compile-classes-directory> -impl -server -client -all
-autoNameResolution -defaultValues<=class name for DefaultValueProvider> -ant
-nexclude <schema namespace [= java packagename]>*  -exsh <(true, false)>
-dns <(true, false)> -dex <(true, false)> -validate -keep
-wsdlLocation <wsdlLocation attribute> -xjc<xjc arguments> -noAddressBinding -h
-v -verbose -quiet <wsdlurl>


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.


wsdl2java HelloWorld.wsdl

wsdl2java -p com.iona.greeting Greeting.wsdl

wsdl2java -client HelloWorld.wsdl

(See below for usage with Apache Ant and Maven.)


The arguments used to manage the code generation process are reviewed in the following table.

Option Interpretation
-? Displays the online help for this utility.
-help Displays the online help for this utility.
-h Displays the online help for this utility.
-fe frontend-name Specifies the frontend. Default is JAXWS. Currently supports only JAXWS frontend.
-db databinding-name Specifies the databinding. Default is jaxb. Currently supports jaxb and xmlbeans databinding. sdo (sdo-static and sdo-dynamic) supported in 2.3.
-wv wsdl-version Specifies the wsdl version .Default is WSDL1.1. Currently suppports only WSDL1.1 version.
-p [ wsdl-namespace= ] PackageName Specifies zero, or more, package names to use for the generated code. Optionally specifies the WSDL namespace to package name mapping.
-sn service-name The WSDL service name to use for the generated code.
-b binding-name Specifies JAXWS or JAXB binding files or XMLBeans context files. Use multiple -b flags to specify multiple entries.
-catalog catalog-file-name Specify catalog file to map the imported wsdl/schema
-d output-directory Specifies the directory into which the generated code files are written.
-compile Compiles generated Java files.
-classdir complile-class-dir Specifies the directory into which the compiled class files are written.
-client Generates starting point code for a client mainline.
-server Generates starting point code for a server mainline.
-impl Generates starting point code for an implementation object.
-all Generates all starting point code: types, service proxy, service interface, server mainline, client mainline, implementation object, and an Ant build.xml file.
-ant Generates the Ant build.xml file.
-autoNameResolution Automatically resolve naming conflicts without requiring the use of binding customizations.
-defaultValues=[DefaultValueProvider impl] Specifies that default values are generated for the impl and client. You can also provide a custom default value provider. The default provider is RandomValueProvider
-nexclude schema-namespace [=java-packagename] 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).
-exsh (true/false) Enables or disables processing of implicit SOAP headers (i.e. SOAP headers defined in the wsdl:binding but not wsdl:portType section.) Default is false.
-dns (true/false) Enables or disables the loading of the default namespace package name mapping. Default is true and namespace package mapping will be enabled.
-dex (true/false) Enables or disables the loading of the default excludes namespace mapping. Default is true.
-validate Enables validating the WSDL before generating the code.
-keep Specifies that the code generator will not overwrite any preexisting files. You will be responsible for resolving any resulting compilation issues.
-wsdlLocation wsdlLocation Specifies the value of the @WebServiceClient annotation’s wsdlLocation property.
-xjc<xjc args> 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 -xjc-X.
-noAddressBinding 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.
-v Displays the version number for the tool.
-verbose Displays comments during the code generation process.
-quiet Suppresses comments during the code generation process.
wsdlfile 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.

Using wsdl2java with Ant

CXF (as of 2.1) includes ant tasks. See Ant Tasks (2.0.x and 2.1.x). It is also possible to invoke the tools using an ordinary ant <java> task, as follows:

The wsdl2java command can be wrapped inside an Ant target as shown below:

<?xml version="1.0"?>
<project name="cxf wsdl2java" basedir=".">
   <property name="cxf.home" location ="/usr/myapps/cxf-2.0.1"/>

   <path id="cxf.classpath">
      <fileset dir="${cxf.home}/lib">
         <include name="*.jar"/>

   <target name="cxfWSDLToJava">
      <java classname="" fork="true">
         <arg value="-client"/>
         <arg value="-d"/>
         <arg value="src"/>
         <arg value="MyWSDL.wsdl"/>
            <path refid="cxf.classpath"/>

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.)

JAXWS Customization

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

    <bindings node="wsdl:definitions/wsdl:portType">
	<class name="GreeterSEI"/>

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:

<jaxws:bindings wsdlLocation="YOUR_WSDL_LOCATION"
  <jaxws:bindings  node="wsdl:definitions/wsdl:types/xs:schema[@targetNamespace='THE_NAMESPACE_OF_YOUR_SCHEMA']">
      <jxb:globalBindings xmlns:jxb="" xmlns:xs="">
        <jxb:javaType name="java.util.Date" xmlType="xs:dateTime"

If you want to use java.util.Calendar, just change the 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:

<jxb:bindings version="2.0"
  <jxb:bindings schemaLocation="file:<path><name>.xsd" node="/xs:schema">
    <jxb:globalBindings xmlns:jxb="" xmlns:xs="">
      <jxb:javaType name="java.util.Date" xmlType="xs:dateTime"

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:

<wsdl:portType name="MyWebServicePortType">
    <jaxws:bindings xmlns:jaxws="">
        ... other binding settings if needed ...
    <wsdl:operation name="sayHello">

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 (“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.

Using maven to generate java code from WSDL

see cxf-codegen-plugin

package test;


import java.util.ArrayList;

import java.util.List;

import java.util.Map;

import javax.xml.namespace.QName;


import org.apache.cxf.headers.Header;

import org.apache.cxf.jaxb.JAXBDataBinding;

import org.w3c.dom.Element;

import stub.LoginResult;

import stub.Query;

import stub.QueryResult;

import stub.SObject;

import stub.SessionHeader;

import stub.SforceService;

import stub.Soap;

public class Test {

public static void main(String[] args) throws Exception{

String path = “/ctc.wsdl”;

URL url = Test.class.getResource(path);

if (url == null) {

throw new RuntimeException(“cannot find ctc.wsdl file at classpath..”);


SforceService service = new SforceService(url, new QName(

““, “SforceService”));

Soap port = service.getSoap();

System.out.println(“Invoking login…”);

String userName = ““;

String password = “bavarian1PVFCx7mm4WcHUp1KWilTE3Jlz”;

// Login to get new endpoint and session

LoginResult loginResult = port.login(userName, password);

// Setting new endpoint

System.out.println(“ServerUrl=” +loginResult.getServerUrl());

Map<String, Object> requestContext = ((BindingProvider)port).getRequestContext();

requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, loginResult.getServerUrl());

// Setting new session

System.out.println(“SessionId=” + loginResult.getSessionId());

SessionHeader sh = new SessionHeader();


List<Header> headers = new ArrayList<Header>();

// Header dummyHeader = new Header(new QName(““, “SessionHeader”), “SessionHeader”,

//                                 new JAXBDataBinding(stub.SessionHeader.class));

headers.add(new Header(new QName(““, “SessionHeader”), sh,new JAXBDataBinding(stub.SessionHeader.class)));

// ((BindingProvider)port).getRequestContext().put(Header.HEADER_LIST, headers);

requestContext.put(Header.HEADER_LIST, headers);


Query query = new Query();

QueryResult queryResult = port.query(“select Name from Contact limit 5″);

List<SObject> list = queryResult.getRecords();

for(SObject so:list){

List<Object> objs = so.getAny();

for(Object obj:objs){

Element ele = (Element) obj;

String name = ele.getLocalName();

String value = ele.getFirstChild().getNodeValue();

System.out.println(name+” : “+value);







Posted 2010年11月10日 by gw8310 in java, salesforce


Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / 更改 )

Twitter picture

You are commenting using your Twitter account. Log Out / 更改 )

Facebook photo

You are commenting using your Facebook account. Log Out / 更改 )

Google+ photo

You are commenting using your Google+ account. Log Out / 更改 )

Connecting to %s

%d 博主赞过: