Re: javax.servlet.ServletException: non-HTTP request or response

Sorry... forgot to post my TestApplication. Cheers, Dave package restlet; import org.restlet.Application; import org.restlet.Context; import org.restlet.Directory; import org.restlet.Restlet; public class TestApplication extends Application { public TestApplication() {

Re: Example for Directory + War? Not working for me

Hi Mike, Thanks a lot for reporting this problem. I've updated the svn repository. Could you make some tests? best regards, Thierry Boileau Hi there. [ ... ] I'm trying to use code like the following to host a bunch of .css files. Because I had problems, I've been testing it with URLs

RE: javax.servlet.ServletException: non-HTTP request or response

Hi David, Are you sure it is an issue within the Restlet code? Looking at the stack trace, it seems that the exception is thrown by org.mortbay.jetty.servlet.ServletHolder.handle Your Restlet Application looks fine. Note that the usage of Directory with the ServerServlet adapter requires a fix

RE: two quick questions

Hi Serge, You're welcome! Thanks for your patience in solving your routing issue. We know that a detailed user guide is missing in our documentation. We hope to start filling this hole at the end of the year. Thanks also for the positive comparison against other frameworks. If you see anything

Re: Proposed OPTIONS compliance patch

Thank you for including this! I think with this addition to NRE, Restlet covers everything needed quite well for DAV 1; our implementation thereof is now functioning nicely. Restlet already includes all the relevant Status and Method definitions. I added RFE #346 per your suggestion; the

Null pointer exception with anonymous restlets

If you have the following code to create a Restlet instance: new Restlet() { public void handle(Request request,Response response) { getContext().getLogger().info(Handling test...); response.setStatus(Status.SUCCESS_OK,OK!); } }; you'll

Re: Keep Alive Problem with Simple Framwork

On 6/4/07, Adam Taft [EMAIL PROTECTED] wrote: I've discovered a problem with the Simple framework web server in conjunction with Keep Alive. Basically, it seems triggered by two POST requests in a row. The first POST request works fine, however a followup POST request will hang. Once a

Re: Keep Alive Problem with Simple Framwork

Alex, The only resolve I found was to switch to Jetty. I didn't do anything more, as I couldn't determine whose fault it was (restlet or simple). I'd suggest using Jetty. Adam Alex Milowski wrote: On 6/4/07, Adam Taft [EMAIL PROTECTED] wrote: I've discovered a problem with the Simple

Re: Example for Directory + War? Not working for me

On 15 Aug 2007, at 19:26, Jerome Louvel wrote: Hi Mike, [ ... ] Alternatively, you can try first with Restlet 1.0.4, then with the 1.0 snapshot I've just uploaded at: http://www.restlet.org/downloads/1.0/current.zip I went for this option. I re-confirmed the failure and applied the

RE: Keep Alive Problem with Simple Framwork

I just saw this behavior in svn trunk on Simple with not just POST, also PROPFIND and PUT ... anything with an entity body in the request. I worked around it with the new Request.release() mechanism, but was not able to locate the underlying cause. -Original Message- From: Adam Taft

Null pointer exception with Grizzy Connector

I was testing grizzy when I ran into a null pointer exception while parsing credentials. Here's the fix: Index: SecurityUtils.java === --- SecurityUtils.java (revision 2136) +++ SecurityUtils.java (working copy) @@ -292,8 +292,12

Critical Patch for Grizzy Connector

I figured out why I was having troubles with the Grizzy connector. It pools the instances of GrizzyServerCall but doesn't clear the headers. As such, previous random headers remain in the call! In my case, there were two Authorization headers and the parser uses getValues() on the