Chuck,
Thanks soo much your clue got me on the right track. Dumb
mistake, I had left the destination java file in the wrong package.
The model was right, the _Sibling.java was correct but Sibling.java
was in completely the wrong location.
I was way too focused on the EOModel and worrying abo
The only time I have seen this happen was when either the model was
not getting loaded, or the class name in the model did not match the
actual class name in Java (package etc. included). Have you cleaned
the project after the changes? If it is somehow still picking up the
old classes wit
Yes the package name is there for Sibling in EOModeler.
I made a typo in the subject line the record is a
com.webobjects.eocontrol.EOGenericRecord instead of the "actual"
class it should be.
At 10:03 AM +0100 12/18/06, Alexander Spohr wrote:
did you add the package to the class-name in eomode
You have to have the fully qualified class name in the model (i.e.
com.myapp.Sibling). The simple class name isn't enough after you've
moved the classes into packages. Does that help?
John
On Dec 17, 2006, at 11:41 PM, Bob Stuart wrote:
After some refactoring classes into packages one of
