DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Coding
  3. Languages
  4. JAXB - Representing Null and Empty Collections

JAXB - Representing Null and Empty Collections

Blaise Doughan user avatar by
Blaise Doughan
·
Jan. 03, 13 · Interview
Like (0)
Save
Tweet
Share
47.29K Views

Join the DZone community and get the full member experience.

Join For Free

In this post I will cover how to differentiate between null and empty collections in the XML representation with JAXB (JSR-222).

Demo Code 

The following demo code will be used for all the different versions of the Java model.  It simply sets one collection to null, the second to an empty list, and the third to a populated list. 

package blog.xmlelementwrapper;
 
import java.util.ArrayList;
import javax.xml.bind.*;
 
public class Demo {
 
    public static void main(String[] args) throws Exception {
        JAXBContext jc = JAXBContext.newInstance(Root.class);
         
        Root root = new Root();
 
        root.nullCollection = null;
 
        root.emptyCollection = new ArrayList<String>();
 
        root.populatedCollection = new ArrayList<String>();
        root.populatedCollection.add("foo");
        root.populatedCollection.add("bar");
         
        Marshaller marshaller = jc.createMarshaller();
        marshaller.setProperty(Marshaller.JAXB_FORMATTED_OUTPUT, true);
        marshaller.marshal(root, System.out);
    }
 
}


Mapping #1 - Default

JAXB models do not require any annotations (see JAXB - No Annotations Required). First we will look at what the default behaviour is for collection properties.

package blog.xmlelementwrapper;
 
import java.util.List;
import javax.xml.bind.annotation.*;
 
@XmlRootElement
@XmlAccessorType(XmlAccessType.FIELD)
public class Root {
 
    List<String> nullCollection;
     
    List<String> emptyCollection;
 
    List<String> populatedCollection;
 
}

Examining the output we see that the output corresponding to the nullCollection and emptyCollection fields is the same.  This means with the default mapping we can't round trip the instance.  For the unmarshal use case the value of the nullCollection and emptyCollection the value of the fields will be whatever the class initialized them to (null in this case).

<?xml version="1.0" encoding="UTF-8"?>
<root>
    <populatedCollection>foo</populatedCollection>
    <populatedCollection>bar</populatedCollection>
</root>

Mapping #2 - @XmlElementWrapper

The @XmlElementWrapper annotation is used to add a grouping element around the contents of a collection.  In addition to changing the appearance of the XML representation it also allows us to distinguish between null and empty collections.

package blog.xmlelementwrapper;
 
import java.util.List;
import javax.xml.bind.annotation.*;
 
@XmlRootElement
@XmlAccessorType(XmlAccessType.FIELD)
public class Root {
 
    @XmlElementWrapper
    List<String> nullCollection;
     
    @XmlElementWrapper
    List<String> emptyCollection;
 
    @XmlElementWrapper
    List<String> populatedCollection;
 
}

The representation for the null collection remains the same, it is absent from the XML document.  For an empty collection we see that only the grouping element is marshalled out.  Since the representations for null and empty are different we can round trip this use case.

<?xml version="1.0" encoding="UTF-8"?>
<root>
    <emptyCollection/>
    <populatedCollection>
        <populatedCollection>foo</populatedCollection>
        <populatedCollection>bar</populatedCollection>
    </populatedCollection>
</root>

Mapping #3 - @XmlElementWrapper(nillable=true)

The nillable property on the @XmlElementWrapper annotation can be used to change the XML representation of null collections.

package blog.xmlelementwrapper;
 
import java.util.List;
import javax.xml.bind.annotation.*;
 
@XmlRootElement
@XmlAccessorType(XmlAccessType.FIELD)
public class Root {
 
    @XmlElementWrapper(nillable=true)
    List<String> nullCollection;
     
    @XmlElementWrapper(nillable=true)
    List<String> emptyCollection;
 
    @XmlElementWrapper(nillable=true)
    List<String> populatedCollection;
 
}

Now the grouping element is present for all three fields.  The xsi:nil attribute is used to indicate that the nullCollection field was null.  Like the previous mapping this one can be round tripped.

<?xml version="1.0" encoding="UTF-8"?>
<root>
    <nullCollection
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:nil="true"/>
    <emptyCollection/>
    <populatedCollection>
        <populatedCollection>foo</populatedCollection>
        <populatedCollection>bar</populatedCollection>
    </populatedCollection>
</root>




XML Annotation Use case Element Trip (search engine) Property (programming) Java (programming language) POST (HTTP)

Published at DZone with permission of Blaise Doughan, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Agile Transformation With ChatGPT or McBoston?
  • What Was the Question Again, ChatGPT?
  • The Role of Data Governance in Data Strategy: Part II
  • Continuous Development: Building the Thing Right, to Build the Right Thing

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: