Any indication when to move toward a 0.7 or 0.8 JAX-WS version? Also browsing through the code, I have noticed that the StringProvider does not support primitive and generic types whereas other JAX-WS implementations do.
Thanks Olivier ----- Original Message ---- From: Sergey Beryozkin <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, May 20, 2008 7:43:04 AM Subject: Re: Message Body Providers for Java types? Hi No primitive types (or their object equivalents) are supported on the output by default, this is per JAX-RS spec, but nothing prevents a user from creating a custom writer, have a look please at a sample code for a Long writer at http://cwiki.apache.org/CXF20DOC/jax-rs-jsr-311.html. The reason is that it's not clear how a default writer should serialize say a given Long or List value if, say, an application/xml format is produced. I have some ideas how to deal with collections/maps on the output if application/xml is requested, and perhaps we may provide a writer for primitive types but only if text/plain is requested On input, primitive types are supported, but not collections. I believe the later version of the spec also mandates a support for collections if they're mapped to queries... Also, yes is the answer to your other question about supporting subresources exposed as interfaces in a root class... Cheers, Sergey Olivier Brand wrote: > > Is it possible to return an int, Integer or List objects on a JAX-RS > @GET method? > > I am getting the following error in the browser (example here with > ArrayList): > > .No message body writer found for response class : ArrayList. > > Thanks > > Olivier > > -- View this message in context: http://www.nabble.com/Message-Body-Providers-for-Java-types--tp17334084p17342174.html Sent from the cxf-user mailing list archive at Nabble.com.
