binding oddity?
binding oddity?
- Subject: binding oddity?
- From: Michael Gargano <email@hidden>
- Date: Tue, 2 Nov 2010 23:47:14 -0700
- Acceptlanguage: en-US
- Thread-topic: binding oddity?
I made a component yesterday that looked like this...
public class myComp extends ERXComponent {
public SomeEntity anObject;
}
anObject was bound in the wod and everything worked great. Later I added a method...
public class myComp extends ERXComponent {
public SomeEntity anObject;
public boolean isAnObject() {
return false;
}
}
this is where all hell broke lose. As soon as I added that method I kept getting KVC errors stating that no such key "anObject" existed on a binding that was just working. Can anyone explain this to me? I thought the search order was getBinding(), binding(), _getBinding(), _binding(), binding, _binding.
Does isBinding() squeeze into that ordering somewhere?
Is this a special case for binding to any boolean?
Thanks.
-Mike
_______________________________________________
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