"Craig R. McClanahan" wrote: > The purpose is a performance optimization -- on subsequent requests to > "/servlet/foo", the container should find an existing mapping for the > servlet, so it will get called directly instead of going through the > invoker. > > > context.addServletMapping is called on every request to the > > InvokerServlet and shows up on performance profiles. Removing it did not > > affect the behaviour of InvokerServlet but it eliminated this > > performance hotspot. > > > > The intent is that the invoker only gets called once for any given > "/servlet/xxx" pattern. If it's actually executing the invoker again, > that's a bug (probably in the way the dynamically registered servlet > mapping's URL pattern is constructed). >
My apologies...the bug was in a change I had made in my tree. The performance optimization is working as implemented. Arvind -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
