Databases
StackOverflow2013
Postsdbo
POUsage of @JsonSerialize and JsonSerializer
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsage of @JsonSerialize and JsonSerializer
    primarykey
    data
    text
    <h3>Problem</h3> <p>I have a Spring MVC application that requires me to translate the id's and names of a list of a certain entity to an array of JSON objects with specific formatting, and output that on a certain request. That is, I need an array of JSON objects like this:</p> <pre><code>{ label: Subject.getId() value: Subject.getName() } </code></pre> <p>For easy use with the jQuery Autocomplete plugin.</p> <p>So in my controller, I wrote the following:</p> <pre><code>@RequestMapping(value = "/autocomplete.json", method = RequestMethod.GET) @JsonSerialize(contentUsing=SubjectAutocompleteSerializer.class) public @ResponseBody List&lt;Subject&gt; autocompleteJson() { return Subject.findAllSubjects(); } // Internal class public class SubjectAutocompleteSerializer extends JsonSerializer&lt;Subject&gt; { @Override public void serialize(Subject value, JsonGenerator jgen, SerializerProvider provider) throws IOException, JsonProcessingException { jgen.writeStartObject(); jgen.writeStringField("label", value.getId().toString()); jgen.writeStringField("value", value.getName()); jgen.writeEndObject(); } } </code></pre> <p>The JSON I get back however, is the default serialization inferred by Jackson. My custom serializer seems to be completely ignored. Obviously the problem is incorrect usage of @JsonSerialize or JsonSerializer, but I could not find proper usage of these within context anywhere.</p> <h3>Question</h3> <p>What is the proper way to use Jackson to achieve the serialization I want? Please note that it's important that the entities are <em>only</em> serialized this way in this context, and open to other serialization elsewhere</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDCKing
    1. USDCKing
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsage of @JsonSerialize and JsonSerializer
      1. USkurochenko
      1. VTFavorite
    2. VO
      singulars
      1. POUsage of @JsonSerialize and JsonSerializer
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUsage of @JsonSerialize and JsonSerializer
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI realize this thread is quite old, but I'm running into this same problem. Since there is no accepted answer, I'm wondering if you found a good answer. As you've indicated, it's undesirable to annotate the entity directly as suggested below. IMHO, the approach you tried is the simplest and most elegant/semantic solution, but of course it isn't supported. It seems you have to jump through hoops with jackson/spring to do this - the only solution I've found requires creating and configuring custom ObjectMappers and involves quite a bit of boilerplate code/config. Is there any better approach?
      singulars
      1. POUsage of @JsonSerialize and JsonSerializer
      1. USshelley
    2. COUnfortunately I haven't fixed this. Although requesting JSON client side was our first preference when implementing it, this specific list of items turned out small enough to be put on the page at once. This is what we turned out doing, so we have a pure client side solution and no JSON to load. If you ever find out the best way to do this, I'd much appreciate knowing about it, however!
      singulars
      1. POUsage of @JsonSerialize and JsonSerializer
      1. USDCKing
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload