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
Partner Zones AWS Cloud
by AWS Developer Relations
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
Partner Zones
AWS Cloud
by AWS Developer Relations
Building Scalable Real-Time Apps with AstraDB and Vaadin
Register Now

Trending

  • What Is React? A Complete Guide
  • Why You Should Consider Using React Router V6: An Overview of Changes
  • Introduction To Git
  • Authorization: Get It Done Right, Get It Done Early

Trending

  • What Is React? A Complete Guide
  • Why You Should Consider Using React Router V6: An Overview of Changes
  • Introduction To Git
  • Authorization: Get It Done Right, Get It Done Early
  1. DZone
  2. Coding
  3. Languages
  4. Applying a Namespace During JAXB Unmarshal

Applying a Namespace During JAXB Unmarshal

Blaise Doughan user avatar by
Blaise Doughan
·
Nov. 10, 12 · Interview
Like (0)
Save
Tweet
Share
58.67K Views

Join the DZone community and get the full member experience.

Join For Free

 For some an XML schema is a strict set of rules for how the XML document must be structured.  But for others it is a general guideline to indicate what the XML should look like.  This means that sometimes people want to accept input that doesn't conform to the XML schema for some reason.  In this example I will demonstrate how this can be done by leveraging a SAX XMLFilter.

Java Model

Below is the Java model that will be used for this example.

Customer
package blog.namespace.sax;
 
import javax.xml.bind.annotation.XmlRootElement;
 
@XmlRootElement
public class Customer {
 
    private String name;
 
    public String getName() {
        return name;
    }
 
    public void setName(String name) {
        this.name = name;
    }
 
}
package-info
We will use the package level @XmlSchema annotation to specify the namespace qualification for our model.
@XmlSchema(
        namespace="http://www.example.com/customer",
        elementFormDefault=XmlNsForm.QUALIFIED)
package blog.namespace.sax;
 
import javax.xml.bind.annotation.*;

XML Input (input.xml)

Even though our metadata specified that all the elements should be qualified with a namespace (http://www.example.com/customer) our input document is not namespace qualified.  An XMLFilter will be used to add the namespace during the unmarshal operation.
<?xml version="1.0" encoding="UTF-8"?>
<customer>
    <name>Jane Doe</name>
</customer>
XMLFilter (NamespaceFilter) 

The easiest way to create an XMLFilter is to extend XMLFilterImpl.  For our use case we will override the startElement and endElement methods.  In each of these methods we will call the corresponding super method passing in the default namespace as the URI parameter.
package blog.namespace.sax;
 
import org.xml.sax.*;
import org.xml.sax.helpers.XMLFilterImpl;
 
public class NamespaceFilter extends XMLFilterImpl {
 
    private static final String NAMESPACE = "http://www.example.com/customer";
 
    @Override
    public void endElement(String uri, String localName, String qName)
            throws SAXException {
        super.endElement(NAMESPACE, localName, qName);
    }
 
    @Override
    public void startElement(String uri, String localName, String qName,
            Attributes atts) throws SAXException {
        super.startElement(NAMESPACE, localName, qName, atts);
    }
 
}

Demo

In the demo code below we will do a SAX parse of the XML document.  The XMLReader will be wrapped in our XMLFilter.  We will leverage JAXB's UnmarshallerHandler as the ContentHandler.  Once the parse has been done we can ask the UnmarshallerHandler for the resulting Customer object.
package blog.namespace.sax;
 
import javax.xml.bind.*;
import javax.xml.parsers.*;
import org.xml.sax.*;
 
public class Demo {
 
    public static void main(String[] args) throws Exception {
        // Create the JAXBContext
        JAXBContext jc = JAXBContext.newInstance(Customer.class);
 
        // Create the XMLFilter
        XMLFilter filter = new NamespaceFilter();
 
        // Set the parent XMLReader on the XMLFilter
        SAXParserFactory spf = SAXParserFactory.newInstance();
        SAXParser sp = spf.newSAXParser();
        XMLReader xr = sp.getXMLReader();
        filter.setParent(xr);
 
        // Set UnmarshallerHandler as ContentHandler on XMLFilter
        Unmarshaller unmarshaller = jc.createUnmarshaller();
        UnmarshallerHandler unmarshallerHandler = unmarshaller
                .getUnmarshallerHandler();
        filter.setContentHandler(unmarshallerHandler);
 
        // Parse the XML
        InputSource xml = new InputSource("src/blog/namespace/sax/input.xml");
        filter.parse(xml);
        Customer customer = (Customer) unmarshallerHandler.getResult();
 
        // Marshal the Customer object back to XML
        Marshaller marshaller = jc.createMarshaller();
        marshaller.setProperty(Marshaller.JAXB_FORMATTED_OUTPUT, true);
        marshaller.marshal(customer, System.out);
    }
 
}

Output

Below is the output from running the demo code.  Note how the output contains the namespace qualification based on the metadata.
<?xml version="1.0" encoding="UTF-8"?>
<customer xmlns="http://www.example.com/customer">
    <name>Jane Doe</name>
</customer>

Further Reading 

If you enjoyed this post then you may also be interested in:
  • JAXB & Namespaces
  • Preventing Entity Expansion Attacks in JAXB


XML Use case Document Schema Metadata Java (programming language) Leverage (statistics) Annotation 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.

Trending

  • What Is React? A Complete Guide
  • Why You Should Consider Using React Router V6: An Overview of Changes
  • Introduction To Git
  • Authorization: Get It Done Right, Get It Done Early

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

Let's be friends: