That's a very good point; I think it indicates that the approach taken by Tapestry when recognizing page names is too simplistic. Instead of trying to match forward, it should match backward, or perhaps create a Trie structure from the available page names.†
On Feb 9, 2008 1:37 PM, nillehammer <[EMAIL PROTECTED]> wrote: > Hello fellow users, > > I have just faced a little problem. I have searched the online documentation > of tapestry 5, this maillist and google for a solution. As I did not find > anything apropriate, I think this might be worth a mail. > > I obviously chose a very stupid packages/classes hirarchy: > eu.domain.app.pages.Menu.java > eu.domain.app.pages.menu.Subpage1.java > eu.domain.app.pages.menu.Subpage2.java > > This results in logical page names (and corresponding URLs): > menu > menu/subpage1 > menu/subpage2 > > Now clicking a link ...menu/subpage1 or .../menu/subpage2 neither of the two > pages ever loads. The page named menu allways shows up. I guess this > behaviour occours, because the remaining part of the URL after "menu/" is > handed to the page named menu as context rather than requesting the subpages. > So do not do this. > > Kind regards, nillehammer > > P.S. My standing ovations to the tapestry developers. They have given the term > "straight forward" a whole new meaning. Keep up the great work! THX > > --------------------------------------------------------------------- > 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]
