Al Maw wrote: > n8han wrote: >> Previously I was able to mount bookmarkable paths including a slash in 1.3.0 >> snapshot, but now ajax request targets on those pages are failing. There is >> no exception logged; the browser redirects to >> resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js. > > As mentioned in the other e-mail, this should be fixed now. It was > caused by a small oversight in some refactoring, for which I apologise. > >> A separate problem is that request targets (ajax and regular) are no longer >> being processed under mounted bookmarkable URLs as they were up until now on >> 1.3.0. A mount like /code have targets like /code?wicket:... , but not they >> are /?wicket: as in Wicket 1.2. Is this intentional? > > Yes, this is intentional, and it shouldn't be causing any problems > (although it may get in the way of hybrid URLs, but we can fix that > post-1.3). > > The reason for this is primarily due to how AJAX HeaderContributions > work. CSS/JS/whatever needs to be relative to the URL for the page that > is being viewed. When an AJAX request comes in, if the URL for the AJAX > request at the same "../ depth" as the page view itself, then we just > construct resource links relative to that, and it all works. Otherwise, > we need to maintain state for the depth of the original page render. > This is possible, but less easy, and I don't want to mess with this > prior to the 1.3 release.
Turns out this is actually required. I've patched in an extra param in RequestParameters for the URL depth of the original page, and updated the interface listener request encoding stuff to cope. Hopefully we should now be able to trivially support hybrid URLs in future and everything should now work as intended. ;-) Let me know if you see any oddness. Al
