WSDL Client Stub Generation (JAVA, Maven, Apache CXF)

To consume WSDL-based web service. The easiest way to do is to generate client stub to make the service call.

Apache CXF is one service framework for web services. Details could be found in official web-site:
http://cxf.apache.org/docs/overview.html

We use maven to manage client stub code, to integrate Apache CXF, we can add dependency:

<properties>
 <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
 <cxf.version>2.7.5</cxf.version>
</properties>

<dependencies>
 <dependency>
   <groupId>junit</groupId>
   <artifactId>junit</artifactId>
   <version>3.8.1</version>
   <scope>test</scope>
 </dependency>
 <dependency>
   <groupId>org.apache.cxf</groupId>
   <artifactId>apache-cxf</artifactId>
   <version>${cxf.version}</version>
   <type>pom</type>
 </dependency>
</dependencies>

To generate client stub, we can use the 'cxf-codegen-plugin':

<plugin>
 <groupId>org.apache.cxf</groupId>
 <artifactId>cxf-codegen-plugin</artifactId>
 <version>${cxf.version}</version>
 <executions>
   <execution>
     <id>generate-sources</id>
     <phase>generate-sources</phase>
     <configuration>
       <sourceRoot>${basedir}/src/main/code</sourceRoot>
       <wsdlOptions>
         <wsdlOption>
           <wsdl>WSDL_URL/RELATIVE_PATH(e.g src/main/resources/wsdl/XXX.wsdl)</wsdl>

           <extraargs>
             <extraarg>-impl</extraarg>
             <extraarg>-verbose</extraarg>
             <extraarg>-client</extraarg>
             <extraarg>-p</extraarg>
             <extraarg>com.test.service.message</extraarg>
             <!-- <extraarg>-p</extraarg> <extraarg>SOME_NAMING_SPACE1=com.test.service.message.space1</extraarg>

          <extraarg>-p</extraarg> <extraarg>SOME_NAMING_SPACE2=com.test.service.message.space2</extraarg> 
          -->
           </extraargs>
         </wsdlOption>
         <wsdlOption>
           <wsdl>WSDL_URL/RELATIVE_PATH(e.g src/main/resources/wsdl/XXX2.wsdl)</wsdl>
           <extraargs>
             <extraarg>-impl</extraarg>
             <extraarg>-verbose</extraarg>
             <extraarg>-client</extraarg>
             <extraarg>-p</extraarg>
             <extraarg>com.test.service.directory</extraarg>
           </extraargs>
         </wsdlOption>
       </wsdlOptions>
     </configuration>
     <goals>
       <goal>wsdl2java</goal>
     </goals>
   </execution>
 </executions>
</plugin>

"<sourceRoot>${basedir}/src/main/code</sourceRoot>" =>Specify where to put the generated code. Instead of using this, in each "<wsdl>", can use extra args "-d" "path" to specify path for each wsdl. "<extraarg>-p</extraarg>  <extraarg>com.test.service.message</extraarg>" => Specify the package name of the generated code. In this case, if not specified, if there are multiple naming space in the wsdl, there may be multiple packages. Sometimes, it's hard to manage. So sometimes we may want to merge all the classes into one package and have one 'ObjectFactory'.
BUT I have one issue left over here, which is although I specify the package name in this way, other packages will still be generated and kept under the directory that I specified. So the result will be, in addition to the two package that I specified, other default packages will also be generated. Which is not what I want. 
If anyone knows how to update this, please leave a comment. Thank you very much!
So, because of that issue, if I want to generate a jar file that contains only two packages that I specify, I need to assemble the jar file myself. Because the plug cxf-codegen-plugin executes in phase generate-source and all the code it generates will be treated as compile source.
SO in pom.xml. I need to specify:

<plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-assembly-plugin</artifactId>
 <version>2.3</version>
 <executions>
   <execution>
     <id>assembly</id>
     <phase>package</phase>
     <goals>
       <goal>single</goal>
     </goals>
     <configuration>
       <finalName>${project.artifactId}</finalName>
       <appendAssemblyId>true</appendAssemblyId>
       <descriptors>
         <descriptor>src/main/assembly/service-jar.xml</descriptor>
       </descriptors>
     </configuration>
   </execution>
 </executions>
</plugin>

service-jar.xml:

<assembly

  xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd">
  <id>self-gen</id>
  <formats>
      <format>jar</format>
  </formats>
  <includeBaseDirectory>false</includeBaseDirectory>
  <dependencySets>
      <dependencySet>
          <outputDirectory>/</outputDirectory>
          <useProjectArtifact>true</useProjectArtifact>
          <includes>
              <include>${project.groupId}:${project.artifactId}</include>
          </includes>
          <unpack>true</unpack>
          <unpackOptions>
              <includes>
                      <include>com/test/service/message/*</include>
                      <include>com/test/service/directory/*</include>
              </includes>
          </unpackOptions>
          <scope>runtime</scope>
      </dependencySet>
  </dependencySets>
</assembly>

In this case, after we run "mvn clean package", we can get two jars. We use the target jar with classifier 'self-gen'.
Then we can write client code based on this jar file.  The client code which makes API calls could refer to the client java class that automatically generated.