Hi Thierry, That's exactly the problem. I have a security filter in front of the router.
The idea was that i would expose some permission based attributes associated with the route for use by the security filter.... but since the filter fires before i get there... well... chicken before the egg ^_^. I've hacked it in the mean time by storing a reference to the route in my 'application context' and manually call 'getNext' from the security filter to figure out which route is being invoked and hence get hold of the extra permission bits i added on. Really ugly... but it works right now. I'll mull it over the weekend. Regards, --KD ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2441232
