Re: Problem relationship with 2 eomodels

On Oct 29, 2009, at 5:15 AM, Pierre Gilquin wrote:

>
> <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> MIME-Version: 1.0
>
>
> I don't have choice=2C deployment is on WO 5.2.4
> Thanks


Btw, if it helps, you can embed the WO libs into your app so it does  
not matter what the target machine has as installed WO.   It will use  
the embedded WO libs instead.   Just set the classpath stuff correctly

Chad

>
> ----------------------------------------
>> CC: [email protected]
>> From: [email protected]
>> To: [email protected]
>> Subject: Re: Problem relationship with 2 eomodels
>> Date: Thu=2C 29 Oct 2009 06:51:35 -0400
>>
>> Have you tried this with latest Project Wonder and WO 5.3.3?
>>
>> On Oct 29=2C 2009=2C at 5:33 AM=2C Pierre Gilquin wrote:
>>
>>>
>>> Hi all=2C
>>>
>>> I have 2 eomodels one using MySql and the second
>>> Oracle.
>>>
>>> I have the following Entities : EntityAFromModel1=2C
>>> EntityBFromModel1and EntityCFromModel2
>>> EntityAFromModel1 has a to-many relationship with
>>> EntityBFromModel1.
>>> EntityBFromModel1 has a to-one relationship
>>> with EntityCFromModel2. This relation crosses the 2 models.
>>>
>>> When fetching EntityAFromModel1=2C I get the
>>> following error when accessing the to-one relationship to
>>> EntityCFromModel2 :
>>> java.lang.IllegalStateException: Server exception:
>>> The object with globalID _EOIntegralKeyGlobalID[EntityCFromModel2
>>> (java.lang.Integer)16823]could not be found in the database. This
>>> could be
>>> result of a referential integrity problem with the database. An
>>> empty fault
>>> could not be created because the object's class could not be
>>> determined (e.g.
>>> the GID is temporary or it is for an abstract entity).
>>>
>>> No SQL statement is send to the Oracle
>>> Database.
>>>
>>> The only thing I find for help is to fetch all
>>> EntityCFromModel2 at the Application start. But it is not very
>>> practical has
>>> EntityCFromModel2 has a lot of instances. Moreover=2C I am sure that
>>> it will still
>>> work a long time after the start.
>>>
>>> I thought also to implement awakeFromFetch in
>>> EntityBFromModel1 in order to fetch the instance needed for the
>>> relationship but
>>> without success.
>>>
>>>
>>> Do you have a better idea to make this relationship
>>> works between 2 models working ?
>>>
>>>
>>> Thank in advance.
>>>
>>> Pierre
>>> WO 5.2.4
>>> _________________________________________________________________
>>> La Suisse re=E7oit plus d'espace! Votre disque dur virtuel de 25 Go
>>> avec Windows Live SkyDrive.
>>> http://
>>> skydrive.live.com_______________________________________________
>>> WebObjects-dev mailing list
>>> [email protected]
>>> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>>
> 		 	   		 =20
> _________________________________________________________________
> La Suisse re=E7oit plus d'espace! Votre disque dur virtuel de 25 Go  
> avec Wi=
> ndows Live SkyDrive.
> http://skydrive.live.com=
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev