Hi Sven, Thanks for pinpointing the redundant usage of PropertyModel.
I will definitely try to do a quickstart project. I need to be aware of creating quickstart, first though. Will try to follow this <http://this> . My project structure is bit complex. It will take some time to come up with the quickstart module (I am simultaneously looking at other issues at hand also). In mean time, I will share my observation with you. Can you please see if something clicks for you? The model attached to the form here is a new model every time the form is loaded. However the properties inside this model remains same. I mean the *ProductPageModel productItem* which is the model for the form is always a new object, however on submit I can see that the properties of these model remains same as first time. It seems that somehow the framework is caching the model's property and setting those in new model. Is it possible somehow? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Compound-Property-Model-to-a-form-is-not-getting-updated-tp4667114p4667137.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
