The Tapestry URL encoding is not a problem for me in general, just for one
use case when i wanted to migrate a site to tapestry and keeping the same
URL (with accents, spaces, dashes, underscores and so on).
On Fri, 18 Jun 2010 17:20:36 -0700, Howard Lewis Ship hls...@gmail.com
wrote:
Tapestry
Makes sense. I must admit I was curious as to why T5 uses custom
encoding, so thanks for the explanation.
I'll use Nicolas's solution to override this behaviour.
On 19/06/10 01:20, Howard Lewis Ship wrote:
Tapestry does its own encoding because Jetty and Tomcat differ on
whether you get the
Thanks, I was curious as to whether I could do what I need using Page,
but in the meantime can get around it using Link.
On 18/06/10 18:02, Howard Lewis Ship wrote:
Currently, there isn't a good way to do what you want. I just hit a
similar problem for my client and am deciding on the right
Hi,
When using t:loop is there a method we can declare on the component that
Tapestry will call before each iteration ?
or is there another way to do this
Joel
On Sun, 20 Jun 2010 13:24:23 -0300, Joel Halbert j...@su3analytics.com
wrote:
Hi,
Hi!
When using t:loop is there a method we can declare on the component that
Tapestry will call before each iteration ?
or is there another way to do this
Use a getter/setter pair in the value
* Nicolas Bouillon nico...@bouil.org:
The Tapestry URL encoding is not a problem for me in general, just for one
use case when i wanted to migrate a site to tapestry and keeping the same
URL (with accents, spaces, dashes, underscores and so on).
It is a problem if you get called by other
Agreed, it would be good to have this as a configuration option.
On 20/06/10 19:20, Kai Weber wrote:
* Nicolas Bouillonnico...@bouil.org:
The Tapestry URL encoding is not a problem for me in general, just for one
use case when i wanted to migrate a site to tapestry and keeping the same
