'duplicate column name'-Exception when using identical objects

Question

Hi all,
we're currently experiencing problems when using one single object instance for two different members of a mapped class. Here is an excerpt from our ToplinkMapping.java which shows the relevant parts:
public ClassDescriptor buildQuotationDefDescriptor() {
RelationalDescriptor descriptor = new RelationalDescriptor();
descriptor.descriptorIsAggregate();
descriptor.setJavaClass(de.hvb.ha.data.QuotationDef.class);
// Descriptor Properties.
descriptor.setAlias("QuotationDef");
AggregateObjectMapping commonQtyMapping = new AggregateObjectMapping();
commonQtyMapping.setAttributeName("commonQty");
commonQtyMapping.setReferenceClass(de.hvb.ha.data.type.VolumeDT.class);
commonQtyMapping.setIsNullAllowed(false);
commonQtyMapping.addFieldNameTranslation("commonQty_value->DIRECT", "value->DIRECT");
descriptor.addMapping(commonQtyMapping);     
AggregateObjectMapping wideningQtyMapping = new AggregateObjectMapping();
wideningQtyMapping.setAttributeName("wideningQty");
wideningQtyMapping.setReferenceClass(de.hvb.ha.data.type.VolumeDT.class);
wideningQtyMapping.setIsNullAllowed(false);
wideningQtyMapping.addFieldNameTranslation("wideningQty_value->DIRECT", "value->DIRECT");
descriptor.addMapping(wideningQtyMapping);
well, if we now assign one object-instance of VolumeDT to both members, i.e. like:
VolumeDT vol = new VolumeDT();
quotationDef.commonQty = vol;
quotationDef.wideningQty = vol;
we end up in the mentioned SQL-Exception, because toplink produces the following SQL-Statement:
UPDATE T_QUOTATIONTARGET SET WIDENING_QUANTITY = 0.0, WIDENING_QUANTITY = 0.0 WHERE …
but we've expected something like:
UPDATE T_QUOTATIONTARGET SET COMMON_QUANTITY = 0.0, WIDENING_QUANTITY = 0.0 WHERE …
Any idea we can prevent this behavior and still use one object-reference for both members??
Appreciate any help!

Answer 1

Thanks for the reply but unfortunately the mentioned change didn't fixed the problem. The sql-statement produced by toplink still looks like the one mentioned above. Moreover, the mentioned change couldn't be managed by the Workbench (which we use in the project to create the mappings), could it?
We currently use TopLink Version 10.1.3.3.
Since you've asked I post the relevant parts of the Parent-Mapping (and again its Parent), so sorry for the verbose post:
public ClassDescriptor buildQuotationORMWrapperDescriptor() {
RelationalDescriptor descriptor = new RelationalDescriptor();
descriptor.setJavaClass(de.hvb.ha.server.businessobjects.techapi.instrument.toplink.quotation.QuotationORMWrapper.class);
descriptor.addTableName("T_QUOTATION");
descriptor.addPrimaryKeyFieldName("T_QUOTATION.SEQ_KEY");
// Descriptor Properties.
descriptor.useSoftCacheWeakIdentityMap();
descriptor.setIdentityMapSize(300);
descriptor.useRemoteSoftCacheWeakIdentityMap();
descriptor.setRemoteIdentityMapSize(300);
descriptor.setSequenceNumberFieldName("T_QUOTATION.SEQ_KEY");
descriptor.setSequenceNumberName("Quotation");
descriptor.setAlias("QuotationORMWrapper");     
// Query Manager.
descriptor.getQueryManager().checkCacheForDoesExist();
OneToManyMapping quotationDefsMapping = new OneToManyMapping();
quotationDefsMapping.setAttributeName("quotationDefs");
quotationDefsMapping.setReferenceClass(de.hvb.ha.server.businessobjects.techapi.instrument.toplink.quotation.QuotationDefORMWrapper.class);
quotationDefsMapping.dontUseIndirection();
quotationDefsMapping.privateOwnedRelationship();
quotationDefsMapping.useCollectionClass(java.util.ArrayList.class);
quotationDefsMapping.addAscendingOrdering("orderBy");
quotationDefsMapping.addTargetForeignKeyFieldName("T_QUOTATIONTARGET.SEQ_KEY", "T_QUOTATION.SEQ_KEY");
descriptor.addMapping(quotationDefsMapping);
and now the parent of QuotationORMWrapper:
public ClassDescriptor buildPersistentInstrumentDescriptor() {
RelationalDescriptor descriptor = new RelationalDescriptor();
descriptor.setJavaClass(de.hvb.ha.server.businessobjects.techapi.instrument.toplink.PersistentInstrument.class);
descriptor.addTableName("T_INSTRUMENT");
descriptor.addPrimaryKeyFieldName("T_INSTRUMENT.INSTR_ID");
descriptor.addPrimaryKeyFieldName("T_INSTRUMENT.INSTR_KEYTYPE");     
// Descriptor Properties.
descriptor.useSoftCacheWeakIdentityMap();
descriptor.setIdentityMapSize(300);
descriptor.useRemoteSoftCacheWeakIdentityMap();
descriptor.setRemoteIdentityMapSize(300);
descriptor.setAlias("PersistentInstrument");
OneToOneMapping quotationMapping = new OneToOneMapping();
quotationMapping.setAttributeName("quotation");
quotationMapping.setReferenceClass(de.hvb.ha.server.businessobjects.techapi.instrument.toplink.quotation.QuotationORMWrapper.class);
quotationMapping.useBasicIndirection();
quotationMapping.privateOwnedRelationship();
quotationMapping.addTargetForeignKeyFieldName("T_QUOTATION.INSTR_ID", "T_INSTRUMENT.INSTR_ID");
quotationMapping.addTargetForeignKeyFieldName("T_QUOTATION.INSTR_KEYTYPE", "T_INSTRUMENT.INSTR_KEYTYPE");
descriptor.addMapping(quotationMapping)
I hope I don't missed any relevant parts. By the way, where could I log a bug for this issue and can it be considered a bug?
Thanks in advance!
Message was edited by:
user630939