Re: EOGenerator Relationships
Re: EOGenerator Relationships
- Subject: Re: EOGenerator Relationships
- From: Florijan Stamenkovic <email@hidden>
- Date: Wed, 17 Sep 2008 09:56:30 -0400
On Sep 17, 2008, at 06:18, David Avendasora wrote:
If it doesn't complain, it means that the code calling this method
is calling the _Invoice version of the method directly somehow.
I believe it is possible to do this using reflection. It however
should not be happening, unless you are purposely doing it.
It sounds like your inheritance tree is not what it should be
(Invoice does not subclass _Invoice). Or the method signature differs
(the _Invoice method takes an argument of a different type). Be sure
to check that out first. Like Dave said, @Override is a fast way to
address that.
Or, you are actually dealing with an instance of _Invoice, and not of
Invoice. Which would be weird, but possible I guess. In that case all
of the above would check out, but you'd still be calling the _Invoice
method.
When you created the instance you are now trying to update, did you
insert it into an editing context?
What's your point Dave? I don't see how this would influence the
runtime binding of methods.
F
_______________________________________________
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