This may be a genuine error (i.e. you do have two entities that are
mapped to the same Java class). Although the fact that it goes away in
3.0 makes me wonder if there is a bug in 2.0.4 EntityResolver. In 3.0
it is much more robust to various cross-ClassLoader and arbitrary
naming issues. So check that only one entity is mapped to
cl.mydomain.User class, and we'll go from there.
On May 3, 2008, at 5:01 PM, Hans Poo wrote:
> I'm getting the next error (using cayenne 2.04):
> Can't perform lookup. There is more than one ObjEntity mapped to
> class cl.mydomain.User.
> The model was created with the cayenne 2.04 modeler, and that is the
> tool i'am using for maintenance.
> Moreover i've checked the model manually, and the class isn't double
> Can anyone give me some help ?
> I've tried using 3.0 libraries, and the error don't show up.
> -- The problem is that i'am force to use 2.04 and can't move to 3.0 --
> Open WebMail Project (http://openwebmail.org)
This archive was generated by hypermail 2.0.0 : Mon May 05 2008 - 04:29:25 EDT