jsonwebservice
unread,Feb 14, 2011, 3:36:24 PM2/14/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jsonwebservice
In upcomming 0.6 version we are going to change the way of choice list
handling.
Root cause: when we have choice list object order not in proper order
added in server.
0.5 version test:
In : {"test1EmptyInXmlElementsOut":{}}";
expected : {"statusFlag":true,"xmlElementsObj":{"mapObject":
[{"keyProperty1":
1,"keyProperty2":"KK","property1":true,"valueProperty1":
2,"valueProperty2":"DD"}],
"objectReserved":[{"boolean":true,"enum":"CONST_2","float":
1.2,"int":1,"String":"SS"}],
"object":[{"property1":1},{"property1":2}]}}
In above example object with property1 added first and second but in
response it is moved last as well if there is another object mixed in
order, json format we are loosing order of choice element.
0.6 change:
{"statusFlag":true,"xmlElementsObj":
{"objectOrObjectReservedOrMapObject":[{"object":{"property1":1}},
{"object":{"property1":2}},{"objectReserved":
{"boolean":true,"enum":"CONST_2","float":1.2,"int":1,"String":"SS"}},
{"mapObject":{"keyProperty1":
1,"keyProperty2":"KK","property1":true,"valueProperty1":
2,"valueProperty2":"DD"}}]}}
Please get back if any one has difrent idea or consern about this
format.