We Keep Coding

Rest facade to map xml to json

I'm confronted to a problem between two applications that we are using in my company. A CRM called Infonova and a mobile application.
The two applications have their own API, one is giving responses in xml format and the other one in Json.
The solution that I'm thinking to implement is to create an application that will be a facade API (gateway). This application will call the url API of the first application and will get xml response, and I'm thinking to map this solution to a json format and return it.
Since the attributes between xml and json are not the same, I want to know if there's a solution to map the two entities that will represent my responses.
Thanks in advance,

You could define an XML unmarshaller with spring, call your service that returns xml, unmarshal response to that bean. And then you could return this bean in response from a controller annotated with #Produces("application/json").
So, to sum it up. You have a controller that produces json, a bean containing field names you want in your json, and a custom unmarshaller for xml to populate those fields (custom because the field names between json and xml do not match).

Spring + Swagger2 + HashMap JSON

I have a service that has a HashMap receiving the json from the client
public ResponseEntity<?> trocarSenha(#RequestBody HashMap<String, String> json)
Is there any way to tell to swagger what I expect receive? I would like Swagger show something like this

In your case, assuming it's a fixed set of attributes your expecting, I would recommend using #ModelAttribute instead of #ResponseBody and using a concrete bean class with the getters and setters for the properties you wish to expose.
The catch is if u want to add additional properties that are not visible to the consumer but only to the server u might have to do some work.
NOTE: if the properties you wish to add are not conforming the bean spec (getters & setters) it will not be included.

How to get Spring 3.2's ConversionService and HttpMessageConverters to work together for #RequestBody annotation?

Before AJAX was popular, it was possible to convert between id's and entities by using a custom property editor and registering that in your controllers. So if you had a User form backing object that contained a Company, if company.id was 5, Spring would call your custom property editor to so that you could go fetch the Company with id 5 and set it onto your user.company property.
Now in the Ajax way of doing things, we have similar requirements. Instead of using a form backing object, we want to do an HTTP POST or PUT of a User object as JSON data and have Spring automatically convert that JSON to a User object on our behalf. Spring has made this possible with the #RequestBody annotation, and by using Jackson to marshall the JSON back and forth to Java objects.
This is just a fictitious example. Imagine a User containing a Company object with the appropriate getters/setters.
#RequestMapping(method = RequestMethod.POST)
#ResponseStatus(HttpStatus.NO_CONTENT)
public void create(#Valid #RequestBody User user) {
userService.saveUser(user);
}
Since property editors are a thing of the past as far as Spring is concerned, we are expected to use the new Conversion Service API. For my application, I have successfully created a factory that does what my old property editor did before - converting id's back to entities.
My question is, how can I get Spring to call into the conversion service during or after Jackson marshals the JSON data? I know it is possible to create a custom JsonDeserializer, but I find writing/testing these to be a pain and lengthy process as I need to do it for a massive number of entities, and each deserializer would take anywhere from 60 to 200 lines of code each.
I'd love it if Spring could do the id to entity mapping for me on my behalf, just as it did for form backing objects. Is there a way?

It will only work the root object User in this case it will not work for nested components. Spring Data REST has a `DomainClassConverter' which you can take a look at.
Basically you want to create ConditionalGenericConverter which checks if it can convert the requested object (i.e. can it be loaded by the EntityManager/SessionFactory). (A non-conditional version is here.
This all goes a bit against REST (basically) to do the lookup on the serverside as you should be sending everything needed with the request (Representational State Transfer and Hypermedia as Transfer Engine of All State). But that is for another discussion :) .
Links
Domain Entity Converter blog
Spring Reference guide

The M. Deinum's answer was great.
But for a practical work , think about AOP ;)
It can be interesting to use it in your problem :).

#RequestBody can not read MultiMap

I am trying to use MultiValueMap (implementation of MultiMap) from apache collections. I am using Spring MVC's #RequestBody annotation. However, I keep getting HTTPMediaTypeNotSupportedException. When I change the implementation to use Map of Map from Java Util, it works fine.
Any clue? Is Jackson API unable to work with anything other than core JDK Types?

A #RequestBody parameter is converted using HttpMessageConverter. For MultiValueMap you should register a custom converter. For more details, check this and this.

Android RestTemplate json deserialization

I need to write a Json client in Android for Zenfolio API. I decided to use Spring ResTemplate with MappingHttpJacksonConverter. When i do POST with "exchange" method i recieve json response with one element named "#type" that causes deserializatoon exception. Is there an annotation that tells deserializer to omit that tag? How to turn on annotation for json deserializer?

Try #JsonIgnoreProperties(ignoreUnknown=true) on your mapping classes if you want to ignore all elements that you are not interested in.

Try using #JsonIgnore ("#type"), Jackson annotations are enabled by default.
See http://wiki.fasterxml.com/JacksonAnnotations for more info.