On Mon, 2009-09-07 at 08:41 -0400, Benson Margulies wrote: > Do you use JSON, XML, or both? If you use JSON, are you happy with it?
I'm a bit new to Apache CXF, but not new to marshalling to/from XML & JSON. As far as I'm concerned, I'm sticking with XML for now because (a) Jettison requires generating really awful JSON when used with JAXB annotations (which I'm also using), and (b) Many of the customers I'm working with are more familiar with XML than JSON anyway. > Have you looked into jackson.codehaus.org's JSON provider? I looked into it by skimming the site (literally) yesterday. And I like what I see. > If you have an existing conventional service, and you are looking to add (or > have added) JSON support, read on. > > How much investment do you have in data binding configuration? I'm > particularly interested in Aegis. Are any of you using Aegis with an > investment in .aegis.xml files or @nnotations? If so, what expectations do > you have for JSON? Well, I'm particularly interested in keeping JAXB around, but I'm not strongly wedded to it as I just started this project. I expect that JSON could natively (and reasonably) map simple types as well as lists of classes and or hashes. I stopped using Jettison when I realized that the contortions needed to make reasonably simple JSON wasn't worth it (I have other work to do that muck about with that right now). > I'm wondering, > really, if all of you could just plug in Jackson and get the results you > want. You might have to add some Jackson-specific @nnotations. If you are > dependent on .aegis.xml files to avoid @nnotations, this would be a problem. Having separate annotations (in addition to JAXB annotations) wouldn't break my heart if they get me what I want. --sgp
