AlMaw and i already talked and discussed about this.
and this is currently the way that we did see.
we could do it maybe a bit better by only looking at the beginning
or have a special urlFor method that doesn't do the relative path
prepending..
I already described the problem a few days ago (i think late last week on
the dev list)
it was really a major problem for me because if i get a mount request
(bookmarkable url thats mounted)
then i always do a redirect to the page so /mout/mout2/mount3 would become
/?wicket:interface=xxxx
But in the redirect to buffer the page is rendered with the mount. So all
the urls that are in the resulting page
had ../../../ (the 3 mounts) and then ?wicket:interface or /resources
that is ofcourse really wrong because ../../../ is just the complete root
because the resulting url isn't the mount
but a wicket interface that is already a root. So all my pages especially
with ajax didn't work on the first request
(a refresh in the browser and it did work) and i have to do a redirect
because else if i do stuff with ajax on the page
and users then think i want a refrehs and they do that. Then it is just a
bookmarkable mount request again and they
loose there page with all the ajax changes
Maybe if matej finally makes its thingie that we keep the mount but do a
redirect but then with:
/mout/mout2/mount3[pageid:versionid]
then it works (so hybrid urls with mounts)
johan
That's sounds very hacky to me:
redirectUrl.replaceAll("../", "")
Can you describe the problem so that we try to provide a better
fix (and hopefully AlMaw is listening to us ;-))
Cheers,
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
