xml映射java类,jaxb java类到多个xml映射

I have a couple of java classes that I want to convert to xml using jaxb. (I have no need to generate the classes based on the schema) I need to be able to map the class to different xml formats so I do not want to use annotations. From what I've seen my best option seems to be to use external xml bindings. So I wanted to know:

1) I am using eclipse. I am new to JAXB and I would like to know how to integrate external bindings using eclipse?

2) What other options other than external xml bindings are available?

解决方案

I think you best option is to use MOXy XML bindings:

This allows you to define XMLJava mappings in form of XML files instead of annotations:

package-name="example">

value="example.adapters.MyHexConverter" />

You can use this file via JAXBContextProperties.OXM_METADATA_SOURCE property:

Map properties = new HashMap();

properties.put(JAXBContextProperties.OXM_METADATA_SOURCE, iStream);

JAXBContext ctx = JAXBContext.newInstance(new Class[] { Customer.class }, properties);

So if you want several different mappings for the same class, just write several XML bindings and create your JAXBContext with corresponding files. I think this is the best options right now, with MOXy

With pure JAXB RI you can write an own annotations reader. I did this once with Annox:

Another option was JBoss JAXBIntroductions, also based on a custom annotations reader:

But I'm not sure this is live anymore.

Since you want multiple mappings, you'll have to write them (all but one) manually. You can generate one set of mappings as annotations, but further mappings will have to be written manually. Or, let's say, I'm not aware of a plugin or tool which would generate, for instance, MOXy XML bindings. Wouldn't be a big problem to write one though.

You may also take a completely different approach. Instead of mapping one central model with different mappings/format, you can have map a separate package of DTOs onto these formats. And then convert between your DTOs and the central model. Something like

XML(1) DTO(1)|

XML(2) DTO(2)|Model

XML(3) DTO(3)|

Thus you'll have clean DTOs per exchange format (which you can generate out of schemas) and a single central business model (to rule them all). You'll have to convert between DTOs and the Model, this can be handled with a tool like Dozer.

If this is a better approach or not depends on how complex your formats are and how different they are fron one another.

Concerning your questions:

1) There's nothing special about Eclipse, just add MOXy as dependency and follow the docs.

2) I've described a few options above.