I'm getting this error while loading my sessionFactory, I have tried to modify the mapping file unsuccesfully. Wonder if this is a bug. A similar bug appeared to be solved in version 2.0.....

Please help I'm stuck.

Hibernate version:
2.1.8
Mapping documents:
<!-- uni-directional many-to-many association to Programa -->
<set
name="programas"
lazy="true"
cascade="none"
table="convenioprograma_cop"

>

<key>
<column name="ncop_codigoempresa"/>
<column name="ccop_codigoconvenio" />
</key>

<many-to-many
class="co.com.unionsoluciones.sofia.cartera.model.bo.Programa"
>

<column name="ncop_codigoempresa" />
<column name="ccop_codigoprograma" />

</many-to-many>
</set>


Full stack trace of any exception that occurs:
net.sf.hibernate.MappingException: Repeated column in mapping for collection: co.com.unionsoluciones.sofia.cartera.model.bo.Convenio.programas column: ncop_codigoempresa
at net.sf.hibernate.collection.AbstractCollectionPersister.checkColumnDuplication(AbstractCollectionPersister.java:652)
at net.sf.hibernate.collection.AbstractCollectionPersister.<init>(AbstractCollectionPersister.java:163)
at net.sf.hibernate.collection.BasicCollectionPersister.<init>(BasicCollectionPersister.java:36)
at net.sf.hibernate.persister.PersisterFactory.createCollectionPersister(PersisterFactory.java:55)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:147)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:791)
at org.springframework.orm.hibernate.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:544)
at org.springframework.orm.hibernate.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:479)
at

Name and version of the database you are using:
MS SQL Server 2000

The generated SQL (show_sql=true):
No SQL Involved

The message is quite clear : the column ncop_codigoempresa is defined twice in your mapping file. You cannot use the same column for both keys of your many-to-many classes

Seb

I generated my mapping using middlegen, unfortunately I'm working with a legacy database. The mapping was generated that way, due to the fact that the referenced column belongs to the primary key of an entity that is related to all the entities of the model.

What can I do to solve this problem?

The problem is that the referenced colum is part of the primary key of both tables. That is the way the legacy database is designed. How can I avoid this.

I am still struggling with this problem. Please help.