Re: ComponentNotFoundException and Clustering failover

Hi, On Fri, Mar 24, 2017 at 1:31 PM, Wayne W wrote: > Thanks Martin, > > I have a theory what this is, perhaps you could confirm? > > What I observe is the following with the replication: If I visit page A and > then visit page B, then kill the instance I am on the

Re: ComponentNotFoundException and Clustering failover

Thanks Martin, I have a theory what this is, perhaps you could confirm? What I observe is the following with the replication: If I visit page A and then visit page B, then kill the instance I am on the session is successfully failed over to the other node. Now I'm still looking at page B in the

Re: Does FormTester no longer pass the parameters to the page constructor when submitting the form?

Okay, turns out to have actually been fixed in 6.13, but caching was messing me up. It was the fix in AbstractBookmarkableMapper which makes it work. It seems like I can wrap the request mapper used in the tester to put the parameters back on in the same situation, which works for 1.5. TX @@

Re: ComponentNotFoundException and Clustering failover

Hi, Once the http session is replicated this method should be executed on the node that did not process the request org.apache.wicket.page.PageStoreManager.SessionEntry#readObject(). Here Wicket will either store the page(s) on the disk or will schedule them for storing. There is no much usage of

Re: Does FormTester no longer pass the parameters to the page constructor when submitting the form?

On Fri, Mar 24, 2017 at 7:58 PM, Maxim Solodovnik wrote: > In one of our projects I did Wicket 1.4 -> Wicket6 jump :) > Not that scared :) I tried 1.5 to 6.x a couple years ago, and after doing all the code changes, almost every test failed due to Wicket calling our code a

Re: Does FormTester no longer pass the parameters to the page constructor when submitting the form?

In one of our projects I did Wicket 1.4 -> Wicket6 jump :) Not that scared :) On Fri, Mar 24, 2017 at 3:46 PM, Trejkaz wrote: > On Fri, Mar 24, 2017 at 7:30 PM, Martin Grigorov > wrote: > > Hi, > > > > Wicket 1.5.x is not maintained anymore. Only

Re: Does FormTester no longer pass the parameters to the page constructor when submitting the form?

On Fri, Mar 24, 2017 at 7:30 PM, Martin Grigorov wrote: > Hi, > > Wicket 1.5.x is not maintained anymore. Only security related issues are > being processed. > Please update your demo app to 6.26.0 and if it still fails then create a > ticket at JIRA! 6.26.0 does appear to

Re: Does FormTester no longer pass the parameters to the page constructor when submitting the form?

Hi, Wicket 1.5.x is not maintained anymore. Only security related issues are being processed. Please update your demo app to 6.26.0 and if it still fails then create a ticket at JIRA! Thanks! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Mar 24, 2017 at

Re: Wicket is #3 in the JSON perf test by TechEmpower

Aww ;-) But yes those values were just to nice to be true ;-) kind regards Tobias > Am 24.03.2017 um 08:50 schrieb Martin Grigorov : > > It was too good to be true :-) > > TechEmpower said that they've had some mistake in the way they executed the > tests and this

Re: Wicket is #3 in the JSON perf test by TechEmpower

It was too good to be true :-) TechEmpower said that they've had some mistake in the way they executed the tests and this led to these good numbers. After fixing the errors the difference between round 13 and 14 are: Framework Test Type Old RPS New RPSChange in RPS Old