The Start page is a special case, and should be relegated to the
"backwards compatibility" scrap heap. Recognizing the Start page is
its own Dispatcher and is probably being processed before your
CookieDispatcher.
What does CookieDispatcher do? It probably is a better fit for one of
the request handling pipelines.
On Fri, Mar 7, 2008 at 11:49 PM, Angelo Chen <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a page that I make it as 'start' page by
> configuration.add("tapestry.start-page-name", "home");
> and I have a dispatcher that is configured in the AppModule as follow:
>
> public static void
> contributeMasterDispatcher(OrderedConfiguration<Dispatcher> configuration,
> @InjectService("CookieDispatcher") CookieDispatcher
> cookieDispatcher) {
> configuration.add("CookieDispatcher", cookieDispatcher,
> "before:PageRender");
> }
>
> the dispatcher is never fired if I start the app like this:
>
> http://localhost:8080/app
>
> but it will fire if I do:
>
> http://localhost:8080/app/home
>
> Any ideal?
>
> Thanks,
>
> A.C.
>
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/t5%3A-dispatcher-not-fired-in-the-start-page-tp15912127p15912127.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
