Hi,
In V2 version of API we completely changed the way how marshallers work. There were many reasons for this, like: simplification, scalability, separation of concerns and performance. In V1 version there was many custom converters for many types, converters were aware of particular formats (mixed JSON and XML logic, etc.).
Now in V2 version it works in much clearer way:
Business objects are converted to POJO objects dedicated for REST API (WsDTO's), it is done by Orika
Those WsDTO objects are marshalled/unmarshalled directly by JAXB. ALL objects are marshalled and unmarshalled in the same way, there is no customization during this process.
In general I don't recommend to customize it. In my opinion it is better to convert all DTO's always in the same way. It is the simplest and the most predictable behaviour. If you still would like to do it, here is detailed description how it works:
Jaxb2HttpMessageConverter is a converter class declared in spring configuration as message converter (separate instances for XML and JSON)
At runtime HttpMessageConverter's methods have the information about 'root' class that is converted (root class = class annotated by RequestBody or ResponseBody in controller)
During the marshalling or unmarshalling process Jaxb2HttpMessageConverter creates JAXBContext for given 'root' class. It uses by default MoxyJaxbContextFactoryImpl for that purpose.
MoxyJaxbContextFactoryImpl factory creates JAXBContext using EeLink Moxy implementation of JAXB. This implementation allows to set all JAXB metadata programmatically instead of annotations. This is important, because DTO classes are autogenerated and there is simple no way to use annotations in them.
In order to provide JAXB metadata the factory creates WsDTOGenericMetadataSourceAdapter for each seen class (see http://ee.org/eelink/documentation/2.5/moxy/runtime004.htm for details).
WsDTOGenericMetadataSourceAdapter creates JAXB metadata at runtime in the same way for all classes (all WsDTO's).
The implementation of naming root elements in XML payload is done in this WsDTOGenericMetadataSourceAdapter. It simply cuts 'WsDTO' from class name (function createNodeNameFromClass). This class is also responsible for wrapping collections (in XML).
In order to customize it, you have to change this implementation, it can be done on vairous levels. The best way is to provide configuration to WsDTOGenericMetadataSourceAdapter, so that it will be able to work with any class with default settings but with customizations for particular classes.
Regards,
Marek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.