Hi, the Entities live in different DataDomains ... but the relation in the second DataDomain uses the entity-definition from the first DataDomain
My workaround for the moment: I defined a synonym in database for one of the 2 entities. So the entities have no longer the same name ... 2006/9/29, Andrus Adamchik <[EMAIL PROTECTED]>:
Hi Juergen, I assume you have 2 DbEntities with the same name, mapped to different ObjEntities (otherwise it wouldn't have worked in 1.1 either). Actually you can work around that issue by putting conflicting entities in two different DataDomains, as domains do not share EntityResolvers. This of course would prevent you from using any shared relationships... We can probably make it smarter in the future and qualify DbEntity name using DataMap name internally. Worth submitting a Jira request. Andrus On Sep 28, 2006, at 6:10 AM, Juergen Saar wrote: > Hi, > > we have two cases where we need the same entity in 2 DataMaps. > Both have the same Structure but live in diffent databases, > but have identical names. > > There is a controlled data exchange between these both entities. > > Till now, we used the version 1.1.4 and all worked fine. > Now, with version 1.2.1, in the second DataMap > relations pointing to this entity, bring back a javaclass > from the first DataMap. > > Is there anything I can do? > > Thanx > --- Juergen ---
