开发者

What is the ObjectFactory role during JAXB-Unmarshalling?

开发者 https://www.devze.com 2023-02-28 19:30 出处:网络
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\" );

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 开发者_StackOverflow中文版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?


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

  • http://bdoughan.blogspot.com/2011/06/jaxb-and-factory-methods.html


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.

0

精彩评论

暂无评论...
验证码 换一张
取 消