Re: Handling collections with Aegis in JAX-RS

Hi Benson JSON has no idea of what namespaces so it needs to map namespaces to something, hence the need for a namespace map being setup. In simple cases it's now being done automatically... cheers, Sergey bimargulies wrote: > > Sergey, > > I've made it as far as the namespace issues with J

RE: JAX-RS and generics

Hi I'm concerned it may be not be portable, that is the providers which work with other JAXRS implementations will end up being unusable in CXF. You may be right but I've seen the number of providers which implement MessageBodyX and then cast them internally. For ex to Feed or Entry, etc. Let me

RE: Possible alternative source of JSON

Users can easily wrap Jackson if they prefer. We can add a property to existing providers which will allow for namespaces be dropped altogether during the serialization if users prefer to parse JSON manually. Cheers, Sergey -Original Message- From: Benson Margulies [mailto:bimargul...@gm

Re: Possible alternative source of JSON

They don't have to wrap it. There's a full JAX-RS 1.0 provider provided. I added a test for our cooperation with it to the systests. Why don't we just endorse it over our on JSON provider? It makes cleaner JSON, and is smaller, lighter, faster and more flexible. On Sun, Sep 6, 2009 at 6:11 PM, S

Re: JAX-RS and generics

There are two ways to look at this. From the point of view of a 'provider bean', I can believe that a non-generic class is attractive. Maybe essential. Maybe my change to the Aegis providers was thus a mistake. >From the point of view of a clean API callable without suppressing any warnings, on th

Re: Handling collections with Aegis in JAX-RS

Sergey, Fine when producing JSON, albeit very ugly JSON. Completely impractical when reading the stuff. I can see no way to make it work in a live application. I also can't see why anyone would want this, as compared to what comes out of the Jackson provider. Which can be tuned with annotations, e

Re: Possible alternative source of JSON

Sergey, I think it is important that we work toward a clearly stated goal here. You originally recruited me to plug in Aegis to JAX-RS because, as I recall, the DOSGi people wanted a way to use JAX-RS without the burden of JAX-B and other related components. Now, on the one hand, Aegis+Jettison p