i think this could hide a problem and be hard to debug. if a field has changed but is readonly, we should explode and tell a readonly field was modified. if it is set to null but not allowed to be removed, we should explode as well, on an update, with a explanatory exception message.

if a field is protected and changed to a different value, i guess the phpcr layer will throw a hopefully meaningful exception.