My only question would be... Why does the AegisJSONProvider work (which requires jettison), yet JSONProvider doesn't. When I tried the JSONProvider, I did have the jettison bundle installed the exact same way, it just didn't work.
... or maybe I misunderstood what you said :) On Fri, Apr 30, 2010 at 12:44 PM, Sergey Beryozkin <[email protected]>wrote: > Thanks for sharing this... > > I do think that the only reason a Jettison provider is not working OTB in > OSGI is that if no Jettison bundle is available by the the DOSGI DSW gets > installed then CXF JAXRS will just fail to initialize (Jettison) > JSONProvider; in this case it has to be restarted/refreshed after a > jettison > bundle has been installed given that it itself does not track the > availability of Jettison. > > I think DOSGI 1.2 should ship Jettison 1.2 - it is a small library and > looks > like many DOSGI RI/JAXRS users are expecting the default JSON support OTB > > cheers, Sergey > > On Fri, Apr 30, 2010 at 5:30 PM, kdog <[email protected]> wrote: > > > > > I did stumble upon a way to get a json (and/or xml) response... > > > > 1.) Make sure jettison 1.2 is available as a bundle in your osgi > container > > 2.) For "org.apache.cxf.rs.provider" use > > > > > "org.apache.cxf.jaxrs.provider.AegisElementProvider,org.apache.cxf.jaxrs.provider.AegisJSONProvider" > > > > Kind of odd since the normal JSONProvider did not work, yet > > AegisJSONProvider that uses jettison also works. Not a huge fan of the > way > > these providers spit things out, but it works for now to get both xml and > > json spitting out :) > > -- > > View this message in context: > > http://old.nabble.com/DOSGi-and-JSON-responses-tp27330507p28414202.html > > Sent from the cxf-user mailing list archive at Nabble.com. > > > > >
