RE: Re: Resources cannot be found anymore after upgrading from 2.0M5 to 2.0M6

2009-12-13 Thread Carsten Lohmann
Hello Fabian, which resource is supposed to match the http://localhost:900​0/workspaces/W1 request? From looking at your source code, I guess that you intended this Route to match: wrouter.attach(/{wksp}, WorkspaceResource.class); But that doesn't work because the new default matching mode

Re: Re: Resources cannot be found anymore after upgrading from 2.0M5 to 2.0M6

2009-12-13 Thread Fabian Mandelbaum
Hello Carsten, answering between lines: On Sun, Dec 13, 2009 at 4:18 AM, Carsten Lohmann c_lohm...@gmx.net wrote: Hello Fabian, which resource is supposed to match the http://localhost:9000/workspaces/W1 request? From looking at your source code, I guess that you intended this Route to

Resources cannot be found anymore after upgrading from 2.0M5 to 2.0M6

2009-12-12 Thread Fabian Mandelbaum
Hello there, I'm trying to upgrade restlet from 2.0M5 to 2.0M6, and found that I cannot access my resources anymore (HTTP 404 returned). The libs I've updated are: org.apache.httpclient.jar org.apache.httpcore.jar org.apache.commons.logging.jar org.restlet.ext.jaas.jar org.apache.httpmime.jar

Re: Resources cannot be found anymore after upgrading from 2.0M5 to 2.0M6

2009-12-12 Thread Ben R Vesco
Maybe it's the trailing slash? M5 defaulted to allowing the slash, M6 defaults to not allowing the trailing slash. Try removing it and see if that helps. This is in reference to the url requested by the client. On Sat, Dec 12, 2009 at 1:19 PM, Fabian Mandelbaum fmandelb...@gmail.com wrote:

RE: Re: Resources cannot be found anymore after upgrading from 2.0M5 to 2.0M6

2009-12-12 Thread Fabian Mandelbaum
Hello Ben, which trailing slash are your referring to? I get 404 when I try to access an existing resource, for example: http://localhost:9000/workspaces/W1 there's no trailing slash in that URL, and W1 does exist and was accessible with 2.0M5 Same happens for resources under the other