Re: Forcing an object to be faulted?
Re: Forcing an object to be faulted?
- Subject: Re: Forcing an object to be faulted?
- From: Lachlan Deck <email@hidden>
- Date: Tue, 26 Jun 2007 06:12:05 +1000
Hmm, never mind. Some model munging was getting in the way...
On 26/06/2007, at 5:21 AM, Lachlan Deck wrote:
I'm following a keypath to an object that I know is in the database
but it's not being faulted in.
SomeObject : WOString {
value = object.site;
escapeHTML = true;
}
SomeName : WOString {
value = object.site.name;
escapeHTML = true;
}
// html
Site: <webobject name="SomeObject"/><br />
Name: <webobject name="SomeName"/>
// output:
Site: <java.lang.Class(10f067) Fault _EOIntegralKeyGlobalID[Site
(java.lang.Long)1090]>
<com.webobjects.foundation.NSKeyValueCoding$Null>
When logging the object returned from valueForKeyPath on my
component I get for the site:
<java.lang.Class(10f067) Fault _EOIntegralKeyGlobalID[Site
(java.lang.Long)1090]> type:class my.app.packages.Site
Any ideas why this isn't being faulted in? Work-a-rounds?
with regards,
--
Lachlan Deck
_______________________________________________
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