Hello All,
I was able to restart wicket8-examples and no it seems to accessible
WebSockets doesn't work
I'm going to fix it later today/tomorrow, please write here if you will
handle it earlier to avoid double efforts :)
--
WBR
Maxim aka solomax
Hi,
Those classes are in wicket jars but if they were not loaded by the
WebappClassLoader before the call to javax.servlet.Filter#destroy() then
the web container won't be able to load them inside #destroy().
It is some kind of security protection done by the web container to not
load any new
Hi all,
The problem where WicketApplication.destroy() hangs in 8.1.0 seems to be
fixed with WICKET-6603, however, I noted a new problem (less impacting for
me at least).
When quickly firing up embedded jetty, then opening a page and shutting
jetty down, I get exceptions in the page serializer.
I can see errors like this in runtime (Jetty only, not reproducible with
Tomcat)
I'm using Java8
Steps are:
1) mvn jetty:run-exploded
2) wait long enough
These errors seems to affect nothing, so I thought it is some jetty problem
On Thu, 29 Nov 2018 at 15:36, Martin Grigorov wrote:
> Hi,
>
>
Hi Martin,
Thanks for the quick response! This confirms my expectation that it had to
do with classloading.
Maybe the Async-Page-Serializer could handle this case?
For now I will just ignore these exceptions.
-Rob
On Thu, Nov 29, 2018 at 9:36 AM Martin Grigorov
wrote:
> Hi,
>
> Those
+1
Regards
Sven
Am 26.11.18 um 21:29 schrieb Andrea Del Bene:
This is a vote to release Apache Wicket 7.11.0
Please download the source distributions found in our staging area
linked below.
I have included the signatures for both the source archives. This vote
lasts for 72 hours minimum.
[
+1 tested random examples.
On 29/11/18 22:28, Sven Meier wrote:
+1
Regards
Sven
Am 26.11.18 um 21:29 schrieb Andrea Del Bene:
This is a vote to release Apache Wicket 7.11.0
Please download the source distributions found in our staging area
linked below.
I have included the signatures for
