Hi Martin,
Thanks for your time and help.
Even though my 1.4 URLs contain pageIds, in the moment they were bookmarked
they were basically made stateless to my application, as the pageId lost
meaning. It is now just noise that gets misinterpreted by the migrated app
because of the dotted notation.
Hi Fabio,
The code looks OK!
Indeed it is not very easy to create really bookmarkable url!
The page has to be stateless to have url that will produce the same result
every time.
With stateful pages (pages with pageId in their url) there is a chance to
load something different than what you expect
Many thanks Martin,
I followed your advice and ended up overriding SystemMapper's mapRequest. I
decided to simply strip away the page instance instead of moving it to the
query string. It's just noise for me, after all. Quite rough probably, but
it seems to do the job in all the cases I tried.
Do
Hi Fabio,
You can create your own root request mapper that when detecting an old url
can either :
1) return a redirect with code 301 (Moved permanently)
2) just "move" the page id from the last segment to the query string
silently
Martin Grigorov
Wicket Training and Consulting
On Wed, Jun 11, 2
Hi all,
I am migrating an application from Wicket 1.4 to 6.15. This app makes use
of HybridUrlCodingStrategy, that I replaced with a MountedMapped using
UrlPathPageParametersEncoder.
The problem is that many users have old bookmarks of URLs generated by
HybridUrlCodingStrategy, in which the page
