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

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