users@jersey.java.net

JSON Format

From: Lars Tackmann <lars_at_randompage.org>
Date: Tue, 14 Oct 2008 11:47:35 +0200

Hi all

Consider the following XML (showing a empty, single and multi element
user list).

--
# empty user list
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<users/>
# single element user list
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<users>
   <user>
     <id>1</id>
     <name>user1</name>
   </user>
</users>
# multi element user list
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<users>
   <user>
     <id>2</id>
     <name>user2</name>
   </user>
   <user>
     <id>1</id>
    <name>user1</name>
  </user>
</users>
--
Prior to Jersey 1.0 this used to be converted into the following JSON code:
--
# empty user list
{"users":null}
# single element user list
{"users":{"user":[{"id":"1","name":"user1"}]}}
# multi element user list
{"users":{"user":[{"id":"2","name":"user2"},{"id":"1","name":"user1"}]}}
--
but in 1.0 it now gets converted into:
--
# empty user list
null
# single element user list
{"user":{"id":"1","name":"user1"}}
# multi element user list
{"user":[{"id":"2","name":"user2"},{"id":"1","name":"user1"}]}
--
is this by design ? (and is this new format stable). If so then I will
refactor my client code to deal with it,
if not then perhaps I should apply a provider fix.
-- 
Yours sincerely
Lars Tackmann