Re: ClassCastException???
Re: ClassCastException???
- Subject: Re: ClassCastException???
- From: Guido Neitzer <email@hidden>
- Date: Thu, 2 Oct 2008 11:23:23 -0600
On 2-Oct-08, at 10:55 AM, David LeBer wrote:
On 2-Oct-08, at 12:46 PM, Guido Neitzer wrote:
On 2-Oct-08, at 10:37 AM, Awbrey Hughlett wrote:
The Basic and Specific EOs are linked to WOPopUpButtons. I want
the selection value (bound to aBasic and aSpecific) to be added to
the new instance of a Listing EO. I figured I didn't want a new
object on both sides of the relationship since aBasic and
aSpecific already have values set by the WOPopUpButton. That is
why I went with listing().addObjectToPropertyWithKey(aSpecific,
"specific"). Is my understanding of this wrong?
Ouch. Yes.
Bind the list to the array of Basic objects, the value to aBasic
(DON'T create an instance for that!!!), and the selection to
listing.basic. That should "just work".
Guido,
You meant bind 'item' to aBasic right?
Aeh, yes. Obviously.
And is the relationship to Basic from Listing to-one or to-many, the
name 'basics' seems to imply a to many.
Sounds like it. So that won't work either. That's why I said we need
more input. Letting us play a guessing game isn't really helpful.
cug
--
Real World WebObjects Bootcamp at the Big Nerd Ranch:
http://www.bignerdranch.com/classes/real-world_webobjects.shtml
_______________________________________________
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