Update of /var/cvs/applications/richtext/src/org/mmbase/versioning
In directory james.mmbase.org:/tmp/cvs-serv3969
Modified Files:
VersioningCommitProcessor.java
Log Message:
See also MMB-1632, cannot use still negative node number in node-fields
See also:
http://cvs.mmbase.org/viewcvs/applications/richtext/src/org/mmbase/versioning
See also: http://www.mmbase.org/jira/browse/MMB-1632
Index: VersioningCommitProcessor.java
===================================================================
RCS file:
/var/cvs/applications/richtext/src/org/mmbase/versioning/VersioningCommitProcessor.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- VersioningCommitProcessor.java 17 Mar 2008 10:08:10 -0000 1.5
+++ VersioningCommitProcessor.java 25 Mar 2008 09:41:51 -0000 1.6
@@ -11,7 +11,7 @@
* This commitprocessor copies on every commit the complete node to a
'versioning' table.
* @author Sander de Boer
* @author Michiel Meeuwissen
- * @version $Id: VersioningCommitProcessor.java,v 1.5 2008/03/17 10:08:10
michiel Exp $
+ * @version $Id: VersioningCommitProcessor.java,v 1.6 2008/03/25 09:41:51
michiel Exp $
* @since
*/
@@ -42,6 +42,8 @@
//clone this version to the versions builder
Cloud cloud = node.getCloud();
+ if (node.getNumber() > 0) { // TODO TODO
http://www.mmbase.org/jira/browse/MMB-1632
+
Node version = wv.createNode();
//increase the version of the current node
int newVersionNo = node.getIntValue(field.getName()) + 1;
@@ -58,6 +60,7 @@
// shit..., node fields don't like new nodes.
version.commit();
version.getCloud().setProperty(Cloud.PROP_IGNOREVALIDATION,
validation);
+ }
// could solve it by in this case using the _old values_ of the
node.
// But there are 2 bugs, which make this work around non-feasible:
// http://www.mmbase.org/jira/browse/MMB-1522.
_______________________________________________
Cvs mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/cvs
