Re: faultWithPrimaryKeyValue, make sure it only returns a fault
Re: faultWithPrimaryKeyValue, make sure it only returns a fault
- Subject: Re: faultWithPrimaryKeyValue, make sure it only returns a fault
- From: Chuck Hill <email@hidden>
- Date: Fri, 13 Oct 2006 10:30:34 -0700
On Oct 13, 2006, at 12:50 AM, Dev WO wrote:
Hi,
I'm using faultWithPrimaryKeyValue to access an eo in a sharedEC.
I was using it thinking it would return only faulted eos in the
sharedEC, but after reading the java doc again, I think it may do a
fetch to access the object (if not available in the fault).
Yes.
So my issue is that I'm fetching object in the sharedEC with
specific parameters, but when I request an object through
faultWithPrimaryKeyValue, I can access object that doesn't conform
to the sharedEC specific parameters.
Yes.
For example, I can have an attribute "available" (boolean) on my
object and only put the ones with available=true in my sharedEC.
But I can still acces all the objet through my specific action
using faultWithPrimaryKeyValue which is not what I want:)
Yes. :-)
Is there a way to request only a fault from a specific ec?
No.
Or do I have to test for the specific attributes after I get the
object? (If I can avoid this, it is really nice:))
If you can get an EOGlobalID instead of creating a fault (see
EOKeyGlobalID.globalIDWithEntityName and EOEntity.globalIDForRow) you
can use EOEditingContext's objectForGlobalID "Returns the
EOEnterpriseObject associated with gid in this EOEditingContext or
its shared context, or null if no such object exists."
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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