everybody has a say, your opinions help us shape ours -igor
On Fri, Oct 3, 2008 at 10:37 AM, Jeremy Thomerson <[EMAIL PROTECTED]> wrote: > I know I don't really have a say, but I'd be +1. I have had to get around > this several times by doing crazy hacks that sort the parameters the same > way (I didn't know about the UnitTestSettings hack). > > I'd add: should page parameters be an interface so that it's more > customizable for whatever the desired behavior is (sorting, etc....). Just > a thought. I haven't given it enough thought to weight the pros / cons. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Fri, Oct 3, 2008 at 9:49 AM, Nino Saturnino Martinez Vazquez Wael < > [EMAIL PROTECTED]> wrote: > >> Now your on it, theres also the mystery setting: >> >> UnitTestSettings.setSortUrlParameters(true); >> >> org.apache.wicket.protocol.http.UnitTestSettings, it actually makes your >> urls stable. But I'd be happy to see the class go away. And it could if it's >> implemented the way you suggest. Currently im using it to get stable urls. >> >> It's both there in 1.3 and 1.4 snapshot. And are used in various places >> around the framework (17 hits, with eclipse search). >> >> so +1 non binding:) >> >> >> Johan Compagner wrote: >> >>> Hi, >>> >>> i just got a complained that urls can be changed because the parameters in >>> an url (hybrid or something else bookmarkable) >>> are in 1.3 just random sorted because it is a HashMap en in 1.4 they are >>> sorted in natural order because we use a TreeMap >>> That last thing in 1.4 we do because of unit testing.... >>> >>> Cant we just use the LinkedHashMap? thats a cheaper one that TreeMap and >>> then the order is not natural but it is stable because >>> it is the order of insertion. >>> >>> johan >>> >>> >>> >> >> -- >> -Wicket for love >> >> Nino Martinez Wael >> Java Specialist @ Jayway DK >> http://www.jayway.dk >> +45 2936 7684 >> >> >
