[Home] [By Thread] [By Date] [Recent Entries]
The treatment of lists is indeed a big issue in XML, misunderstood by lots of people. Some of them systematically wrap the list into a markup list : <foo> <valuelist> <value>123</value> <value>456</value> </valuelist> </foo> which is incredibly verbose compared to the JSON { "foo": ["bar", "spam"] } A better solution is to use xsd:list datatype : <foo value="bar spam"/> but that is not known. I have seen a REST javadoc generator which uses xsd:list for a list of markups... There are still critical Axis bugs opened on the serialization of String[] values, see https://issues.apache.org/jira/browse/AXIS-2250 Even without a schema you can get that value "bar spam" and split it, that is not XML philosophy, but... I agree it would be better not to have to define a schema in order to get that list. Regards Nicolas Debeissat 2010/12/9 Stephen Green <stephengreenubl@g...> Alternatively, why not improve the way XML defines attribute
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



