I'm migrating my application to wicket7.x, but it is still running in
wicket1.5 in production and logging following error frequently and
throwing OutOfMemoryError later. I'm still analyzing wicket1.5 code for the
root cause of the memory leakage.
Is it an existing error with the wicket1.5.x? did
Hi.
It seems I found the problem.
I'm developing with Scala (2.12.1) and that seems to be the problem in this
particular case.
Setting the option for the behavior:
ends up as being rendered as a list: ["#menu-target"] instead of just
"#menu-target".
That seems to be because the Scala compiler
