On Fri, 2008-11-14 at 21:06 +0100, Stephan Koops wrote:
> Hi Bruno,
> > Great work. I've tested it, it works fine and fits my needs.
> >
> Fine.
> > One comment though: I see the default route is only used when a root
> > resource is not found, not when a sub resource is not found. But from my
> > point of view, I'm only interested in whether there is some resource
> > which can handle the requested URI, I don't care if it is the root or
> > sub resource which is missing. IIUC, everything which can be done with
> > sub resources can also be done with root resources, so it seems like an
> > implementation detail to me. So I would call the default route in both
> > cases. What do you think?
> >
> The JaxRsRouter has now the same behaviour as in the org.restlet.Router.
> If this Router finds a Route ("root resource class") and gave it the
> request, but the reached Restlet could not forward the request (no "sub
> resource class"), than the defaultRestlet will not catch this error.
> In older versions I gave the possibility for such cases. Should I
> reimplement it?
Yes, I'd like that.
IMO the situation can't be easily compared with org.restlet.Router, as
that one has no knowledge of the internal behavior of the attached
Restlet's (nor does it say anything about what kinds of restlets can be
attached), while the JAX-RS system defines and controls the complete
routing up to potential sub-resources.
--
Bruno Dumon http://outerthought.org/
Outerthought http://www.daisycms.org/
[EMAIL PROTECTED] http://www.kauriproject.org/
