I should have read the rest of the thread before posting, sorry. I was forgetting just how big the Person object was and just how compact annotations are.... and then there will be the pain of maintenance with anything that large hand coded.
We might be talking about different jsonlibs ?, http://json-lib.sourceforge.net/usage.html does both ways serialize and parse, based on getters and setters..... but I suspect the hand coding is still a killer and mapping may be a pain, so annotations still win (IMH and better informed O :) ) Ian 2008/6/10 Kevin Brown <[EMAIL PROTECTED]>: > On Tue, Jun 10, 2008 at 3:12 PM, Ian Boston <[EMAIL PROTECTED]> wrote: > >> I have had good experiences with trees of maps and lists containing >> primitive types, serialized by json-lib. The same trees are easy to >> serialize using the apache xml-rpc libraries, and appear to stack-up >> reasonably well underload. Its not sophisticated, but it is fast to >> work with, light on the GC under load and appears to perform well. > > > The JSONObject library being used right now handles primitives and > containers already (JSONObject.put(Map), JSONObject.put(Collection)), as > well as bean-style objects (JSONObject.put(Object)). That doesn't handle the > conversion back, though, which is where a library would come in handy. > > This isn't just an issue for the social data, either -- the metadata handler > is currently doing all this by hand, and it would be much more convenient to > just have an annotation processor or something along those lines. > > >> >> I was going to try abdera in another project, now I am not so sure. >> >> 2008/6/10 Cassie <[EMAIL PROTECTED]>: >> > We tried to use abdera to implement the opensocial json restful format >> > within Shindig.. and it didn't work out very well. The code is clunky, >> > overly complicated for simple json and is hard to come up to speed on. >> > >> > So... I am going to try an alternate implementation based on the existing >> > older json wire format code. I was going to start coding something in a >> > separate dir so that none of the current code is disturbed. Hopefully, in >> > the next couple days we will have a cleaner impl of the restful json that >> is >> > 90% the same as all of the current social code. (this means less >> migration >> > for current social code users too, yea!) >> > >> > And as for atom... well, we can figure that out later :) >> > >> > Please let me know if you have any huge objections to this. >> > And of course, if it turns out to be worse than the abdera impl.. we can >> > always go back. >> > >> > - Cassie >> > >> >
