Thanks for pointing that out, Thiago - that hadn't occurred to me. I assume binding my own implementation in the AppModule should do that. Let's hope I'm not breaking anything fundamental in the process :)
Does anyone know why $0000 encoding was chosen over %-encoding? Thanks! Jochen On Jan 16, 2012, at 9:41 AM, Thiago H. de Paula Figueiredo wrote: > On Mon, 16 Jan 2012 15:21:10 -0200, Jochen Frey <joc...@jochenfrey.com> wrote: > >> Unfortunately (for me), I get this parameter passed from non-Tapestry code, >> and the rest of the internet uses %-encoding >> (http://tools.ietf.org/html/rfc3986#section-2), which makes this a problem >> for me, especially since this seems to be one of the few places where >> Tapestry gives me no way to intercept this behavior (typically Tapestry is >> GREAT about that). > > Actually, you can override the URLEncoder implementation with your own > implementation through Tapestry-IoC. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br --- joc...@jochenfrey.com +1.415.366.0450 @jochen_frey --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
