Hi Jens, just to make sure: > maybe I wasn't quite clear: on some startups my dispatcher is used (and than > is always used, which is what I want). On other startups (i.e. restarting > jetty/tomcat) the dispatcher is never used. Though log show, that it is > instantiated. But then it feels, as if it wasn't included in the dispatchers > chain of commands.
As far as I understand your mails, your "AuthorizationDispatcher" is certainly instanciated and contributed on every startup, but in about 50% of the times it feels like it is not doing its work. If so, could it be an error in the implementation of your "dispatch()" method? If you parse Strings in the request, maybe in the 50% not working, the Strings are presented a bit differently than in the other cases, urlencoded characters. Or it sometimes fails to load its dependencies (maybe SiteMap) or loads a mock implementation of that. To clarify could you post your dispatch()-method? Cheers nillehammer. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
