On Thu, Mar 5, 2009 at 8:04 AM, Kristian Marinkovic
<[email protected]> wrote:
> hi thiago
Hi!
> +1
>
> i have the same problem as described by markus. a fully
> internationalized web app should also have internationalized
> urls. not just urls implied by the class names.
I guess I answered it in my last message in this thread. :)
> i'd also wish to have positional parameters that i could set
> on a per page/link basis. example in german below:
>
> @URL("gebrauchtwagen/${car.id}/ausstattung/${equipment.id}")
> public class CarEquipment
> {
> }
If I've undersrtood correctly what you mean, this would break the
Tapestry philosophy of strong relationship between page and URL,
including name. Tapestry 4, as far as I can remember, doesn't have
this strong relationship and Howard thought that that wasn't the best
way to do it. On the other hand, the URL rewriting could solve at
least partly what you want. The other part (positional parameters)
could be solved by using onActivate(EventContext context).
--
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
