Thanks Martin,
the parameters are the appendixes to page name (-ti123-ki345-ii789).
So i think i have to provide and encoder.
Cheers
Per
Yes, you need a custom IRequestMapper. You need to set it as root
mapper (see HttpsMapper and CryptoMapper examples).
You don't need custom IPageParametersEncoder unless you encode the
parameters in a special way. The url you showed below has no
parameters at all.
On Sat, Sep 3, 2011 at 5:25 PM, Per Newgro<[email protected]> wrote:
Hi,
we have some urls like in following pattern
http://domain.de/ShowTheme-ti123-ki345-ii789.html
With wicket 1.4 we built a BookmarkablePageRequestTargetUrlCodingStrategy
with matches(path) based on a pattern and encoding / decoding the url /
parameters.
Now i'm not sure how i have to migrate that to wicket 1.5.
I think i have to provide a IRequestMapper.
Is the getCompatibilityScore method the "equivalent" of matches(path)?
Do i have to provide a custom IPageParametersEncoder to encode / decode my
url / parameters?
Thanks for clearification
Per
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
