It is not a very special setup.
All devices run a Tomcat 9 servlet container. The servlet container runs
a webservice that is being used onsite by other systems and an
administration UI which is Wicket based. Both apps use the same H2
database, which is tiny (<1MB) and only contains configurat
As a simple test you could deploy a Wicket quick start to the device (make
sure it runs in deployment mode) to see if it still is slow. If that is the
case, you might need to look at the memory available for Tomcat. It might
need a bit more than it is configured with. Tweaking the memory settings
m
Jetty starts up quite a bit faster than Tomcat, so that’s an option too.
Jon
On Jan 2, 2023, at 12:51 PM, Martijn Dashorst
wrote:
As a simple test you could deploy a Wicket quick start to the device (make
sure it runs in deployment mode) to see if it still is slow. If that is the
case, you mig
from mobile (sorry for typos ;)
On Tue, Jan 3, 2023, 00:26 wrote:
> It is not a very special setup.
>
> All devices run a Tomcat 9 servlet container. The servlet container runs
> a webservice that is being used onsite by other systems and an
> administration UI which is Wicket based. Both apps
Hi there,
I am working to upgrade our Wicket apps to Spring Boot 3 and found that
10.0.0-M1-SNAPSHOT plays nicely with it.
It seems however, that
org.apache.wicket:wicket-bean-validation:10.0.0-M1-SNAPSHOT
is not available from
https://repository.apache.org/
while the module seems to be regu
Forgot to add that the same happens with wicket-devutils.
Regards.
On 2023/01/03 07:33:36 Francesco Chicchiriccò wrote:
> Hi there,
> I am working to upgrade our Wicket apps to Spring Boot 3 and found that
> 10.0.0-M1-SNAPSHOT plays nicely with it.
>
> It seems however, that
>
> org.apache.wic
