Hey Steve, You should not mount it yourself given the long session ID of 'a79c7348-6c8b- 4912-8cc7-3b4419344f7f' since that will change anyhow.
To understand how Wicket handles the URL mapping see the user guide's Chapter 10 "Wicket Links and URL generation" at: http://wicket.apache.org/guide/guide/single.html#urls I guess you want to provide your own IMapperContext? On Mon, Oct 6, 2014 at 12:31 AM, Steve Swinsburg <steve.swinsb...@gmail.com> wrote: > Hi all, > > I've been working on Wicket 1.4 for a while and in upgrading to Wicket 6 > I've found an inconsistency in the way URLs are handled, specifically in > the inmethod data grid but also the editable data grid. > > I have a particular context path that I need to maintain as the webapp > rendering is inside a portal type framework. > > I have taken the example webapps from both 1.4 and 6 and customised them so > they run in the framework. > > In Wicket 1.4, the page is mounted like: > > mount(new HybridUrlCodingStrategy("/data-grid/editable", > EditableDataGridPage.class)); > > and works fine. The URL is: > > http://localhost:8080/portal/tool/a79c7348-6c8b-4912-8cc7-3b4419344f7f/data-grid/editable.3 > > In Wicket 6, the page is mounted as: > > mount("/data-grid/editable", EditableDataGridPage.class); > ... > getRootRequestMapperAsCompound().add(new MountedMapper(mountPath, > pageClass)); > > and it does not work. It strips my leading context bits > (/portal/tool/UUID). > > I tried to mount it myself: > mountPage("/a79c7348-6c8b-4912-8cc7-3b4419344f7f", > EditableDataGridPage.class); > > But that goes into an infinite redirect loop if I mount it to the webapp I > want. If I mount it to a non wicket webapp, then that mount works fine. > > I am not sure how to restore the old URL mapping strategy. > > Can anyone help? > > thanks, > Steve >
