On Tue, 16 Mar 2010 12:22:13 -0300, Mike Oestereter
<mike.oestere...@gmail.com> wrote:
I dont know how but I think 1) could be addressed by making tapestry
to "encode" action differently to say login-form in stead of
login.form or to adjust the handler - I'm sorry but I'm not up to
speed with the Tapestry internals.
You'd need to change how Tapestry generates event URLs. I don't think it's
worth the hassle.
But 2) I'm afraid is definitely a bug - I'll try and get the code for
org.apache.tapestry5.internal.services.URLEncoderImpl and make it work
better
It's not a bug, as Tapestry purposefully encodes URLs in a different way
to better support page activation context. You can override the URLEncoder
with your own implemenation through Tapestry-IoC.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
