I agree that it would be nice to be able to have an "index" page/class that can be accessed by navigating to that directory/package in the URL, while still having nested pages/classes accessible.
I hit this list about that a while back: http://www.nabble.com/forum/ViewPost.jtp?post=12846148&framed=y Perhaps if Tapestry's Big Brother approach (don't take me too seriously) of truncating redundancy in the URL is getting in the way, then maybe there could be a reserved class name that could be used to represent the package as a directory in the URL. For example, these classes: myapp.pages.menu.DefaultIndexClass; (or something) myapp.pages.menu.SubPage1; myapp.pages.menu.SubPage2; would be accessible at these URLs: www.mydomain.com/menu/ www.mydomain.com/menu/subpage1 www.mydomain.com/menu/subpage2 nirvdrum wrote: > > I ran into the same problem early on, and eventually just changed the name > of my pages. What I wanted was to be able to have a URL hierarchy like > the > following: > > http://localhost/orders > http://localhost/orders/view/101 > http://localhost/orders/edit/101 > > There was no clear way to have an "index" page, like Start functions as in > the root package. So, I naturally added an "Orders" page. All subsequent > page accesses were viewed as activation context, however, so that fell > apart. > > I sorta forgot about all this and hoped it had been fixed. If not, it'd > be > great if it could be, as it seems to be a tripping point for a lot of > people. > > -- > Kevin > > > On 2/10/08 3:52 PM, in article > [EMAIL PROTECTED], "Howard Lewis > Ship" <[EMAIL PROTECTED]> wrote: > >> 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] >>> >>> >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-Hint--Pages-in-subpackages-not-loaded%2C-if-page-and-subpackage-have-the-same-name-tp15390423p15419969.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]
