>> All my modal windows use a single instance of ModalWindow that is >> instantiated in the base page and reused for all modal windows - >> hopefully that is ok. > >no, thats the problem. when modal B shows it removes the panel that >was inside modal A out of component hieararchy. so when you click >submit on modal A after modal B has been opened that button is no >longer in the component hierarchy and thus the error.
Doh! Reusing a single ModalWindow was my "genius" plan for a simple, reusable Modal Window architecture. Is there a way to 're-establish' modal A's ModalWindow in the hierarchy after Form B is closed? Apparently it's only not visible in Wicket's hierarchy - the form appears to still be in the DOM hierarchy because the form is still present in the browser. I have a modal close listener. Could I somehow reestablish Modal A in the wicket hierarchy when the listener callback is called? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
