Using Node.save() after changing descendants of shareable nodes can lead to not all changes being saved

Consider the case where a node N1 is shared to another node N2, and where a session is used to change the descendants of N1, but then Node.save() is called on one of the ancestors of N2. In this case, the save operation does not
save the changes to the descendants of N1. Of course, the changes are still in the transient state of the session and will be saved upon the next Session.save() (so no information is lost nor is the persisted state corrupted in any way). For details, see the testModifyDescendantAndSave() and testModifyDescendantAndRemoveShareAndSave() tests in the ShareableNodeTest in the TCK.

Note that Node.save() has been deprecated in JCR 2.0, so the workaround is to simply call Session.save().