Hello,

 >I extended the base router class and overloaded the createRoute method.
 >This allowed me to add my own properties on the route object.
That looks good.

 >I still haven't quite figured it out yet, but how does one get a 
reference to the current route that triggered the request?
At this time, the chosen route is not memorized, since the framework 
simply focuses on the routing task and does not take into account less 
simple scenarios where a request is routed across several routers, for 
example.
Having said that, you can update the attributes of the current request 
with a reference to the chosen route(s). this could be done by 
overriding the Router#getNext(Request, Response) which returns a Route 
(actually a TemplateRoute) instance.

Best regards,
Thierry Boileau

> Just to follow up my own post.
>
> I extended the base router class and overloaded the createRoute method.
>
> This allowed me to add my own properties on the route object.
>
> See:
>
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=16263
>
> I still haven't quite figured it out yet, but how does one get a reference to 
> the current route that triggered the request?
>
> Is there some sort of handle to it?
>
> Regards,
> --KD
>
> ------------------------------------------------------
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2440650
>
>

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2440886

Reply via email to