[JCR-10] save() might create new transient properties

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Environment: Jackrabbit SVN revision 54847
• Assignee: Stefan Guggisberg
• Reporter: Felix Meschberger
• Created: 15/Oct/04 15:01
• Updated: 18/Oct/04 13:15
• Resolved: 18/Oct/04 13:15

Description

It seems that when a new node is saved through the parent node, new properties might get created, which are not saved. To persist those properties the new node must be saved again.

Example:

(Consider a mixin type "extVer" extending the standard type mix:versionable.)

Node node = parent.addNode("newNode", "nt:base");
node.addMixin("extVer");
// "mix:versionable" properties do not exist here

// save the new node
parent.save();

// now "mix:versionable" properties like "jcr:isCheckedOut"
// exist in the "node" but:
// node.getProperty("jcr:isCheckedOut").isNew() == true
// fix:
node.save();

If the last node.save() opertation would not be done, a RepositoryException would result if a node.checkIn() would be done immediately after parent.save().

This seems counterintuitive and seems like an error. I wonder whether the properties should not be added upon "node.addMixin" ? At least "parent.save()" should (or might I say must ?) not only add the properties but also save them.