Details
Bug
Closed
Major
Description
Hi,
I don't know if I'm doing something wrong or not.
I've a pojo as a generic container: ResultBean<E extends Serializable> , where it has a property: E bean;
When E is an ArrayList, the output is this:
:{"@id": "1","bean": {"@class": "list","@id": "2","org.kyrian.entity.gnomo.GnNode": {"@id": "3","nodeId": 1,"nodeTitle": "nodo 1"},"org.kyrian.entity.gnomo.GnNode": {"@id": "4","nodeId": 2,"nodeTitle": "nodo 2"}}}
It has this structure: bean: node1, node 2. The desired output it will web: bean:[node1,node2]
I'm doing something wrong?
Activity
Hi Joerg, I've put on Jira, because I think it is an anormal behavior of json serializer, you can see it:
- Actual ouput of generic list:
bean: node1, node 2 - Desired and correct output:
bean: [node1,node2]
I think it's a bug, and for that I create this jira issue
Marcial Atiénzar Navarro
added a comment - Hi Joerg, I've put on Jira, because I think it is an anormal behavior of json serializer, you can see it:
Actual ouput of generic list:
bean: node1, node 2
Desired and correct output:
bean: [node1,node2]
I think it's a bug, and for that I create this jira issue It's a json bug on serializer generic objects
Marcial Atiénzar Navarro
added a comment - It's a json bug on serializer generic objects Not that I know that you use the JsonDriver and Jettison is not involved, I had the chance to take a closer look. Actually it turned out that the JsonWriter was fed by some reflection-based converters not with the actual type of the instance, but with the type of the field holding this object. Therefore the writer could no longer generate proper JSON for the serialized real type, that could leed to ill-formed JSON in the worst case. Fixed in trunk.
Jörg Schaible
added a comment - Not that I know that you use the JsonDriver and Jettison is not involved, I had the chance to take a closer look. Actually it turned out that the JsonWriter was fed by some reflection-based converters not with the actual type of the instance, but with the type of the field holding this object. Therefore the writer could no longer generate proper JSON for the serialized real type, that could leed to ill-formed JSON in the worst case. Fixed in trunk. 
Please use the user's list to ask questions.