Further to the FYI, I've updated the ManagedObject api to implement the AOP skeleton. So it should be possible for Scott to intercept changes to the ManagedObject and persist them according to whatever required. e.g. * Persist on every change (simple) * Persist when the user clicks "apply" (implemented a bit like transactions in JavaEE) * Versioning (create a new version on every change or more lazily, e.g. only when the user chooses to save the changes) * etc. In fact, I have a feeling that some of the simpler processing has a lot in common with what POJO Cache does in terms of intercepting changes and allowing atomic updates/rollbacks? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995600#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...