Some of the pages are working now but the generated HTML code sure has some interest URLs:
<a wicket:id="faqCategoryLink" href="../../../////o/76429/c/22"> <h2 wicket:id="faqCategoryName">Getting started</h2></a> The href value has a few too many '/' slashes in it for my liking. Any idea why it might be adding so many slashes? The links work ok but look very strange. In 1.4 the links looked normal with no ../../ and ///// Any ideas what might be causing this? >-----Original Message----- >From: Chris Colman [mailto:chr...@stepaheadsoftware.com] >Sent: Wednesday, 21 September 2011 4:17 PM >To: users@wicket.apache.org >Subject: RE: BookmarkablePageLink works differently in 1.5? > >>i meant: >> >>mount(new MountedMapper("/content/home", HomePage.class, new >>MyCustomPageParameterEncoder()); >> >>-igor > >Arh! I didn't think of that. > >Would the PageParameterEncoder passed into the MountedMapper be used by any >BookmarkablePageLink instance when it encodes the URL or does the encoder >need to be separately specified for the BookmarkablePageLink? > >> >>On Tue, Sep 20, 2011 at 9:12 PM, Chris Colman >><chr...@stepaheadsoftware.com> wrote: >>> The pages are mounted but with 1.4 I mounted them all like: >>> >>> mountPage("/content/home"); >>> mountPage("/content/about"); >>> mountPage("/content/product"); >>> ... >>> >>> Any links to the page would suffix the parameters to the mount point >>like: >>> >>> /content/home/o/123 >>> /content/about/o/123 >>> /content/product/o/123/p/756 >>> ... >>> >>> With 1.4 I could mount them all in a similar way and let the page itself >>interpret the parameters according to what it expected. >>> >>> I guess in 1.5 I will have to mount each page in a way that explicitly >>declares its particular parameter composition: >>> >>> mountPage("/content/home/${dummy_o}/${o}"); >>> mountPage("/content/about/${dummy_o}/${o}"); >>> mountPage("/content/product/${dummy_o}/${o}/${dummy_c}/${c}"); >>> ... >>> >>> I kind of arrived at that conclusion yesterday. The problem I was having >>today was more to do with getting BookmarkablePageLink to produce URLs >with >>the /n/v/ style instead of the ?n=v style but I think I've almost worked >>that out. >>> >>> I have to simulate the name/value pairing of 1.4 /n/v style parameters >by >>outputting a dummy parameter name (where the name used to be in 1.4) and >>the real value. >>> >>> >>> >>>>-----Original Message----- >>>>From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] >>>>Sent: Wednesday, 21 September 2011 12:25 PM >>>>To: users@wicket.apache.org >>>>Subject: Re: BookmarkablePageLink works differently in 1.5? >>>> >>>>mountmapper also uses pageparameters, can you not mount your pages....? >>>> >>>>-igor >>>> >>>> >>>>On Tue, Sep 20, 2011 at 6:31 PM, Chris Colman >>>><chr...@stepaheadsoftware.com> wrote: >>>>> It looks like the parameter encoding/decoding is all done via the >>>>> interface: >>>>> >>>>> IPageParametersEncoder >>>>> >>>>> Which has only a single implementation which obviously encodes/decodes >>>>> the new 1.5 style. >>>>> >>>>> Would it be possible to provide a 1.4 legacy implementation of >>>>> IPageParametersEncoder to allowing upgrading a 1.4 wicket application >>to >>>>> 1.5 but maintain support for existing URLs that already exist for the >>>>> 1.4 built web application? >>>>> >>>>> Could the setting of the IPageParameterEncoder implementation be an >>>>> application or page setting? >>>>> >>>>>>-----Original Message----- >>>>>>From: Chris Colman [mailto:chr...@stepaheadsoftware.com] >>>>>>Sent: Wednesday, 21 September 2011 11:14 AM >>>>>>To: users@wicket.apache.org >>>>>>Subject: BookmarkablePageLink works differently in 1.5? >>>>>> >>>>>>It seems that in Wicket 1.5 BookmarkablePageLink's produce URLs that >>>>>>employ query parameters >>>>>> >>>>>>Eg., >>>>>> >>>>>>?name1=value1&name2=value2 >>>>>> >>>>>>instead of the directory style parameters of 1.4.x >>>>>> >>>>>>Eg., >>>>>>/name1/value1/name2/value2 >>>>>> >>>>>>While this may not be a problem for new Wicket applications the >>>>>>thousands of URLs of existing 1.4 Wicket applications are referenced >>>>>>from many existing websites and search engines on the web. >>>>>> >>>>>>Is there a replacement for BookmarkablePageLink in 1.5 that can >produce >>>>>>the 1.4 style URLs? (Or could BookmarkablePageLink take an option like >>>>>>'legacyStyle' that, when set to true, will create legacy (1.4) style >>>>>>URLs?) >>>>>> >>>>>>Regards, >>>>>>Chris >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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 >>> >>> >>> --------------------------------------------------------------------- >>> 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 > > >--------------------------------------------------------------------- >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
