Too many variables to debug without seeing the actual code. The best thing for you to do would be to create a quickstart so that we could try to run it. Of course, most people find their problem while creating the quickstart.
On Tue, Jun 29, 2010 at 3:56 PM, jbrookover <jbrooko...@cast.org> wrote: > > To clarify even further, I did try to hack it so I changed the model of the > form directly (even though, I presume, it's all the same model propagated > up > and down the hierarchy). That also did not work. Nothing I've done will > force the Form to take a new object before its next submission. > > Thanks again! > > Jake > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Model-not-Updating-on-Multiple-Form-Submits-tp2272644p2272646.html > Sent from the Wicket - User 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 > > -- Jeremy Thomerson http://www.wickettraining.com
