Hello Martin,
okay, it was a misunderstanding. I will file a new issue and attach the
quickstart.
Cheers,
Dirk
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Cannot-modify-component-hierarchy-after-render-phase-has-started-tp4676711p4676766.html
Sent from the Users
Hi Dirk,
I think Sven said that this is a bug (caused most probably by the support
for queueing components).
Please file a bug report in JIRA and attach the quickstart app.
Thank you!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Jan 16, 2017 at 7:47 AM,
Sven Meier wrote
> problem is that TestPanel.onConfigure() is called during render phase
> only, while in 7.4 it was (correctly) called in #beforeRender() (where
> hierarchy changes are still allowed).
Hi Sven,
to be honest I didn't get it. Livecycle stages of a component are
"initializing",
Hi Dirk,
problem is that TestPanel.onConfigure() is called during render phase
only, while in 7.4 it was (correctly) called in #beforeRender() (where
hierarchy changes are still allowed).
So I assume this is caused by WICKET-6216, component queuing might be
involved.
Regards
Sven
Hi Sven,
attached you can find a quickstart which demonstrates the problem. I've
added 3 test pages all with a TextField and a Panel with a TextField. For
each component, the model object is set at the onConfigure method. At the
first page both components are added to the page itself. At the
Hi Sven,
could it be that this belongs to
https://issues.apache.org/jira/browse/WICKET-6303? I'm not sure, but after
migrating to Wicket 7.5.0 we've got several errors belonging to this issue.
I'll try to provide a quickstart though.
Thanks,
Dirk
--
View this message in context:
Hi,
a quick lock on a 7.4-7.5 diff didn't reveal any change that has
something to do with checking the hierarchy.
Could you provide a quickstart, so I can find the difference?
Sven
On 12.01.2017 08:56, Dirk Forchel wrote:
Hi,
I would like to know why we shouldn't change the model object
