RE: Re: Using Asynch setOnResponse

Hi Jerome, Thanks for your reply. I realized that two things were causing a problem: 1) I was using the client net extension. This seemed to prevent async. Can we only use the internal client connector for this feature? 2) I thought the Async Get() was having no effect, when it was in fact

RE: Re: Dynamic Redirector

Hmm, digging in on this a bit more, I'm not sure it fully works for what I'm trying to do. The issue seems to be in the handling of the {rr} template. In other words, if I'm just redirecting a single URI to another (i.e. http://foo/a to http://bar/b), this approach works, but if I want to

Re: Re: Dynamic Redirector

I don't understand what you mean by the handling of the {rr} template. The approach I suggested, overriding getTargetRef, ignores the template argument entirely. --tim On Sat, Apr 27, 2013 at 2:54 PM, Grant gsing...@apache.org wrote: Hmm, digging in on this a bit more, I'm not sure it fully

RE: Re: Re: Dynamic Redirector

I don't understand what you mean by the handling of the {rr} template. The approach I suggested, overriding getTargetRef, ignores the template argument entirely. In my old code, I had: URI = hardcoded URI to resource Redirector redir = new Redirector(router.getContext(), URI + {rr},

Re: Re: Re: Dynamic Redirector

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. Also, the template argument to Redirector is ignored if you override getTargetRef. --tim On Sat, Apr