Then maybe java.net.URLEncoder is more strict than the 'spec'... ok. ** Martin
2009/2/17 Johan Compagner <jcompag...@gmail.com>: > as far as i know it does follow the spec specially for query portion and the > path portions. > > > > On Tue, Feb 17, 2009 at 08:26, Martin Makundi < > martin.maku...@koodaripalvelut.com> wrote: > >> Hi! >> >> The constructor WicketURLEncoder(Type type) explains a whole lot about >> the compatibility of QUERY_INSTANCE and java.net.URLEncoder. >> >> However, the results differ significantly. Specifically the >> "dontNeedEncoding" characters. We had a bit of a surprise integrating >> our app with another app expecting more strict encoding. >> >> Does this difference remain intentional? >> >> ** >> Martin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
