>> >> I'm a bit short on time currently but what I meant with the fewer >> redeploys is not anywhere near this livereload jvm. Why? well, I dont think >> wicket is used that much in "small" projects but in rather larger ones. >> (I know DHL uses it for the GK-Portal - the solution any smaller customer >> uses to print labels and do shipments, thats no way a single server setup >> or trivial by the kind of forms they are having there) >> Even our own apps require a complete application server with EJB, JNDI >> etc. - like payara. >> If I would do a small app that has no need for outer things or is in the >> microservice area I would go with micronaut or quarkus already. >> No, what I mean was something that tapestry had included some time ago ( >> https://tapestry.apache.org/class-reloading.html ) - I must admit that I >> never used it, just read about it some time ago. I didnt think much of this >> feature to be honest till I got it for free when using micronaut. >> > > https://github.com/apache/wicket/blob/cd297625ad1df0399ebb5022d65e9c23a1965376/wicket-core/src/main/java/org/apache/wicket/protocol/http/ReloadingWicketFilter.java > >
Thats new to me! Will try it! I didnt see any trace of it on the documentation however...? https://ci.apache.org/projects/wicket/guide/8.x/single.html
