Re: JAX-RS extension: not enough time for development

Hi Jerome, This looks good. I've just updated the Javadocs of the extension to reflect what I think is the current state. Please review and let me know if you are fine with this statement: "Implementation of the JAX-RS 1.0 API developed by the JSR-311 expert group. The main class is JaxRsApplica

Re: Random Grizzly IOException

Hi Jerome, I downloaded the Restlet 1.1 RC2 and although it seems to be much better than before, under running the test with Jmeter, there is still exceptions being thrown. The exception is as follows: SEVERE: An exception occured writing the response entity java.lang.NullPointerException at

Re: Missing bytes in entity body

Pretty sure that's a bug. Content-length is supposed to be octets (HTTP spec 4.4.3, http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html) On Fri, Sep 26, 2008 at 5:29 AM, Roman Geus <[EMAIL PROTECTED]> wrote: > Is it a bug or a feature? > > Cheers, > Roman > >

Re: Using OPTIONS to describe a Resource

That's very cool! I've been ambivalent about WADL itself (I just don't encounter many actual users in my circles), but I just had a look at the extension, and it sure offers a good template to be followed by anyone wanting to leverage OPTIONS to describe Restlet plumbing in any syntax. On Fri, Se

Re: Missing bytes in entity body

BTW: I was using Restlet 1.1rc2, the reported tests. Roman Roman Geus wrote: Hi all I have run across a problem, where the last few bytes of the entity body are not transferred to the client. The problem occurs if the number of characters in the entity body does not match the number of byt

Missing bytes in entity body

Hi all I have run across a problem, where the last few bytes of the entity body are not transferred to the client. The problem occurs if the number of characters in the entity body does not match the number of bytes in the encoded string (in my case UTF-8). Example 1: @GET @Produces(

RE: JAX-RS extension: not enough time for development

Hi Stephan, This looks good. I've just updated the Javadocs of the extension to reflect what I think is the current state. Please review and let me know if you are fine with this statement: "Implementation of the JAX-RS 1.0 API developed by the JSR-311 expert group. The main class is JaxRsApplic

RE: Using OPTIONS to describe a Resource

Hi all, No need to wait for Restlet 1.2! The current WADL extension supports exactly this scenario. You just need to extend the WadlResource class and it will automatically handle the OPTIONS requests, returning an XML description of the resource. Of course, this default description can be cust