Hi Deacon, Thanks for the thanks!
With respect to that problem, I believe this is ISIS-1396 [1]. Yes, it is a Wicket viewer bug, which has always been there I think, but only now showing up with the new layout.xml. Anyway, it is fixed in 1.13.0-SNAPSHOT; perhaps you could build from source [2] and see if it addresses the issue. With respect to your query about updating(), what do you mean exactly by the "value of the changed object". I suppose if the object has changed because of a property edit, then you might mean the old/new values of that property? But the object might be changed because of an action invocation, in which case many of its property values will have changed. Perhaps what might help is to use @DomainObject(updatingLifecycleEvent=...). This is just a lightweight layer on top of the JDO lifecycle events, but to save you having to dig down to the JDO PersistenceManager. Maybe that would do the job for you? Alternatively, if you do need fine-grained visibility of changes in state, then there's the AuditingService3 API that you could implement. HTH Dan [1] https://issues.apache.org/jira/browse/ISIS-1396 [2] http://isis.apache.org/guides/dg.html#_dg_building-isis On 11 May 2016 at 11:59, Deacon Frost <[email protected]> wrote: > Hi, > > first of all thanks for the latest release and also the latest screencasts > -- Apache Isis keeps getting better and better!! :) > > I am using the wicket viewer with v 1.12.1. I use a custom > <Object>.layout.xml file copied verbatim from SimpleObject with tabGroups > displaying properties on different tabs. If I create a new object or update > value properties of an existing one, the titles of referenced objects get > reset to "undefined ...". If I just click on the tab-title, the screen gets > updated immediately to the correct values. (The behavior is correct as > expected when I remove the layout.xml-file.) Am I missing something or > might this be a wicket viewer bug? > > Also, is there any chance to get the value of the changed object in an > "updating()"-event? or do I have to resort to a custom publishing-module or > hook into jdoPreStore? > > Cheers, > > Deacon >
