Hi, We have a situation that comes up in our system infrequently where a node is garbage collected which has unsaved changes. (we have a check in the finalize method of a Resource subclass).
When we look in the repository the node actually does exist and the values are what we expect them to be. Is it possible to see what the unsaved changes are programmatically? (if not, we could just print out all of the properties of the node that has unsaved changes to the logs and then browse the repo with the sling explorer, but I'm wondering if there's a way to do it programmatically.) Rob
