This JAXB plugin utilises the power of @XmlElementWrapper annotation. Originally xjc trends to create wrapper classes which are the containers for collections. This plugin goes through all properties to find ones which can be represented in the model in more optimal way.
If you like this plugin, please give in a star in GutHub! Report the issues to bugtracker or use jaxb-xew-plugin tag on StackOverflow.
To illustrate the problem let's take the following XSD:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified">
<xsd:element name="order">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="items" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="items">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="item" type="xsd:string" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>From this XSD by default xjc will generate two classes:
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "", propOrder = { "items" })
@XmlRootElement(name = "order")
public class Order {
@XmlElement(required = true)
protected Items items;
public Items getItems() {
return items;
}
public void setItems(Items value) {
this.items = value;
}
}and
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "", propOrder = { "item" })
@XmlRootElement(name = "items")
public class Items {
@XmlElement(required = true)
protected List<String> item;
public List<String> getItem() {
if (item == null) {
item = new ArrayList<String>();
}
return this.item;
}
}So to access a particular item one need to write a but clumsy code order.getItems().getItems().get(itemIndex). The solution is to use @XmlElementWrapper which cures exactly this case. The result will be only one class with direct access to items:
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "", propOrder = { "items" })
@XmlRootElement(name = "order")
public class Order {
@XmlElementWrapper(name = "items", required = true)
@XmlElement(name = "item")
protected List<String> items;
public List<String> getItems() {
if (items == null) {
items = new ArrayList<String>();
}
return items;
}
public void setItems(List<String> items) {
this.items = items;
}
}After this transformation of Order class, the class Items is not needed anymore and can be removed from the model.
The plugin is used together with the xjc from the command line or from an Ant task or via maven-jaxb2-plugin.
The following options are applicable for plugin:
| Option | Comment |
|---|---|
| -Xxew | Activate the XML Element Wrapper plugin |
| -Xxew:control filename | Specify a file with classes to exclude/include/keep in the compilation. |
| -Xxew:summary filename | Specify a filename to contain summary information for the compilation. |
| -Xxew:collection FQCN | Specify the class name of the collection instance to use. |
| -Xxew:collectionInterface FQCN | Specify the class name of the collection interface to use. |
| -Xxew:instantiate [early|lazy|none] | Specify when the collection class should be instantiated: when class is created / when property is accessed from getter / not instantiated at all. |
| -Xxew:plural | Apply plural form to collection property (e.g. turn "item" into "items"). |
This file allows to control how substituted classes (candidates) are handled. Each control file line specifies a fully qualified candidate class name or regex pattern (provided between slashes /.../) plus mode associated with it.
The following control modes are available:
| exclude | Given candidate class is excluded from becoming candidate for substitution and will not be removed from the model. |
| include | Given candidate class is not excluded from becoming candidate for substitution. Used usually in conjunction with exclude to include back a part of the exclusion space. |
| keep | Given candidate class is not removed (kept) from model. Substitutions are nevertheless made. |
The rules are attempted for match from top to bottom, so the last matched rule prevails.
Example of control file:
# RegEx to exclude all classes in given package and subpackages:
/org\.company\..*/=exclude
# Specific class marked for exclusion is now included back:
org.company.Processor=include
Empty lines or lines started with # (comment) are ignored. See also inner-element-control.txt and other control files in test suit.
With JAXB customization it is possible to pass the same options as via XJC arguments. Here is the example with all global options enumerated:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema
jaxb:version="3.0"
xmlns:jaxb="https://jakarta.ee/xml/ns/jaxb"
xmlns:xew="http://github.com/jaxb-xew-plugin"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
jaxb:extensionBindingPrefixes="xew"
elementFormDefault="qualified"
>
<xsd:annotation>
<xsd:appinfo>
<xew:xew
control="control.txt" summary="summary.txt"
collection="java.util.LinkedHashSet" collectionInterface="java.util.Collection"
instantiate="early" plural="true" />
</xsd:appinfo>
</xsd:annotation>
...
</xsd:schema>XJC arguments are overridden with JAXB global customizations, which are overridden with JAXB type customizations, which are overridden with JAXB field customizations. Per-type and per-field customizations cannot override control and summary configuration options, but have additionally annotate option, which if set to false, disables annotation/replacement of the particular field or all fields of the type/class (see element-with-customization.xsd example for global, per-type and per-field customization). Note that in contrast to exclude mode in control file, this option controls the behaviour for the particular field (or all fields of a type/class) which are being annotated with @XmlElementWrapper, but not the types/classes which are used for substitution (candidate classes). Example of per-field JXB file:
<?xml version="1.0" encoding="UTF-8"?>
<jaxb:bindings
xmlns:jaxb="https://jakarta.ee/xml/ns/jaxb"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xew="http://github.com/jaxb-xew-plugin"
jaxb:extensionBindingPrefixes="xew"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" version="2.1">
<jaxb:bindings node="xsd:complexType[@name='container']">
<jaxb:bindings node=".//xsd:element[@name='items']">
<xew:xew annotate="false" />
</jaxb:bindings>
</jaxb:bindings>
</jaxb:bindings>First you need to download the plugin jar (for example, from Maven repository) and put it to your project libs folder together with other dependencies.
To use the plugin from Ant you will need something like the following in your build file:
<?xml version="1.0" encoding="UTF-8"?>
<project name="SunlightDataService" default="build" basedir=".">
<path id="runtime.classpath">
<fileset dir="libs">
<include name="jaxb-xjc-3.0.1.jar" />
<include name="jaxb-api-2.2.11.jar" />
<include name="jaxb-core-3.0.1.jar" />
<include name="commons-logging-1.2.jar" />
</fileset>
</path>
<path id="xjc.classpath">
<fileset dir="libs">
<include name="jaxb2-basics-tools-3.0.0.jar" />
<include name="jaxb-xew-plugin-2.1.jar" />
</fileset>
</path>
<taskdef name="xjc" classname="com.sun.tools.xjc.XJCTask">
<classpath>
<path refid="runtime.classpath" />
</classpath>
</taskdef>
<target name="build">
<mkdir dir="target" />
<xjc destdir="target" schema="xsd/test.xsd" package="org.mycompany" extension="true" removeOldOutput="true">
<classpath refid="xjc.classpath" />
<arg value="-Xxew" />
</xjc>
</target>
</project>Plugin does not support JAXB v3, see issue #199.
Versions ≥ 0.12.2 work with jaxb-xew-plugin ≥ v1.8 (see issue#50 for other options):
<plugin>
<groupId>org.jvnet.jaxb2.maven2</groupId>
<artifactId>maven-jaxb2-plugin</artifactId>
<version>0.12.2</version>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<generateDirectory>${project.build.sourceDirectory}</generateDirectory>
<extension>true</extension>
<args>
<arg>-Xxew</arg>
</args>
<plugins>
<plugin>
<groupId>com.github.jaxb-xew-plugin</groupId>
<artifactId>jaxb-xew-plugin</artifactId>
<version>1.11</version>
</plugin>
</plugins>
</configuration>
</execution>
</executions>
</plugin>Note: maven-jaxb2-plugin prior to v0.8.0 was compiled against JAXB XJC API which is not compatible with this plugin. Versions [0.8.1…0.12.1] should work fine.
<plugin>
<groupId>org.jvnet.jaxb2.maven2</groupId>
<artifactId>maven-jaxb2-plugin</artifactId>
<version>0.8.1</version>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<verbose>true</verbose>
<generateDirectory>${project.build.sourceDirectory}</generateDirectory>
<schemaDirectory>xsd</schemaDirectory>
<removeOldOutput>false</removeOldOutput>
<episode>false</episode>
<extension>true</extension>
<args>
<arg>-no-header</arg>
<arg>-Xxew</arg>
<arg>-Xxew:instantiate lazy</arg>
</args>
<plugins>
<plugin>
<groupId>com.github.jaxb-xew-plugin</groupId>
<artifactId>jaxb-xew-plugin</artifactId>
<version>1.11</version>
</plugin>
</plugins>
</configuration>
</execution>
</executions>
</plugin>jaxb2-maven-plugin ≥ v3.1.0 requires jaxb-xew-plugin ≥ v2.0, see example.
jaxb2-maven-plugin ≥ v2.1 should work just fine with jaxb-xew-plugin ≤ v1.11.
Note: jaxb2-maven-plugin ≤ v1.5 was compiled against JAXB XJC API v2.1.13 which is not compatible with this plugin, thus additional dependency is needed to be added to plugin classpath.
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxb2-maven-plugin</artifactId>
<version>1.5</version>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>xjc</goal>
</goals>
<configuration>
<verbose>true</verbose>
<outputDirectory>${project.build.sourceDirectory}</outputDirectory>
<schemaDirectory>xsd</schemaDirectory>
<clearOutputDir>false</clearOutputDir>
<extension>true</extension>
<arguments>-no-header -Xxew -Xxew:instantiate lazy</arguments>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>com.github.jaxb-xew-plugin</groupId>
<artifactId>jaxb-xew-plugin</artifactId>
<version>1.11</version>
</dependency>
<!--
| We need to update the jaxb-xjc dependency from v2.1.13 to v2.2.11
| used by the jaxb-xew-plugin (v2.1.13 does not have the required
| method com.sun.codemodel.JAnnotatable.annotations()Ljava/util/Collection).
-->
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-xjc</artifactId>
<version>2.2.11</version>
</dependency>
</dependencies>
</plugin>You can find more examples of this plugin in samples directory (including how to call this plugin using jaxws-maven-plugin or cxf-codegen-plugin).
plugins {
id 'java'
id 'maven'
}
sourceCompatibility = 8
targetCompatibility = 8
repositories {
mavenCentral()
}
project.ext {
jaxbVersion = "3.0.1"
generatedSourcesDir = "target/generated-sources"
}
sourceSets {
generated {
output.classesDir = "target/classes"
java {
srcDir project.generatedSourcesDir
}
}
test {
compileClasspath += generated.output
runtimeClasspath += generated.output
}
}
configurations {
xjc
}
dependencies {
compile "jakarta.xml.bind:jakarta.xml.bind-api:${jaxbVersion}"
compile "org.glassfish.jaxb:jaxb-xjc:${jaxbVersion}"
compile "org.glassfish.jaxb:jaxb-runtime:${jaxbVersion}"
xjc "com.github.jaxb-xew-plugin:jaxb-xew-plugin:2.1"
xjc "codes.rafael.jaxb2_commons:jaxb2-fluent-api:3.0.0"
}
task processXSD {
ant.taskdef(name: "xjc", classname: "com.sun.tools.xjc.XJCTask", classpath: configurations.compile.asPath)
mkdir project.generatedSourcesDir
ant.xjc(destdir: project.generatedSourcesDir, package: "com.mycompany", extension: true) {
classpath {
pathelement(path: configurations.xjc.asPath)
}
schema(dir: "xsd", includes: "test.xsd")
arg(value: "-Xxew")
arg(value: "-Xfluent-api")
}
}
compileJava.dependsOn processXSD
It could be that some plugins fail if executed after Xew, check this my comment for further details.
For correct generation of episode file the corresponding XJC options should follow -Xxew, for example:
... -Xxew -episode <file> ...
This will trigger episode plugin after Xew plugin and episode file will be correctly generated. Note that maven-jaxb2-plugin adds -episode to the end of argument list, hence works correctly.
equals, hashCode, simpleEquals, simpleHashCode, fluent-api, value-constructor, jaxbindex and immutable plugins
These plugins should be activated after Xew plugin:
... -Xxew -Xequals -XhashCode -XsimpleEquals -XsimpleHashCode -Xfluent-api -Xvalue-constructor -Xjaxbindex -immutable ...
Otherwise (if they are activated before) Xew plugin cannot revert/complement the changes they made and compile-time error is guaranteed.
This plugin should be activated before Xew plugin due to problem described in issue#15:
... -Xsetters -Xxew ...
If you have time and desire to contribute to this project you can do it in many ways:
- Improve this very documentation.
- Implement unit tests.
- Provide extra samples.
Everybody is very welcomed to send patches by email. But the best way would be:
- Fork the repository.
- Apply the formatting rules (the ones for Eclipse can be found in
distfolder). - Create a ticket in bugtracker. If applicable attach XSD that demonstrates the problem to the issue.
- Create a branch referring the ticket number (
git branch issue-22). - Do the changes.
- Verify your outgoing changeset. Make sure that:
- Your changeset is minimal and sufficient for the feature implementation.
- Your formatting rules have not caused changes in each and every line (e.g. due to end-of-line markers).
- All unit tests run successfully.
- Commit to your own fork, mentioning the ticket number in commit message (
Implemented nice feature (fixes #22)). Check here the commit message syntax sugar. - Request for pull.
If you provide the code in any way (patch, pull request, post, comment, …) you automatically agree with a project license.
This very open source project is maintained and improved during my free time. That is why I have no ability to test the functionality will all different combinations of Java, JAXB, JAXB plugins and Maven plugins. I leave this to community. Hence please in newly created bug report:
- mention Java version
- attach a simple minimalistic project (preferably based on Ant, Maven, Gradle) that demonstrates the problem (alternatively one can clone this repository plus alter one of the
samples)
- There are no specific coding and naming conventions for this project except ones given in Code Conventions for the Java Programming Language by Sun. Use best practices and common sense.
- For code formatting basically Eclipse build-in formatting rules were used with following changes:
- Indentation → Align fields on columns: on
- Indentation → Tab policy: Mixed
- Indentation → Use spaces to indent wrapped lines: on
- Line Wrapping → Maximum line width: 120
- Line Wrapping → Default indentation for wrapped lines: 3
- Comments → Maximum line width for comments: 120
- Comments → Enable line comment formatting: off
- New Lines → Insert new line in empty anonymous class body: off
- New Lines → Insert new line in empty block: off
- TAB is used for alignment for XML/XSD/... files.
- Read Sonatype OSS Maven Repository Usage Guide from cover to cover.
- Use the following
settings.xmlfor your Maven (see Sharing Files with Build Agents about how to sharesettings.xmlwith build nodes on CloudBees and Configuring GPG/PGP for Maven Releases about GPG profile):
<settings>
<!-- Optional proxy configuration (if applicable to your environment) -->
<proxies>
<proxy>
<active>true</active>
<protocol>http</protocol>
<host>proxy</host>
<port>8080</port>
<nonProxyHosts>*.internal.domain</nonProxyHosts>
</proxy>
<proxy>
<active>true</active>
<protocol>https</protocol>
<host>proxy</host>
<port>8080</port>
<nonProxyHosts>*.internal.domain</nonProxyHosts>
</proxy>
</proxies>
<servers>
<server>
<id>sonatype-nexus-snapshots</id>
<username>...sonatype_user...</username>
<password>...sonatype_password...</password>
</server>
<server>
<id>sonatype-nexus-staging</id>
<username>...sonatype_user...</username>
<password>...sonatype_password...</password>
</server>
<server>
<id>github.com</id>
<username>...github_user...</username>
<password>...github_password...</password>
</server>
</servers>
<profiles>
<profile>
<id>secure</id>
<properties>
<gpg.useagent>false</gpg.useagent>
<gpg.passphrase>...passphrase...</gpg.passphrase>
<gpg.homedir>/private/...github_user.../gpg</gpg.homedir>
</properties>
</profile>
</profiles>
</settings>- Make sure you have git ≥ v1.7.10 installed, otherwise you may face this bug#341221.
- For JDK 1.6 you need to put JAXB API ≥ v2.2.3 to
jre/lib/endorseddirectory of JDK which is used to build the project. Otherwise build will fail withjava.lang.NoSuchMethodError: javax.xml.bind.annotation.XmlElementWrapper.required()Z. - For Hudson freestyle job specify:
- Pre-release step
git checkout master; git reset --hard origin/master(see Can't get automated release working with Hudson + Git + Maven Release Plugin for more details about the problem). - Next step (release):
release:prepare release:perform -Pstage-release,secure -Dresume=false
- Pre-release step
The plugin flow consists of the following parts:
- Parse arguments.
- Find classes which are candidates for removal:
- The candidate class should not extend any other class (as the total number of properties will be more than 1)
- The candidate class should have exactly one non-static property.
- This property should be a collection.
- This collection should have exactly one parametrisation type.
- Visit all classes again to check if the candidate is not eligible for removal:
- If there are classes that extend the candidate
- If there are class fields that refer the candidate by e.g.
@XmlElementRefannotation
- Visit all classes again to replace the property having the candidate class type with collection plus
@XmlElementWrapperannotation. On this step getters/setters are update andObjectFactorymethods are corrected. Also lazy initialization policy is applied. - Candidates which are still marked for removal are finally removed (and
ObjectFactoryis updated accordingly).
There are many pitfalls in JAXB Code Model API which are forcing the developer to use dirty tricks (like accessing private fields) in order to implement the manipulation of code model. Among others:
- issue #957 mentions what need to be added to make it possible for the inner class to be moved to another class or package.
- issue #883 does not allow to learn if "simpleMode" setting is enabled, which in its turn controls plural form for collection property names. There are however some more difficulties to overcome.
- issue #1677 add/implement JVar.annotate(JAnnotationUse annotation).
- issue #1679 add/implement JAnnotationUse.param(String name, JAnnotationValue annotationValue).
Original code by Bjarne Hansen. Many thanks to committers:
- Dmitry Katsubo
- Tobias Warneke
- David Matheson
- Sebastian Steiner
- Colin Fairless
- Patrick Crocker
- Kermit The Frog
- Dominik Broj
- and others...
The whole project is licensed under LGPLv3 (or any later version).