Thanks for the input Kevin... The T5 documentation states: The dispatcher here strips terms off of the path until it finds a known page name. Thus, "/mypage/27" would look first for a page whose name was "mypage/27", then look for a page name "mypage". Assuming the second search was succesful, the page would be activated with the context "27".
So obviously it is not working per the spec. ----------------- I remember running into that before. I spent some time trying to figure it out before deciding to just restructure my pages. The issue, as near as I can tell, is that Tapestry cannot distinguish between activation context and pages. Or rather, a preference is given to the former over the latter. My opinion, it should be the other way around, and thinking about it now, may not actually require that much of a change to the T5 code. -- Kevin On 1/22/08 7:15 AM, in article [EMAIL PROTECTED], "kranga" <[EMAIL PROTECTED]> wrote: > I'm using 5.0.7 > > I have a page called Admin.java in the root "pages" package. I also have a > page called Search.java in package "pages/admin/" > When I send a request to /admin, Tapestry correctly renders the admin page. > But when I send a request to /admin/search, I still get the admin page. How > do I get the Search.java page to be invoked? > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
