Re: Invalid JS src url for ajax behaviors - degradation after 6.17.0

2016-01-11 Thread Daniel Stoch
Hi, Thanks for your answer. I have tried to reproduce this problem in quickstart app and it seems that it is a problem in my application. Problem is related to Wicket-Ajax-BaseURL encoding, when parameter values contains "#" (eg. abx#xyz). In 6.17.0 there were some problems with these encodings

Re: Invalid JS src url for ajax behaviors - degradation after 6.17.0

2016-01-08 Thread Sven Meier
Hi, please create a quickstart and/or test case and attach it to a new Jira issue. This way we can dissect the problem. Best regards Sven On 08.01.2016 18:19, Daniel Stoch wrote: Hi, I have upgraded Wicket from 6.17.0 to 6.21.0. And there is some problem after this upgrade. I am using

Invalid JS src url for ajax behaviors - degradation after 6.17.0

2016-01-08 Thread Daniel Stoch
Hi, I have upgraded Wicket from 6.17.0 to 6.21.0. And there is some problem after this upgrade. I am using UrlPathPageParametersEncoder so my page parameters are encoded like: /param1Name/param1Value/param2Name/param2Value Sample scenario to reproduce this problem: 1. User enters a bookmarkable