Re: Dispatcher doesn't get called in default start page

Yep, using "before:RootPath" as a constraint when registering my Dispatcher did the trick. Thanks. Chris Lewis wrote: > Hi, > > This is probably correct. The handling of 'mapping' your app's default > page is also accomplished by a dispatcher. I /think/ its name is > 'RootDispatcher' but don't qu

Re: Dispatcher doesn't get called in default start page

Hi, This is probably correct. The handling of 'mapping' your app's default page is also accomplished by a dispatcher. I /think/ its name is 'RootDispatcher' but don't quote me on that - look for details in TapestryModule. If you want your dispatcher to fire first you'll need to place it :before th

Dispatcher doesn't get called in default start page

I've registered a Dispatcher class which works just fine except when the page name is not specified in the URL. So, if i put http://localhost:8080/mycontext/start the Dispatcher is called like expected, but if i access http://localhost:8080/mycontext/ although the same start page shows up the Dispa