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

2017-08-22 Thread UlrichKnaack
hank you -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/why-is-DefaultNestedTree-component-treated-as-property-within-PropertyResolver-tp4678549p4678572.html Sent from the Users forum mail

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

2017-08-21 Thread UlrichKnaack
.1842946.n4.nabble.com/why-is-DefaultNestedTree-component-treated-as-property-within-PropertyResolver-tp4678549p4678564.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr

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

2017-08-18 Thread Bas Gooren
Hi Ulrich, My guess (based on quickly looking at your code on my phone): the DeafultNestedTree probably uses a model to store open/closed state or selected states. Since you don't provide it in the constructor, wicket automatically creates a property model since a parent component has a

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

2017-08-18 Thread Sven Meier
Hi, nested tree stores the expansion of its nodes in its model. You have added your tree to a component with a CompoundPropertyModel, thus the tree is inheriting its model from that parental component. You can override #initModel() and let it call #newModel() directly, this skips the

why is DefaultNestedTree component treated as property within PropertyResolver ?

2017-08-18 Thread Knaack, Ulrich
Hi, I'm trying to display a DefaultNestedTree (id="dataTreeView") within a Bootstrap Modal Instances of Service contain an ID that I use for retrieving a recursive data structure from database. The recursive structure is realized by instances of "RecursiveData" . See line 15 and method