The fun here all happens below the level of the service interface, so I'll trim ...
On Tue, Sep 8, 2009 at 7:37 AM, Josh Holtzman <[email protected]>wrote: > On Mon, Sep 7, 2009 at 2:41 PM, Benson Margulies <[email protected] > >wrote: > > > > Do you use JSON, XML, or both? If you use JSON, are you happy with it? > > > > > Both, but I'm just starting to play around with CXF's JSON support. I need > pretty tight control over the JSON/P that my REST endpoints produce, so > I'll > likely wind up serializing entities myself in at least some cases. > > > > Have you looked into jackson.codehaus.org's JSON provider? > > > > > Not yet. Should I? Is there a way to plug this into the DOSGi > implementation (which I use -- possibly inappropriately -- only as a means > to declarative publish my JAX-WS and JAX-RS endpoints)? > You might. The questions would be: does it produce the JSON you want, or can it be configured more easily to do so than the alternatives? > > > > 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? > > > > I use JAXB, not Aegis, for databinding because it's "the standard". Sorry > I > can't be of any help here. > So eventually you'll find out if you can use the JSON that emerges from JAXB feeding Jettison. > > Josh > >
