Re: RequestLogger - Different Page Memory Addresses

2022-01-31 Thread Sven Meier
Hi, session size is calculated by serializing the session. During session serializing your cached page is thrown away, see InSessionPageStore#writeObject(). So the next request will acquire the page from the persistent store: it's the identical page, just on a different memory location.

RequestLogger - Different Page Memory Addresses

2022-01-31 Thread Drummer, Matthias
Hello all, I stumbled across the following issue. If the RequestLogger is activated, I get a new page object with every request (including AjaxRequests). If disabled then the page object will remain the same across multiple requests. I am wondering why this is the case. I attached a

Re: Selenium testing

2022-01-31 Thread Ernesto Reinaldo Barreiro
Hi, Our app contains about 600 selenium tests... They are a pain to maintain even when we are trying to do things "the smart way". By this we mean: - We have some reusable wicket components. E.g. some AJAX table with lateral filtering facets. We roll in component marker CSS classes (e.g.

How to use the JavaScriptDeferHeaderResponse correctly?

2022-01-31 Thread Bas Gooren
Hi, We are experimenting with the JavaScriptDeferHeaderResponse, but out of the box it doesn’t work correctly for us. We are on wicket 9.7.0. On an Ajax call (e.g. link click), the response includes a ‘DOMContentLoaded’ event listener (which is not needed there). Since that never fires, any

Re: Selenium testing

2022-01-31 Thread Martin Terra
ma 31. tammik. 2022 klo 15.38 Wayne W (waynemailingli...@gmail.com) kirjoitti: > Hello all, > > Is anyone out there successfully using Selenium to do regression testing? > It seems with the latest version of Selenium you cannot add custom > selectors anymore (the idea turning on >

Selenium testing

2022-01-31 Thread Wayne W
Hello all, Is anyone out there successfully using Selenium to do regression testing? It seems with the latest version of Selenium you cannot add custom selectors anymore (the idea turning on getDebugSettings().setComponentPathAttributeName("wicketpath") ). So it just uses css selectors and xpath