Aha! I knew there was already a JIRA filed for this. Just voted got it.
On Jan 16, 2012, at 2:40 PM, David Canteros <davidcanteros....@gmail.com> wrote: > I have the same problem with Tapestry ULREncoder and the W3C standards > URLs. I think it must follow the standar way because this brings headaches > when the programmer dont known about the internal stuff of tapestry. > > I have filed a Jira for this https://issues.apache.org/jira/browse/TAP5-1803 > > Regards > David > > ------------------------------------------------------------------ > David Germán Canteros > > > 2012/1/16 Thiago H. de Paula Figueiredo <thiag...@gmail.com> > >> On Mon, 16 Jan 2012 15:45:52 -0200, Lenny Primak <lpri...@hope.nyc.ny.us> >> wrote: >> >> or rather *not* adhering to W3C standards :) >>> >> >> I agree that at least with query parameters Tapestry should use the >> standard URL encoding, except maybe for the cases of encoding null values. >> >> >> -- >> 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 >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@tapestry.**apache.org<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
