Re: why is DefaultNestedTree component treated as property within PropertyResolver ?

Hi Sven, I solved the problem related to PropertyResolver by this way: the model of my "Modal"-extension is now a "Model" (String) and not "CompoundPropertyModel". My next problem is: the tree isn't expandable. I'll try to fix it before I post another question. Thank you -- View this message in

Re: why is DefaultNestedTree component treated as property within PropertyResolver ?

Thank you both for your hints, I'm just testing with a MCVE. It seems the behaviour of the DFN depends to which parent it belongs (WebPage or Modal). It also seems to matter if the Modal is opened via an AjaxLink in a page or within a form -- View this message in context: http://apache-wicket.18

http://examples7x.wicket.apache.org/ is down

no text -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/http-examples7x-wicket-apache-org-is-down-tp4678272.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail:

Re: reusable Panel with Delete-Button and Confirmation Dialog (Bootstrap Modal), issue with page refresh

I guess I bit the hand that fed me... I attached the confirmation Modal to the Panel, and this was attached to the cell which belonged to the row which was deleted before. Will change my code tomorrow -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/reusable-Panel-with