On 09/09/2008, at 10:56 AM, Mike Schrag wrote:
More specifically: /** * This is Kelly Hawks' fix for the missing to one relationship.* Delegate on EODatabaseContext that gets called when a to-one fault cannot find its data in* the database. The object that is returned is a cleared fault.* We raise here to restore the functionality that existed prior to WebObjects 4.5. * Whenever a fault fails for a globalID (i.e. the object is NOT found in the database), we raise * an [EMAIL PROTECTED] com.webobjects.eoaccess.EOObjectNotAvailableException EOObjectNotAvailableException}. <br> * If you have entities you don't really care about, you can set the system property * < code>er.extensions.ERXDatabaseContextDelegate.tolerantEntityPattern</ code> to a regular expression * that will be tested against the GID entity name. If it matches, then only an error will be logged* but no exception will be thrown. * * @param context database context* @param object object that is firing the fault for a given to- one relationship* @param gid global id that wasn't found in the database. */public boolean databaseContextFailedToFetchObject(EODatabaseContext context, Object object, EOGlobalID gid) {
Ah, thank you! That always bugged me that it would throw an exception when the restricting qualifier had kicked in.
Now I can have peace ;-) er.extensions.ERXDatabaseContextDelegate.tolerantEntityPattern=\\w+ with regards, -- Lachlan Deck _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
