Jonathan, I hope you don't mind the suggestion, but I wonder if you'd be open to possibly shifting your URL scheme a little?
For example, if /user/list routes to the "list of users" resource, which is what I call a "collection", you might want to consider something like this: /users /users/{id} I have the impression that this scheme is becoming fairly common in RESTful web services, and it was used repeatedly in the new book, RESTful Web Services (which I highly recommend). HTH, Avi On 6/8/07, Jonathan Hall <[EMAIL PROTECTED]> wrote:
Hi, Is it possible to do this: /user /user/{id} /user/list The problem comes from the app thinking list is just a {id} variable. I thought router.setRoutingMode(Router.FIRST) sounded like it would pick the route I wished by the order they were attached. In which case this would work: /user /user/list /user/{id} However, it seems to not work like that. No matter what order I attach the routes they seem to end up in the same order in a RouteList. I also need to have optional parameters attached to all of the urls. Any ideas? Best Regards, Jon
-- Avi Flax Senior Technologist arc90 | http://arc90.com