Thanks for trying to help, but no, there's no LDM involved here. I actually refactored the entire class and simplified things a bit. However, the problem is still occurring, not sure what's going on...
-----Original Message----- From: Jeremy Thomerson [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 4:44 PM To: users@wicket.apache.org; users@wicket.apache.org Subject: RE: PropertyModel of textfield not being updated Yes - it may be that eventSchedule isn't initialized at the time you create the PropertyModel, or that it's getting swapped out later, or similar. If it is, then this will make it always read the latest eventSchedule from your parent object, even if something else swapped it out. I haven't read the whole thread, but is it possible that you have a loadable detachable model that is swapping in a new object into your form model on each request? That would cause the situation I described above where your PropertyModel was initialized with one eventSchedule, and the form is using another one on your next request. Jeremy Thomerson -- sent from a wireless device -----Original Message----- From: "Michael Mehrle" <[EMAIL PROTECTED]> To: users@wicket.apache.org Sent: 4/21/08 5:58 PM Subject: RE: PropertyModel of textfield not being updated Sounds like a clever shortcut, but does it offer any benefit? Michael -----Original Message----- From: Igor Vaynberg [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 3:15 PM To: users@wicket.apache.org Subject: Re: PropertyModel of textfield not being updated new PropertyModel(eventSchedule,"foo") where is eventschedule referenced, how is it loaded? i would make that a property of the page and do it like this: new PropertyModel(this, "eventSchedule.foo") -igor On Mon, Apr 21, 2008 at 12:07 PM, Michael Mehrle <[EMAIL PROTECTED]> wrote: > I got a textfield: > > > > add(fooTextField = new TextField("foo", new PropertyModel(eventSchedule, > "foo"), Integer.class)); > > > > eventSchedule is a bean that has a foo field which is an integer. > > > > For some reason it's never being updated, although the field picks it up > when I programmatically call eventSchedule.setFoo(). > > > > I'm using this with AJAX and have all my component ids set and the > textfield added to the target. > > > > Any ideas? > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
