Re: Potential Bug in DefaultNestedTree. Reproducible in Wicket examples

Hi Conny, If you create a PR with Java doc improvements I'm sure committers will be happy to merge it :-) On Wed, Dec 20, 2017 at 8:24 AM, Conny Kühne wrote: > Hi Sven, > > thanks. Maybe the javadoc of the tree classes should state this. It is not > obvious, e.g., why

Re: Potential Bug in DefaultNestedTree. Reproducible in Wicket examples

Hi, the tree implementation does what many other Wicket component do too: If you don't provide a model, it tries to find one in one of its parental components. (Note that the tree uses the model to store the expanded nodes.) Since you have a CompoundPropertyModel in the page, it will create

Potential Bug in DefaultNestedTree. Reproducible in Wicket examples

Hi, don't know whether this is a bug so I'll ask here first. In the wicket tree examples, when I get a WicketRuntimeException in the org.apache.wicket.examples.tree.BeginnersTreePage when I set a model to the page as follows: public BeginnersTreePage() { setDefaultModel(new

Re: i18n of ButtonElement for YES/NO button text

Hi, #getSttring() will lookup the value for the i18n bundle *once* and then the value (a String) will be stored in the Model. To make it dynamic you should use ResourceModel("the.i18n.key"). This model will load the value every thing you ask it by taking into account the content (locale, style,