Cannot modify component hierarchy after render phase has started

2017-01-11 Thread Dirk Forchel
Hi, I would like to know why we shouldn't change the model object within the configure phase for Wicket components. We're running our application with Wicket 7.4 and all works as expected. After migrating to Wicket 7.5 we get the following exception for different pages, mainly due to modifying the

Re: Log tailer sample?

2017-01-11 Thread Francesco Chicchiriccò
On 11/01/2017 16:39, Martin Grigorov wrote: Thanks for sharing, Francesco! Small feedback: - for us (Wicket users) it would be useful to have an url to the implementation of the log viewer (Apache Git or GitHub) Here you go:

Re: Log tailer sample?

2017-01-11 Thread Martin Grigorov
Thanks for sharing, Francesco! Small feedback: - for us (Wicket users) it would be useful to have an url to the implementation of the log viewer (Apache Git or GitHub) - mount the pages so that they have a nicer (user friendly) url instead of /wicket/bookmarkable/ Martin Grigorov Wicket

Re: AjaxFallbackLink in DefaultDataTable

2017-01-11 Thread Martin Grigorov
Hi, The reason is here: There could be just one HTML element with a given id. In your case you have many with "editLink". Wicket uses the markupId from the markup template if it is provided. If it is not provided then generates a unique one for each component. Remove id="editLink". Do you

Re: DropDownChoice models

2017-01-11 Thread Sven Meier
Hi, Im not sure I got this right but seems to me you still have to call "User.findOne(id)" for each user actually not, findOne() is called for the currently selected user only - that's the advantage. Regards Sven On 11.01.2017 13:16, Zbynek Vavros wrote: Hi, Im not sure I got this

Re: DropDownChoice models

2017-01-11 Thread Zbynek Vavros
Hey, I dont really think so because this kind of renderer will use these ("name" and "id) as property expression from User object. And then the DropDown selection itself would be of type User as well. I want the selection to be only user's ID, not the whole User object. The whole point is just to

Re: DropDownChoice models

2017-01-11 Thread Sebastien
Hi Zbynek, Maybe I missed something about your problem, but wouldn't this be enough? new ChoiceRenderer("name", "id") Best regards, Sebastien.

AjaxFallbackLink in DefaultDataTable

2017-01-11 Thread Christoph.Manig
Hello, I created a page to manage all users of my application. It contains a form for creating and updating users and a table below to delete and edit users. Here is the creation of the table and its columns: List> columns = new ArrayList

Re: DropDownChoice models

2017-01-11 Thread Zbynek Vavros
Hi, Im not sure I got this right but seems to me you still have to call "User.findOne(id)" for each user that touches DB (big nope) or create a Map that doesn't sound great either. Seems to me the best way is to fetch all users from DB and in ChoiceRenderer just iterate and get the

Re: DropDownChoice models

2017-01-11 Thread Sven Meier
Hi, as an alternative you can use a custom model instead: IModel target = ...; IModel userModel = new IModel() { public void setObject(User user) { target.set(user.getId()); } public User getObject() { return User.findOne(target.get());

Re: DropDownChoice models

2017-01-11 Thread Peter Henderson
Hi I've quickly knocked up this [1]. It's in Scala, I started with Java but got frustrated with just how slow I was. Note if you convert this to Java. You won't be able to use Java 8 Optional as it is not serializable (my biggest disappointment of java 8) so back to nullable model objects and

Re: Log tailer sample?

2017-01-11 Thread Francesco Chicchiriccò
Hi, FYI here are the results: http://blog.tirasa.net/apache-syncope-2.0-the-new-log-viewer.html Regards. On 05/01/2017 13:38, Francesco Chicchiriccò wrote: On 05/01/2017 13:28, Martin Grigorov wrote: On Thu, Jan 5, 2017 at 1:23 PM, Francesco Chicchiriccò wrote: On

DropDownChoice models

2017-01-11 Thread Zbynek Vavros
Hey, I have a DropDownChoice for list of users. I want to display user's name but bind user's ID. So far I have come to this (ugly) solution that can surely be improved: // create model with Long userId... final DropDownChoice usersDropDown = new DropDownChoice<>( "userId",