-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Too retrictive mapping validation?
PostPosted: Mon Dec 06, 2004 12:48 pm 
Newbie

Joined: Mon Dec 06, 2004 12:31 pm
Posts: 1
Hibernate version: 2

I got a problem with mapping two classes with the same name from two different libraries in Hibernate.
com.inceptor.somelib.Account
com.inceptor.someotherlib.Account

I get "duplicate import: Account"

These are mapped in hibernate.cfg.xml
<mapping resource="com/inceptor/somelib/Account.hbm.xml"/>
<mapping resource="com/inceptor/someotherlib/Account.hbm.xml"/>

However, it works fine if, I rename my com.inceptor.somelib.Account class to com.inceptor.somelib.SomeLibAccount.

Could it be the below change, has been made too restrictive?

Changes in version 2.1 final (12.12.2003)
-----------------------------------------
* detect and throw exception in the case of a duplicate property mapping


Top
 Profile  
 
 Post subject:
PostPosted: Mon Dec 06, 2004 1:01 pm 
Hibernate Team
Hibernate Team

Joined: Tue Sep 09, 2003 2:10 pm
Posts: 3246
Location: Passau, Germany
use auto-import=false


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.