Re: attempt to assign value to unknown key
Re: attempt to assign value to unknown key
- Subject: Re: attempt to assign value to unknown key
- From: Chuck Hill <email@hidden>
- Date: Thu, 17 Feb 2005 12:40:45 -0800
Assuming that George's suggestion was not the problem, did you try
quitting xCode, WOBuilder, and EOModeler before deleting (rm -r) the
build/ directory under the project? Sometimes the tools are rather
agressive about caching. Wouldn't you really rather be using WOLips
and Eclipse? ;-)
Chuck
On Feb 17, 2005, at 6:04 AM, George Domurot wrote:
This has happened to me several times. Usually when I have no
setMethod(Object value), event though I don't want anything actually
set. Adding the appropriate set method has always cleared up the
issue, event though the method doesn't actually do anything. In your
case, do you have a similar method, such as:
public setShowID(YouKeyObjectClass value){}
Adding this should do the trick.
-George
On Feb 16, 2005, at 8:50 PM, Nathan Hampton wrote:
This suddenly started happening to me, though in my case it's trying
to get the value. I first confirmed that the instance variable is
public (Note to Chuck: I re-typed it just to make sure). Then I
changed it to private and added accessors. Still no dice. I've
cleaned the targets both with Xcode's clean function and by deleting
all the build products manually, both before and after I put the
accessors in. I'm starting to get a touch frustrated, and I DON'T
want to start this project over.
Help!
--NCH
On 31 Jul 2004, at 5:23 PM, Art Isbell wrote:
On Jul 31, 2004, at 2:09 AM, Amorya North wrote:
Reason:
[<com.webobjects.appserver.WOComponent name: TabsForShows
subcomponents: null > takeValueForKey()]: attempt to assign value to
unknown key: 'showID'. This WOComponent does not have an instance
variable of the name showID or _showID, nor a method of the name
setShowID or _setShowID
The thing is, TabsForShows (the subcomponent I'm trying to call)
_does_
have a key called showID.
This can occur if the showID instance variable isn't public and no
public access methods exist. public instance variables don't
support good object-oriented design, so a protected or private
instance variable with public accessors is better.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development 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