This is crazy, each time I made a project clean, the packages
declaration of the EO gets crazy.
Im gonna do something radical... start a new project.
You need to step back and look critically at the classes in your
Sources folder. You have something wrong in there. Nothing radical
is called for here.
To clarify here, like Henrique pointed out -- look at your exception.
The #1 thing I can recommend for anyone who is confused by an error --
READ THE ACTUAL EXCEPTION CRITICALLY.
[2008-9-29 13:13:30 COT] <WorkerThread0> java.lang.ClassCastException:
Empleado
at controlHorarios.app.eo._Empleado.fetchEmpleado(_Empleado.java:220)
That's all that matters, right there. Your _Empleado class is in the
controlHorarios.app.eo package, but you're getting a
ClassCastException to "Empleado", which has no package on it. That
means you have a class named "Empleado" that is not in a package, but
your _Class is in a package. If you look in your
controlHorarios.app.eo package, I bet you have an Empleado class
there, and I bet if you look in your (default) package, you have an
Empleado there also. EOF looks up classes by simple name (i.e.
packageless), which means you have two classes -- one in a package and
one not in a package and it's picking the wrong one because it doesn't
know which one should win. Delete the one that's not in a package (or
rather make sure your classes match your model).
This is debatably a limitation of Entity Modeler, but I didn't want to
deal with it because it introduces some nasty problems (deleting
people's Java files automatically is kind of a bad idea).
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
