Re: WicketURLEncoder.QUERY_INSTANCE result not (even near) same as java.net.URLEncoder?

2009-02-17 Thread Martin Makundi
Then maybe java.net.URLEncoder is more strict than the 'spec'... ok. ** Martin 2009/2/17 Johan Compagner : > 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>

Re: WicketURLEncoder.QUERY_INSTANCE result not (even near) same as java.net.URLEncoder?

2009-02-17 Thread Johan Compagner
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_IN

WicketURLEncoder.QUERY_INSTANCE result not (even near) same as java.net.URLEncoder?

2009-02-16 Thread Martin Makundi
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 expect