What is the ObjectFactory role during JAXB-Unmarshalling?
Asked Answered
C

2

9

I'm using JAXB 2.2.2 to parse a simple XML-REST stream. This is the piece of code:

JAXBContext jc = JAXBContext.newInstance( "com.example.entities" );
Unmarshaller u = jc.createUnmarshaller();
r = (Response )u.unmarshal( inputStream );

ObjectFactory class:

@XmlRegistry
public class ObjectFactory {

    public Response createRsp() {
        return new Response();
    }
}

Response class:

@XmlAccessorType(XmlAccessType.FIELD)
@XmlRootElement(name="rsp")
@XmlType
public class Response { ... }

The "com.example.entities" must contain the ObjectFactory class or jaxb.index. I would like to use the ObjectFactory class in order to decide some pojo initialization, but these class is never used: the Response class is always instantiated by class.newInstance() directly. Is there something wrong in this?

Condone answered 25/4, 2011 at 15:51 Comment(0)
P
13

You can leverage the @XmlType annotation to control how the objects are created:

@XmlType(factoryClass=ObjectFactory.class, factoryMethod="createRsp")
public class Response {
}

For More Information

Predestinate answered 25/4, 2011 at 15:58 Comment(1)
My goodness, I spent the last several hours looking in vain for clues as to how to get my factory method to work, until I read this. Thank you!Limy
C
2

The ObjectFactory class generated by the XJC compiler is not useful to the factoryClass and factoryMethod @XmlType annotation because the factoryMethod must be a static no-arg method and the XJC generate instance methods.

Chericheria answered 13/8, 2014 at 20:31 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.