Hello Jim, I've made some tests that I suspect to be too simple. I've just added a public "updateRoute" method on my application which I call between 2 loops of client calls, but I am not able to reproduce your case.
Could you send a reproductible test case (maybe in standalone mode)? What is your Restlet version? best regards, Thierry Boileau On Wed, Mar 19, 2008 at 1:49 PM, Jim Alateras <[EMAIL PROTECTED]> wrote: > I seem to be having a issue changing the routes on a Router after the > Application.createRoot method is called. I am using an Application in > the context of a Servlet. > > I set up a minimum number of routes during startup and then at some > later stage I replace those routes with new ones doing something like this > > Router router = ... > router.getRoutes().clear() > > router.attach(..., ) > router.attach(..., ) > > > Now when a new request arrives the Application seems to still use the > old routes to process the request, which seems to indicate that they are > cached somewhere. > > One I set up the routes do I need to do anything else to activate them > or notify other components of the change > > cheers > </jima> >
