Thank you. I don't think either of those will work (though I will try them) as
* The update event is (I assume - but don't know as I can't reproduce the problem myself) being generated in the browser before the modal window is closed. * The canCallListenerInterface method is invoked after the component has been found - so it's already too late. Alex -----Original Message----- From: W Mazur [mailto:[email protected]] Sent: Monday, 25 June 2012 8:48 p.m. To: [email protected] Subject: Re: Suppress Ajax ComponentNotFoundException 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 <[email protected]>: > I have a problem that shows up intermittently (and never when I try to > reproduce it). > > We have ModalWindows that contain fields with associated > AjaxFormComponentUpdatingBehaviors on the onblur event. These work great > while the ModalWindow is open but sometimes events are received out of > sequence and we get an update event firing after ModalWindow is closed. > Wicket the throws a ComponentNotFoundException and the users sees the error > page. > > Is there some way I can prevent these happening, or at least suppress them? > All the field values will have been submitted when the ModalWindow was closed > so the extra update event can be safely ignored. > > Thanks > > Alex Grant. > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
