There was a bug raised about this recently, so it may well be broken (ie never made to work with the JDO objectstore). Should be fixable.
In the meantime, however, an alternative (and probably better) is to use the new EventBus stuff, @PostsPropertyChangedEvent and the other @PostsXxx annotations. This will allow you to decouple the changes to some other service (rather than making it a responsibility of the object being updated). Will that work in your case? Dan On 10 June 2014 12:15, Erik de Hair <[email protected]> wrote: > Hi, > > Do I have to do more than creating a lifecycle callback method "public > void updating()" to do some actions just before updating to the database? > It looks like the updating()-method is never called after using the > edit-button in the wicket viewer. I can see the object being updated in the > logs. > > Thanks, > Erik >
