Hi, >Another possible solution is wrapping the complete node, in an object that >detects changes also, but that is quite cumbersome because Node has already >65 methods or so. But we don't have to add yet another one, then.
I know it won't help much but here is what I think 1- it would be great if it was possible for anyone to add such generic behaviour under the bridge.(I think this is required to support node versioning) 2-I think most of the time nodes are read only. I would be in favour of adding the concepts of locking. normal nodes are readonly and you must be able to get an "editable" nodes node.getEditableClone(); editablenode.hasChanged() editablenode.replaceOrinigal() (if everything is ok) editablenode.revertToOldNode() something like this :) Did I mention that it would not help much?
<<winmail.dat>>
