Thiago,
I think a better statement would be "Tapestry is behaving exactly as it wants to." I guess this is a very unfortunate side-effect of the way Tapestry uses contexts. The design is fine when the web-app consists only of Tapestry, but that is seldom the case in real-world applications.

This still doesn't explain why I don't see this behavior when using a Start page. Can a start page not have activation context?

----- Original Message ----- From: "Thiago H. de Paula Figueiredo" <[EMAIL PROTECTED]>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Wednesday, June 25, 2008 10:49 AM
Subject: Re: T5 version 5.0.13 Index page suppressing other servlets?


Em Wed, 25 Jun 2008 11:32:05 -0300, kranga <[EMAIL PROTECTED]> escreveu:

I have Index.tml setup in my app root for the home page. I also have a servlet defined that listens to requests to /broker. There is no folder by the name of /broker. I find that Tapestry takes over the /broker request and serves up the home page! Unless there is a /broker folder with some file Tapestry takes over! Why is the Tapestry servlet over-reaching and is there any configuration to prevent it from doing so?

NOTE: This behavior is not present when I use Start.tml as my home page.

Tapestry is behaving exactly as it should. For any request, the Tapestry servlet filter (it is not a servlet), checks if the request can be handled by it. If it cannot, it just ignores it, giving a chance to other servlet filters and servlets to process the request.

Having an Index page, Tapestry receives a request to /broker and thinks that "broker" is the activation context for the Index page.

You can leave your Index page and tell Tapestry to ignore requests to /broker adding this lines to you AppModule:

public static void contributeIgnoredPathsFilter(UnorderedCollection<String> configuration) {
configuration.add("/broker/.*");
}

More details at the end of http://tapestry.apache.org/tapestry5/tapestry-core/guide/conf.html.

Thiago

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to