Skip to main content

jaxb2-maven-plugin to generate java code from XSD schema

In this tutorial I will show how to generate the Java source code from XSD schema. I will use jaxb2-maven-plugin to generate the code using XSD file which will be declared in pom.xml to make it part of build, so when maven build is executed it will generate the java code using XSD. Class generation can be controlled in plugin configuration.

Maven changes (pom.xml)

Include below plugin in your pom.xml. Here we have done some configuration under configuration section as given below.
schemaDirectory: This is the directory where I keep my schema (XSD file).
outputDirectory: This is the java source location where I want to generate the Java files. If it is not given then by default it will be generate inside target folder.
clearOutputDir: If this property is true then it will generate the classes on each build otherwise it will generate only if output directory is empty.
<plugin>
 <groupId>org.codehaus.mojo</groupId>
 <artifactId>jaxb2-maven-plugin</artifactId>
 <version>1.6</version>
 <executions>
    <execution>
     <id>xjc</id>
     <goals>
        <goal>xjc</goal>
     </goals>
    </execution>
 </executions>
 <configuration>
    <schemaDirectory>${project.basedir}/src/main/resources/schema</schemaDirectory>
    <outputDirectory>${project.basedir}/src/main/java</outputDirectory>
    <clearOutputDir>false</clearOutputDir>
 </configuration>
</plugin>

XSD Schema (employee.xsd)

Below is the XSD schema which will be used to generate the Java class.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://myexample.com/employee"
targetNamespace="http://myexample.com/employee">
 <xs:complexType name="employee">
  <xs:sequence>
   <xs:element name="name" type="xs:string"/>
   <xs:element name="age" type="xs:int"/>
   <xs:element name="organization" type="xs:string"/>
   <xs:element name="salary" type="xs:decimal"/>
  </xs:sequence>
 </xs:complexType>
</xs:schema>
XSD location is as given below in my application.
xsd location

Generating Java classes

After setting up the above code and configuration, we can run the maven build by executing "men clean install". It will generate the Java classes using the XSD schema. Below is the generated code package structure after the build execution.
generated classes

Below is the snap of code from generated classes. Getters/Setters are also generated but not included in example.
  • Employee.java
  • @XmlAccessorType(XmlAccessType.FIELD)
     @XmlType(name = "employee", propOrder = {
         "name",
         "age",
         "organization",
         "salary"
     })
    
     public class Employee {
         @XmlElement(required = true)
         protected String name;
    
         protected int age;
    
         @XmlElement(required = true)
         protected String organization;
    
         @XmlElement(required = true)
         protected BigDecimal salary;
    
  • ObjectFactory.java
  • @XmlRegistry
     public class ObjectFactory {
         /**
          * Create a new ObjectFactory that can be used to create new instances of schema derived classes for package: com.myexample.employee
          * 
          */
         public ObjectFactory() {
    
         } 
    
         /**
          * Create an instance of {@link Employee }
          * 
          */
         public Employee createEmployee() {
             return new Employee();
         } 
     }
    
  • package-info.java
  • @javax.xml.bind.annotation.XmlSchema(namespace = "http://myexample.com/employee")
    package com.myexample.employee;
    
That's all. Usually you may have a need to generate the class this way when you are creating some SOAP service client or you can use it to just create the Java POJO classes also.

You may be interested in my other post on generating Java classes using annotation processor.
https://www.thetechnojournals.com/2019/12/annotation-processor-to-generate-dto.html

Comments

  1. Nice blog ! Thank you so much for compiling such a great article! Clearly, this is an excellent post. I appreciate the insightful and useful information you have offered here. custom erp software

    ReplyDelete
  2. 4398CCEC12JacquelineBDEE446DA726 November 2024 at 15:22

    A2CB785C1E
    telegram show

    ReplyDelete
  3. D3A7F3D4B5
    Printing techniques continue to evolve, offering more vibrant and durable results for various designs. One popular method gaining popularity is DTF TRANSFERS, which allows for high-quality, full-color images to be transferred onto fabrics with ease. Many entrepreneurs and artists prefer this method for its versatility and excellent detail reproduction. Whether for custom apparel or promotional items, DTF TRANSFERS provide a reliable solution for achieving professional-grade results.

    ReplyDelete

  4. Aşk, insan hayatında en derin duygulardan biridir ve bu duyguyu anlamak için farklı bakış açıları sunan birçok eser bulunuyor. Bu eserler arasında aşk kitapları, okuyuculara sevgi ve tutkunun farklı yönlerini keşfetme fırsatı verir. Her biri, kalplerde iz bırakacak hikayeler ve duygusal yolculuklar sunar. Bu nedenle, sevgiye dair içgörü kazanmak isteyenler için bu kitaplar oldukça değerli olabilir.

    ReplyDelete

Post a Comment

Popular Posts

Setting up kerberos in Mac OS X

Kerberos in MAC OS X Kerberos authentication allows the computers in same domain network to authenticate certain services with prompting the user for credentials. MAC OS X comes with Heimdal Kerberos which is an alternate implementation of the kerberos and uses LDAP as identity management database. Here we are going to learn how to setup a kerberos on MAC OS X which we will configure latter in our application. Installing Kerberos In MAC we can use Homebrew for installing any software package. Homebrew makes it very easy to install the kerberos by just executing a simple command as given below. brew install krb5 Once installation is complete, we need to set the below export commands in user's profile which will make the kerberos utility commands and compiler available to execute from anywhere. Open user's bash profile: vi ~/.bash_profile Add below lines: export PATH=/usr/local/opt/krb5/bin:$PATH export PATH=/usr/local/opt/krb5/sbin:$PATH export LDFLAGS=...

Multiple data source with Spring boot, batch and cloud task

Here we will see how we can configure different datasource for application and batch. By default, Spring batch stores the job details and execution details in database. If separate data source is not configured for spring batch then it will use the available data source in your application if configured and create batch related tables there. Which may be the unwanted burden on application database and we would like to configure separate database for spring batch. To overcome this situation we will configure the different datasource for spring batch using in-memory database, since we don't want to store batch job details permanently. Other thing is the configuration of  spring cloud task in case of multiple datasource and it must point to the same data source which is pointed by spring batch. In below sections, we will se how to configure application, batch and cloud task related data sources. Application Data Source Define the data source in application properties or yml con...

Microservices with Spring Boot - complete tutorial

In this tutorial we are going to learn how to develop microservices using spring boot with examples. Main focus of this tutorial is on learning by doing hands-on. Before hands-on we will first understand what is microservices and related terminologies like DDD, 12-Factors App, Dev Ops. What is a Microservice In simple terms microservice is a piece of software which has a single responsibility and can be developed, tested & deployed independently. In microservices we focus on developing independent and single fully functioning modules. Opposite to microservice, with monolithic application it focuses on all the functionality or modules in a single application. So when any changes required to monolithic application it has to deploy and test the complete application while with microservice it has to develop and deploy only affected component which is a small service. It saves lot of development and deployment time in a large application. It's basically an architectural style ...