Kodo 3 - inverse owner and order-column bug?

Question

Hi,
I have problems to move an object from one ordered list collection to
another.
This is the scenario:
A DocumentGroup is element of a tree, so it has children and a parent.
Tree ordering is important, so it must be maintained.
public class DocumentGroup
* @link aggregation
* @associates <{DocumentGroup}>
* @supplierCardinality 0..*
* @bidirectional <{de.daisi.model.DocumentGroup#parent}>
* @clientCardinality 0..1
* @supplierRole Children
* @clientRole Parent
private Vector children;
* @bidirectional
private DocumentGroup parent;
public void addChild(DocumentGroup newChild)
if (this.children.contains(newChild)==false)
if (newChild.isRoot())
newChild.setRoot(false);
if (newChild.getParent()!=null)
newChild.getParent().removeChild(newChild);
// Add child
newChild.setParent(this);
this.children.add(newChild);
if (this.tree!=newChild.getTree())
newChild.setTree(this.tree);
public void removeChild(DocumentGroup child)
boolean removed = this.children.remove(child);
if (removed)
child.setParent(null);
This is my mapping, the column DOCG_INDEX should be managed by KODO and
ist NOT mapped to a Java field.
<class name="DocumentGroup">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="pk-column" value="DOCG_ID"/>
<extension vendor-name="kodo" key="table" value="DOCUMENTGROUP"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="DOCG_LOCK"/>
</extension>
<field name="children">
<collection element-type="DocumentGroup"/>
<extension vendor-name="kodo" key="inverse-owner" value="parent"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-many">
<extension vendor-name="kodo" key="table" value="DOCUMENTGROUP"/>
<extension vendor-name="kodo" key="ref-column.DOCG_ID"
value="DOCG_DOCG_ID"/>
<extension vendor-name="kodo" key="order-column" value="DOCG_INDEX"/>
</extension>
</field>
<field name="parent">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.DOCG_ID"
value="DOCG_DOCG_ID"/>
</extension>
</field>
<field name="root">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="DOCG_IS_ROOT"/>
</extension>
</field>
<field name="tree">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.DOCT_ID"
value="DOCG_DOCT_ID"/>
</extension>
</field>
</class>
Now, if I move a document group several times (by invoking first
removeChild() on the source group and then addChild() on the target
group), the following error occurs:
kodo.util.FatalUserException: Attempt to set column
"DOCUMENTGROUP.DOCG_INDEX" to two different values: "0", "1" This usually
occurs when you map different fields to the same column, but you do not
keep the values of these fields in synch.
at kodo.jdbc.runtime.VRow.setObjectInternal(VRow.java:95)
at kodo.jdbc.sql.AbstractRow.setObject(AbstractRow.java:535)
at kodo.jdbc.sql.AbstractRow.setInt(AbstractRow.java:301)
at
kodo.jdbc.meta.OneToManyFieldMapping.updateInverse(OneToManyFieldMapping.java:364)
at
kodo.jdbc.meta.OneToManyFieldMapping.update(OneToManyFieldMapping.java:299)
at
kodo.jdbc.runtime.UpdateManagerImpl.update(UpdateManagerImpl.java:303)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:126)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:71)
at
kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:503)
at
kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:158)
at
kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:760)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:639)
at
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:411)
So, is there an error in my mapping configuration?
(I tried to leave out the "inverse-owner", but that does not change the
behaviour.)
Any help to make my tree editable with Kodo 3 would be great...

Answer 1

Abe White wrote:
Is there any way you could send us a test case that reproduces this
problem? Saying you have to move a DocumentGroup "several times" makes
me think it might be best if you sent us a program that shows exactly
what you mean. Just zip up your DocumentGroup class, metadata, mapping,
and a driver program showing the error and send it to
[email protected]
We'd really appreciate it.I sent a program for testing to the mail address above. So I hope you can
reproduce this error.