Re: EOObjectNotAvailableException
Re: EOObjectNotAvailableException
- Subject: Re: EOObjectNotAvailableException
- From: Anjo Krank <email@hidden>
- Date: Thu, 27 Jul 2006 07:11:44 +0200
Am 25.07.2006 um 17:20 schrieb Watkins, Garry:
Really not the answer that I wanted. Personally, I think that it is a
bug in EO, if the relationship is defined as NOT mandatory, and it
encounters a EOObjectNotAvailableException it should return null.
However, I want to continue to use EOGenericRecords since it is
mainly a
reporting type application. Does anyone know where the Fault is
triggered inside the EO stack so that I might be able to trap the
operation with AspectJ? This would also require that I have the
EORelationship that triggered the fault.
If you have a key that points into nirvana, your data is broken and
should be fixed. EOF certainly should *not* return null in this case.
You could probably write an accessor to your relationship and trap
the exception there or get the committed snapshot in the EODBC or
EODB and patch it to be null. But the easiest route is to fix your data.
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden