> Actually, it did not help. But thank you very much anyway, because it
> was in the entitypk.j the error occured. The problem was that our
> primary key was in a superclass, but the entitypk.j was not able to
> generate correct equals method for the subclasses. (All primary keys
> was equal...)
Glad I could help, even if it wasn't what I thought :-). We haven't
come across that one because our primary keys are in the subclass, this
may change soon though. Thanks for the warning.
BTW How did you fix it? Did you change the hashCode, equals and toString
XDtEjbPersistent:forAllPersistentFields superclasses attribute to true?
Thanks,
Kev
P.S. Watch out for the hashCode one because it does cause problems
when serialising.
Kevin Conner
Orchard Information Systems Limited
Newcastle Technopole, Kings Manor
Newcastle Upon Tyne, NE1 6PA. United Kingdom
Registered in England, Number 1900078
Tel: +44 (0) 191-2032536 Fax: +44 (0) 191 2302515
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
