Hi Thiago, I think what Tapestry needs is not necessarily a complete URL rewriting logic but a way to abstract from package and class names in the path. I am located in Europe and have done work for different clients in different countries and often the clients want to have meaningful URLs in their native language.
Given that you want to reuse the code you have (english packages/classnames) you can only solve this by heavy URL rewriting in apache. I think it should be the responsibility of tapestry to provide a hook for "translations" of package and classnames, as only this makes the i18n package complete. Regards, Markus On Thu, Mar 5, 2009 at 3:06 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > Hi! > > As a new committer, I would like to hear what do you think about this. > I'm working on a project that needs some URL rewriting. What about adding > this to Tapestry? I've been playing with it and it seems easy enough to be > my first issue in Tapestry. One example of open source's "scratching your > own itch". :) As I'll have little free time this month to work with other > issues, I guess this is good way to finally start contributing to Tapestry, > instead of just participating in the mailing list. > > Any thoughts? Does Tapestry really needs URL rewriting or should it be > developed elsewhere (in Ars Machina Project, for example)? > > -- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
