RE: Tomcat not shutting down with Restlet

Still no reply on this yet. Anyone out there with some advice? Thanks, Matt -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2195179

RE: Re: release the connection

Hi, I'm getting a similar error using JsonRepresentation. Thanks, Gabi -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2189743

Re: release the connection

Hello I think I've read somewhere that the problem is related with Jetty manipulation of dom responses. I've solved the problem changing the result representations: @Get public Representation represent(Variant variant) throws ResourceException { Representation resultRepresentation = null; try

Reissuing Post after challenge losses entity body

I'm not sure if I am approaching the problem incorrectly, or I have found a bug. I am using the 1.2 snapshot from May 5 2009. I have a restlet client process and an associated restlet based server. The resources are all guarded using HTTP_DIGEST authentication. I have setup the client to automa

Reissuing Post after challenge losses entity body

Excuse me if this is a duplicate, my first post did no appear to go through. I'm not sure if I am approaching the problem incorrectly, or I have found a bug. I am using the 1.2 snapshot from May 5 2009. I have a restlet client process and an associated restlet based server. The resources are al

RE: GWT 1.6.4 (client only)

Yeah. You're right. I had two servlet API jars in my classpath. thanks -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2110301

release the connection

hi, I can see that I got the following message when using Client: INFO: The length of the message body is unknown. The entity must be handled carefully and consumed entirely in order to surely release the connection. how do I assure that the connection is released? ---

Weird exception using Spring integration

Hi, We move recently to the Spring integration (SpringBeanRouter and RestletFrameworkServlet). Since then, we have a resource that does not behave properly (and not on all environments) "The Web form cannot be parsed as no fresh content is available. If this entity has been already read once, cac