Em Tue, 10 Mar 2009 15:14:59 -0300, Howard Lewis Ship <[email protected]>
escreveu:
Yes, it does seem to be a partial solution as it will encourage people
to bypass Tapestry link creation facilities to generate the url they
want ... this comes down to something that could be done with a
servlet filter around Tapestry almost as well.
I don't want and I won't provide a partial solution. Andreas correctly
pointed out I overlooked part of the solution.
I think people were hoping for a full-featured solution, perhaps based
on annotations on
the pages.
The solution I'm writing has this possibility: anyone (including me) can
write an URLRewriterRule that does that.
The problem with partial solutions is there's an implicit commitment
to maintain this forever and there's the potential that it will
interfere with a more full-bore solution.
Agreed.
My goal with the built-in Tapestry "friendly" URL support was to have
Tapestry generate short names that were sensible to the *developer*
and similar to what a developer would create as a hand-tooled URL. It
was never to make the URLs sensible to end-users, or to make them
localized.
That's why I went to the Request wrapping path: to Tapestry and to the
developer, the URL is still the developer one. If some exception occurrs,
the exception page will show the original (developer) URL, not the
rewrittenone. I love the 1:1 class/URL relationship and I would never
break that.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
