> On Sun, Apr 28, 2013 at 11:42 AM, Grant <gsingers at apache dot org> wrote: > > > > I haven't dug into this code, but I suspect you aren't manipulating > > > References properly. I advise printing out the intermediate steps of your > > > Reference computation to see where it goes wrong. > > > > That's just it, I don't think it is even selecting my Redirector as the > > target for the endpoint, b/c it is not even calling getTargetRef due to the > > child endpoints. Is there something else on Redirector or in my attachment > > I should be overriding so that it stops trying to match once it resolves > > the parent? > > > > I don't know what you mean by "parent" or "child endpoints". > > If getTargetRef isn't being called, it's because the routing is wrong. If > you want the application or component to send *all* requests to the > redirector, use attachDefault: > > router.attachDefault(new MyRedirector(getContext(), ... other args ...); > >
Yes, this is my suspicion too. Here's what I mean by parent and child. I am attaching my DynRedirector at: http://foo:port/a I am, at run time, making a call to http://foo:port/a/b. Thus, "/b" is my "child" endpoint and "/a" is my parent endpoint (ie the one that _is_ the Redirector). Not sure if this is the right nomenclature for Restlet, so please correct me. I can see that the Restlet that owns the DynRedirector is getting selected, but then it is not able to find it's next route b/c "/b" was never officially attached since it is (in my mind) supposed to be handled by the {rr} part. I suspect my issue is in how I am handling the {rr} part when I am attaching the DynamicRedirector to the owning Restlet. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3054494
