so.
Daniel
Gesendet: Mittwoch, 29. November 2023 um 07:03 Uhr
Von: "Bas Gooren"
An: users@wicket.apache.org, ihmehlm...@gmx.de
Betreff: Re: Odd behaviour with StatelessForm and onInitialize()
Hi!
Can you share some code? (e.g. a quickstart which reproduces your issue)
It sounds
aniel
Gesendet: Mittwoch, 29. November 2023 um 07:03 Uhr
Von: "Bas Gooren"
An: users@wicket.apache.org, ihmehlm...@gmx.de
Betreff: Re: Odd behaviour with StatelessForm and onInitialize()
Hi!
Can you share some code? (e.g. a quickstart which reproduces your issue)
It sounds to me like
Hi!
Can you share some code? (e.g. a quickstart which reproduces your issue)
It sounds to me like in the one case you are dealing with a stateless page,
and the other a stateful page.
In general, with stateless pages, everything is initialized on every render
/ submit, because there is no page i
Thanks for the idea, but there doesn't seem to be any difference between adding
the components before or after calling super.onInitialize()
Gesendet: Freitag, 24. November 2023 um 13:56 Uhr
Von: "Martin Grigorov"
An: users@wicket.apache.org
Betreff: Re: Odd behaviour with St
Hi,
I don't have time to debug the problem right now but could you try
something: swap these two lines -
https://gist.github.com/TekkiWuff/824e820427c16e204bde68e95fd566a6#file-homepage-java-L25-L26
I.e. first add() the components to the page and then call
super.onInitialize()
On Thu, Nov 23, 202
Hello,
upon working with StatelessForms for the first time I stumbled up an odd
behavior in regards to when the corresponding models are updated.
Following setup:
The base for this is a wicket quickstart 9.15.0. I modified the two HomePage
files, which can be found here:
https://gist.github.co
