Re: Ajax Link not resolving Wicket 6.4
Hi Sven, I just tried 6.5 and that's fixed it! Thank you very much. If you still want a quickstart to have a look at the code that demonstrates the issue in 6.4, then let me know. As it turned out It wasn't to do with my BookmarkableMapper sub class although the urls that the mapper handles have two segments e.g. http://localhost:8080/sale/pedro-moran-agronomia-297919.html The issue seemed to be in the UrlRenderer.renderRelativeUrl(Url) method in Wicket 6.4 which seems to have been updated in 6.5 Anyway the ServletWebResponse (SWR) was creating a fullUrl and also an encodedFullUrl when a fresh request from a unknown User Agent happens the two are different given that the encodedFullUrl contains the sessionId: e.g fullUrl: encocedFullUrl: As these two differ the SWR object was using the UrlRenderer to create a Relative Url this method took a parsed Url e.g: and produced the relative url which (in 6.4) had a double slash in it: Incidentally bookmarkable url for the page that the AjaxButton was on was: venta/laprida-recoleta-286358.html i.e. it had two segments [venta, laprida-recoleta-286358.html] rather than just one I'm not sure if this caused the double slash? Anyway let me know if you'd like the quickstart that shows the issue in 6.4 Thanks very much for fixing it in 6.5, Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving-Wicket-6-4-tp4655511p4655576.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax Link not resolving Wicket 6.4
Hi, Anyway let me know if you'd like the quickstart that shows the issue in 6.4 We have no need for it. Better create a quickstart for the next issue you'll find. Thanks Sven On 01/21/2013 10:27 AM, Simon B wrote: Hi Sven, I just tried 6.5 and that's fixed it! Thank you very much. If you still want a quickstart to have a look at the code that demonstrates the issue in 6.4, then let me know. As it turned out It wasn't to do with my BookmarkableMapper sub class although the urls that the mapper handles have two segments e.g. http://localhost:8080/sale/pedro-moran-agronomia-297919.html The issue seemed to be in the UrlRenderer.renderRelativeUrl(Url) method in Wicket 6.4 which seems to have been updated in 6.5 Anyway the ServletWebResponse (SWR) was creating a fullUrl and also an encodedFullUrl when a fresh request from a unknown User Agent happens the two are different given that the encodedFullUrl contains the sessionId: e.g fullUrl: encocedFullUrl: As these two differ the SWR object was using the UrlRenderer to create a Relative Url this method took a parsed Url e.g: and produced the relative url which (in 6.4) had a double slash in it: Incidentally bookmarkable url for the page that the AjaxButton was on was: venta/laprida-recoleta-286358.html i.e. it had two segments [venta, laprida-recoleta-286358.html] rather than just one I'm not sure if this caused the double slash? Anyway let me know if you'd like the quickstart that shows the issue in 6.4 Thanks very much for fixing it in 6.5, Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving-Wicket-6-4-tp4655511p4655576.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax Link not resolving Wicket 6.4
Hi, I've managed to produce a quickstart that reliably reproduces the problem I'm having. It looks like that it's to do with my BookmarkableMapper sub class, so I thought I'd try and diagnose the issue more precisely first rather than ask others to look into it, as it may simply be a bug in my code. Also I've not tried it with Wicket 6.5 yet. I'll post again when I've done both of the above. Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving-Wicket-6-4-tp4655511p4655542.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax Link not resolving Wicket 6.4
We're trying to improve on the double-slash issue. A quickstart would be helpful. Please try out with 6.5.0 which contains a fix for WICKET-4935: https://dist.apache.org/repos/dist/dev/wicket/wicket-6.5.0 Sven On 01/19/2013 04:13 AM, Chris Colman wrote: This looks very similar to: https://issues.apache.org/jira/browse/WICKET-4920 Which was I thought was fixed but might have been unfixed ;) Regards, Chris -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Saturday, 19 January 2013 2:02 AM To: users@wicket.apache.org Subject: Re: Ajax Link not resolving Wicket 6.4 Try to reproduce it in a quickstart, with any render strategy. If you succeed then please attach it to a ticket in Jira and we will investigate. On Fri, Jan 18, 2013 at 4:50 PM, Simon B simon.bott...@gmail.com wrote: Hi Martin, Thanks for replying. I take the url of the page for example: http://localhost:8080/rental/piedras-otra-afuera-de-bs-as-52368.html This is mounted using a MountedMapper in the Application object and resolves to a subclass of WebPage I copy the url, then boot up a fresh version of IE 9 from scratch and paste the URL into the navigation bar. Try with other browser too. Then I look at the source and see that the URLs that are being created for the AjaxButtons (called via: Wicket.Ajax.ajax) are like I mentioned in my original post e.g.: the above url which is called when I click the AjaxButton, does not resolve with the Wicket Servlet on the Jetty Container I guess it's got something to do with the // in the relative url. incidentally I'm also using a one pass render stategy set up in my Application class i.e. I'm not sure if that's pertinent or not. Try with the default render strategy too If you'd like any more information let me know Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving- Wicket-6-4-tp4655511p4655513.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Ajax Link not resolving Wicket 6.4
Hi I'm using wicket 6.4.0 on Jetty I've got mounted Bookmarkable page with various forms submitted via a AjaxButton (actually a IndicatingAjaxButton) When I go to the page by directly copying the url of the mounted Bookmarkable page into the nav bar or clicking the url from an email, the target url for the ajax requests triggered by the AjaxButton(s) does not resolve properly. The Wicket Ajax Debug Window goes red and an Error entry appears: ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Not Found Looking at the source there are several entries like the following: Looking at the net panel of firebug it seems that the url simply does not resolve with wicket: note the //wicket/page;jsessionid=yvcj55z9trey1omjoh9cqme7p Once I go back to the page, thereby having established a session with the application, things work fine, at that point the Wicket.Ajax.ajax call is as follows: the url resolves ok with wicket: note the /wicket/page rather than //wicket/page and the lack of ;sessionid= This happens in all browsers, I'm using Wicket 6.4.0 // 1.6.4, as far as I'm aware it was working in wicket 1.5 Has anyone experiencied similar issues, is there a fix. I don't want to jump the gun, but it appears like it might be a bug. Does anyone have any suggestions to help resolve this? Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving-Wicket-6-4-tp4655511.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax Link not resolving Wicket 6.4
Hi, On Fri, Jan 18, 2013 at 4:22 PM, Simon B simon.bott...@gmail.com wrote: Hi I'm using wicket 6.4.0 on Jetty I've got mounted Bookmarkable page with various forms submitted via a AjaxButton (actually a IndicatingAjaxButton) When I go to the page by directly copying the url of the mounted Bookmarkable page into the nav bar or clicking the url from an email, the target url for the ajax requests triggered by the AjaxButton(s) does not resolve properly. Can you give more details what exactly you do ? ^^ The Wicket Ajax Debug Window goes red and an Error entry appears: ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Not Found Looking at the source there are several entries like the following: Looking at the net panel of firebug it seems that the url simply does not resolve with wicket: note the //wicket/page;jsessionid=yvcj55z9trey1omjoh9cqme7p Once I go back to the page, thereby having established a session with the application, things work fine, at that point the Wicket.Ajax.ajax call is as follows: the url resolves ok with wicket: note the /wicket/page rather than //wicket/page and the lack of ;sessionid= This happens in all browsers, I'm using Wicket 6.4.0 // 1.6.4, as far as I'm aware it was working in wicket 1.5 Has anyone experiencied similar issues, is there a fix. I don't want to jump the gun, but it appears like it might be a bug. Does anyone have any suggestions to help resolve this? Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving-Wicket-6-4-tp4655511.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: Ajax Link not resolving Wicket 6.4
Hi Martin, Thanks for replying. I take the url of the page for example: http://localhost:8080/rental/piedras-otra-afuera-de-bs-as-52368.html This is mounted using a MountedMapper in the Application object and resolves to a subclass of WebPage I copy the url, then boot up a fresh version of IE 9 from scratch and paste the URL into the navigation bar. Then I look at the source and see that the URLs that are being created for the AjaxButtons (called via: Wicket.Ajax.ajax) are like I mentioned in my original post e.g.: the above url which is called when I click the AjaxButton, does not resolve with the Wicket Servlet on the Jetty Container I guess it's got something to do with the // in the relative url. incidentally I'm also using a one pass render stategy set up in my Application class i.e. I'm not sure if that's pertinent or not. If you'd like any more information let me know Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving-Wicket-6-4-tp4655511p4655513.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ajax Link not resolving Wicket 6.4
Try to reproduce it in a quickstart, with any render strategy. If you succeed then please attach it to a ticket in Jira and we will investigate. On Fri, Jan 18, 2013 at 4:50 PM, Simon B simon.bott...@gmail.com wrote: Hi Martin, Thanks for replying. I take the url of the page for example: http://localhost:8080/rental/piedras-otra-afuera-de-bs-as-52368.html This is mounted using a MountedMapper in the Application object and resolves to a subclass of WebPage I copy the url, then boot up a fresh version of IE 9 from scratch and paste the URL into the navigation bar. Try with other browser too. Then I look at the source and see that the URLs that are being created for the AjaxButtons (called via: Wicket.Ajax.ajax) are like I mentioned in my original post e.g.: the above url which is called when I click the AjaxButton, does not resolve with the Wicket Servlet on the Jetty Container I guess it's got something to do with the // in the relative url. incidentally I'm also using a one pass render stategy set up in my Application class i.e. I'm not sure if that's pertinent or not. Try with the default render strategy too If you'd like any more information let me know Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving-Wicket-6-4-tp4655511p4655513.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
RE: Ajax Link not resolving Wicket 6.4
This looks very similar to: https://issues.apache.org/jira/browse/WICKET-4920 Which was I thought was fixed but might have been unfixed ;) Regards, Chris -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Saturday, 19 January 2013 2:02 AM To: users@wicket.apache.org Subject: Re: Ajax Link not resolving Wicket 6.4 Try to reproduce it in a quickstart, with any render strategy. If you succeed then please attach it to a ticket in Jira and we will investigate. On Fri, Jan 18, 2013 at 4:50 PM, Simon B simon.bott...@gmail.com wrote: Hi Martin, Thanks for replying. I take the url of the page for example: http://localhost:8080/rental/piedras-otra-afuera-de-bs-as-52368.html This is mounted using a MountedMapper in the Application object and resolves to a subclass of WebPage I copy the url, then boot up a fresh version of IE 9 from scratch and paste the URL into the navigation bar. Try with other browser too. Then I look at the source and see that the URLs that are being created for the AjaxButtons (called via: Wicket.Ajax.ajax) are like I mentioned in my original post e.g.: the above url which is called when I click the AjaxButton, does not resolve with the Wicket Servlet on the Jetty Container I guess it's got something to do with the // in the relative url. incidentally I'm also using a one pass render stategy set up in my Application class i.e. I'm not sure if that's pertinent or not. Try with the default render strategy too If you'd like any more information let me know Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajax-Link-not-resolving- Wicket-6-4-tp4655511p4655513.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
