Wicket | modest library for moving between Well-Known Text | Map library

You could use UNION ALL in a sub-query and then GROUP BY.
This would give you zeros where there is no value. If this is a problem we could modify the presentation.
If you have another table with all the players we could us LEFT JOIN onto the three tables with
WHERE runs <>'' OR wickets <> '' OR catches <> ''

I doubt that Payara server provides wicketstuff artefacts.

Change your dependency to compile:

You create several objects via their constructors but they (most of them) are not used later. WicketTester uses the passed Application to find the others, i.e. it uses application#newSession() to create the Wicket Session, and application#newRequest() to create the Wicket Request. If you want to use mock versions of those then you need to create a custom MyTestWebApplication (that extends from MyWicketApplication), override these methods and set it up as a Spring bean.

WicketTester uses a new/fresh instance of MockHttpServletRequest for each request. You can get a reference to it via tester.getRequest() and call its #setAttibute()method before actually making the HTTP call (e.g. viaclickLink(), executeAjaxEvent()orstartPage()`).

So you could just use tester.getHttpSession().setAttribute(..., ...) before making the http call.

Some immediate things that could be causing this error are as follows:

First, it may be worth checking to make sure that the page store size hasn't been exceeded. If it has, it's possible that some pages from the store have been erased. getSession().getApplication().getStoreSettings().getMaxSizePerSession()

Second, I would advise checking whether or not the http session has expired. If it has, the pages of the session would've been erased from the page store. ((HttpServletRequest)getRequestCycle().getRequest().getContainerRequest()).getSession().getMaxInactiveInterval()

Finally, it could be an error which occurred during the process of saving the page to the page store. If that's the case, it's entirely possible that you cannot receive the page from the page store for that reason.

Also, keep in mind that Apache Wicket 1.5 was discontinued a while ago so everything regarding this is very old. It's possible that versions are mismatched or there are issues coming from something new. The best bet here would be to migrate to newer versions as soon as possible to avoid other obscure errors.

You need to add "wr": false to the attributes:

Try adding a wait there to make elements loaded before accessing them.
Instead of

There is no such functionality in current Wicket (9.8.0).

I'd also be hesitant to implement something like WicketMessageResolver! But it would be quite simple to implement with non-auto component (auto-components are all created from markup - ), i.e. with a custom Panel that has two Labels which models use Localizer.get() to get the localized values.

The default messages are defined at https://github.com/apache/wicket/blob/c6fde82ce9637c43753b59620b2f5551ad7f20fe/wicket-core/src/main/java/org/apache/wicket/Application.properties#L16

So, you need to override it in MyApplication.properties (must be next to MyApplication.class)