Looks like serialization problem.
Does anybody know how it works?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problem-with-setWindowClosedCallback-tp3823361p4452909.html
Sent from the Users forum mailing list archive at Nabble.com
Does this problem still not documented?
Does anyone know a solution to this problem?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problem-with-setWindowClosedCallback-tp3823361p4452543.html
Sent from the Users forum mailing list archive at Nabble.com
move comments from first {1} setWindowClosedCallback - wicket(1.5)
> will use {1} instead of {2}
>
> It's a short example, and appending setWindowClosedCallback on the
> constructor level is not a solution - runtime parameters can be used into
> onClose method
>
>
> --
> Vie
ntext:
http://apache-wicket.1842946.n4.nabble.com/Problem-with-setWindowClosedCallback-tp3823361p3823895.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.a
before calling
window.close(target)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problem-with-setWindowClosedCallback-tp3823361p3823361.html
Sent from the Users forum mailing list archive at Nabble.com.
-
is doesn't work.
I tryed to move setWindowClosedCallback to constructor of the page - it
works, but how can I set WindowClosedCallback directly before calling
window.close(target)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problem-with-setWindo
