Thank you, Sven. In my code I was not calling LoadableDetachableModel.detach() after persisting objects to the database. Something I should have done.
As for the new events mechanism, I just had a look at the Migration to Wicket 1.5 and it looks like it's just what I need. The example from the wicket-example page is clear and concise. This will indeed "untangle" my code as you rightly put it. I shall read the Migration to Wicket 1.5 document as up until now I was more concern of having my code up and running and charging ahead with having my 1.4 code working on 1.5. Thanks for your help, Lucas -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxbutton-updating-forms-broken-persistence-strange-seemingly-unrelated-behaviour-tp4650049p4650112.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
