Hi,
This can happen if you change the component tree in Ajax request but forget
to update the client (i.e. forget to add some components to
AjaxRequestTarget). Later if you click on such stale component that has
Ajax behavior it wont be able to find itself at the server.
On Thu, Mar 21, 2013
Did anyone ever find a solution to this? We are having the same problem with
ComponentNotFoundExceptions.
Thanks,
Josh
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Suppress-Ajax-ComponentNotFoundException-tp4650209p4657428.html
Sent from the Users forum
the component has been
found - so it's already too late.
Alex
-Original Message-
From: W Mazur [mailto:wlodekma...@gmail.com]
Sent: Monday, 25 June 2012 8:48 p.m.
To: users@wicket.apache.org
Subject: Re: Suppress Ajax ComponentNotFoundException
I would try to add WindowClosedCallback
I would try to add WindowClosedCallback to Modal Window and remove
behavior(s) in that callback (unless you are going to reuse that
ModalWindow).
Another option: try to override Behavior's canCallListenerInterface()
Regards
Wlodek
2012/6/25 Alex Grant alex.gr...@unimarket.com:
I have a
