• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
faultWithPrimaryKeyValue, make sure it only returns a fault
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

faultWithPrimaryKeyValue, make sure it only returns a fault


  • Subject: faultWithPrimaryKeyValue, make sure it only returns a fault
  • From: Dev WO <email@hidden>
  • Date: Fri, 13 Oct 2006 09:50:19 +0200

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).


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.

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:)

Is there a way to request only a fault from a specific ec?
Or do I have to test for the specific attributes after I get the object? (If I can avoid this, it is really nice:))


Thanks

Xavier
_______________________________________________
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


  • Follow-Ups:
    • Re: faultWithPrimaryKeyValue, make sure it only returns a fault
      • From: Chuck Hill <email@hidden>
  • Prev by Date: Re: Tomcat deployment woes
  • Next by Date: Re: Trouble adding Project Wonder frameworks to XCode project
  • Previous by thread: Re: Tomcat deployment woes
  • Next by thread: Re: faultWithPrimaryKeyValue, make sure it only returns a fault
  • Index(es):
    • Date
    • Thread