Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.2.2
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
JDK version and platform:1.6u3 for linux
Description
//the following test will always failed
public void testArrayListOrder()
Activity
Unfortunately this is another issue with Jettison itself ... :-/
Jörg Schaible
added a comment - Unfortunately this is another issue with Jettison itself ... :-/ Hi,
after some investigation, I have to state that the problem is related to the way Jettison maps the XML into JSON arrays. See Jettison's user guide and you'll know that Jettison will only put XML elements into an array if they are at the same level and have the same name. In your case it will map the collection into an object containing an array of ints and a single string. And it will also deserialize this. It is just that the original sequence of the elements is no longer kept. You may use the JsonHierarchicalStreamDriver to generate the JSON, but recognize the different JSON representation. Here the renderer did know exactly what types it dealt with and how they have to be written into proper JSON. However, the resulting JSON string does no longer contain enough information to recreate the original objects. Main problem is, that you cannot express all necessary data in JSON to guarantee a 1:1 deserialization into arbitrary Java objects.
- Jörg
Jörg Schaible
added a comment - Hi,
after some investigation, I have to state that the problem is related to the way Jettison maps the XML into JSON arrays. See Jettison's user guide and you'll know that Jettison will only put XML elements into an array if they are at the same level and have the same name. In your case it will map the collection into an object containing an array of ints and a single string. And it will also deserialize this. It is just that the original sequence of the elements is no longer kept. You may use the JsonHierarchicalStreamDriver to generate the JSON, but recognize the different JSON representation. Here the renderer did know exactly what types it dealt with and how they have to be written into proper JSON. However, the resulting JSON string does no longer contain enough information to recreate the original objects. Main problem is, that you cannot express all necessary data in JSON to guarantee a 1:1 deserialization into arbitrary Java objects.
Jörg
Closed after no further comment has been given.
Jörg Schaible
added a comment - Closed after no further comment has been given. 
actually, i tried with list, vector and array. both of them failed. that's why i issue this bug:
JettisonMappedXmlDriver doesn't work for collection object.