I'll consider overriding the URLEncoder service, but I'm not too keen on that as it will require me to check for changes in the std implementation on each Tapestry upgrade. Maybe the most reliable solution is to use context segments after all...
Thank you for your input. -----Original Message----- From: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 6. maj 2015 16:39 To: Tapestry users Subject: Re: Generate link to Tapestry page from another program On Wed, 06 May 2015 10:24:01 -0300, Poder, Jacob <jacob.po...@thermofisher.com> wrote: > Tapestry will throw an exception in URLEncoderImpl.decode before even > getting to onActivate in my page, so I can't do that. You can override the URLEncoder service with your own implementation if you really want to use commas. Or you could even do some URL rewriting. -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
