so you manually change your link to be at the mountpoint...
Where do you manually change it?
I was just pointing out that the 2 mount params must be in sync in wicket
else it doesn't work by default. If somebody makes a mistake an configures
it like i said
it goes wrong. The url will be encoded to something that when it is clicked
on will not be decoded.
That why it is dangerous to have the mount(string,coder) method and why it
is removed in wicket 2.0
(and it will stay that way)
URLs are build like that: preParams / postParams
while the first part of the preParams is the mountpoint...
i didnt consider it a bug, but a big feature as it also allows even the
most
complicated URL creation schemes as well as more enhanced CodingStrategies
Where do you use your coding strategies then for then?
Because or you don't use it completely for the encoding (setResponsePage(
Page.class))
or you don't use it complete for the decoding when a request comes in.
mount("/path/to/page2", new
> BookmarkablePageRequestTargetUrlCodingStrategy("", Page2.class,null));
is IMHO not a mountpoint but a pain - a mountpoint is a "short"
description
of what comes to a page
e.g: "/path/" would be enough here... everything of a URL is logic - and
that has to be handled by the appropriate class and not coded fixed into a
init function
That was just an example fine we use your example:
mount("/path", new BookmarkablePageRequestTargetUrlCodingStrategy("",
Page2.class,null));
Still doesn't work at all.
The encode will generate a "/" url (with nothing behind it if there are no
page params)
the decode will only accept urls that starts with "/path"
johan
