Hi Guys,
I agree with Howard. I think tapestry's behaviour of mapping URLs to page
classes is good enough to be left as is. It is pretictable and easy to use...
at least looking back from now.
The day I had the problem I was a little confused not having totally
understood everything. A hint in
I'm really opposed to this. It is One More Choice to Make and that's
a bad thing. Addiing lots of options that can be enabled or disabled
is a cop out, if a feature needs to be disabled, it is likely broken.
I'm only leaving in the "optimized request" stuff so that I can prove
its not worth using
Yeah. I just think following the friendly URLs to their logical conclusion
would dictate that the most common action would be mapped to that subroot
URL.
In this case, though, I really think just simply extending the Start class
convention to all packages would take care of the problem. You'd st
How about a flag in the app module to just turn off the friendly page
renaming altogether? Then if someone wants to have a
page structure like
report/status
report/reportstatus
report/statusreport
report/statusreport1
They can all resolve to unique pages.
For now, I'll add the contents of my ol
I agree this is a tripping point that needs addressing.
I tend to organize things a little differently, so I'd have an orders
package, with ListOrders, ViewOrders and EditOrders classes, thus:
http://localhost/orders/list
http://localhost/orders/view/101
http://localhost/orders/edit/101
On Feb
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&frame
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" pag
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 <[E
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.dom
