Re: Websocket redirect wrong url

2017-05-23 Thread Martin Grigorov
Hi, I'm afraid a quickstart would be needed to be able to tell what goes wrong there. The appearance of /wicket/ in the url looks like either BookmarkableMapper (responsible for urls like /wicket/bookmarkable/com.example.Page) or PageInstanceMapper (responsible for urls like /wicket/page?123) is

Re: Questions regarding Wicket 8 and lambda expressions for models

2017-05-23 Thread Martin Grigorov
Hi, On Tue, May 23, 2017 at 5:40 PM, Ihmehlmenn wrote: > Hello everyone, > > while trying out some of the very cool new features in Wicket 8, > specifically replacing PropertyModels with lambda expressions, I had a few > questions coming up. Most of them have been answered by

Re: Question about

2017-05-23 Thread Martin Grigorov
Hi, It is not very clear how your code looks like. Could you please provide more information the setup and how WICKET-6289 breaks it ? A quickstart application would be the best way to show us! You can share it via GitHub/BitBucket or even attach it to a ticket in JIRA! Thank you! Martin

Question about

2017-05-23 Thread Claudia Hirt
Hi all, there's something I came across when trying to migrate an application to Wicket 7.7. When using an anchor link like with autmatic linking activated (getMarkupSettings().setAutomaticLinking(true)) the AutolinkResolver breaks my hierarchy. This does not appear when encapsulating the

Questions regarding Wicket 8 and lambda expressions for models

2017-05-23 Thread Ihmehlmenn
Hello everyone, while trying out some of the very cool new features in Wicket 8, specifically replacing PropertyModels with lambda expressions, I had a few questions coming up. Most of them have been answered by the great guide provided, but following things are still a bit unclear to me: 1)

Websocket redirect wrong url

2017-05-23 Thread Peter Henderson
Hi all. I'm seeing a strange redirect problem which leads to a 404 Scenario. 1) User is on fat bookmarkable page [1] 2) Ajax onClick redirects to non bookmarkable SendMessagePage 3) SendMessage page uses websockets + background threads. 4) SendMessage page receives a websocket push event which