Community
Participate
Working Groups
Build Identifier: 2.3.0-20110326.050514-69 When a subclass does not implement interface of parent class then the parent subclass does not get mapped to correct concrete class In the below case, for class C, field A in class AbsA resolves to interface P instead of class BA @mappedsuperclass abstract class AbsA <A extends W, B extends Y, C extends Z> impelents P, Q, R, serialzable { A fieldA; B fieldB; @manyToOne C fieldC; } @mappedsuperclass abstract class AbsB <EA extends A, EC extends C> extends<EA,BY,EC> impelements serialzable { Z fieldz; } @entity class C extends AbdB<BA,BC> implements serializable { } Reproducible: Always
Ofcourse Workaround is to make sure Class AbsB & C implement P,Q,R
The above workaround did not work in all cases. In addition to making sure all interfaces were implemented by subclass, I calso had to make sure the number of generic type arguments had to be same. @mappedsuperclass abstract class AbsB <EA extends A, EB extends BY, EC extends C> extends<EA,EB,EC> impelements serialzable { Z fieldz; } @entity class C extends AbsB<BA, BY, BC> implements serializable { }
Can you please describe the symptoms of the problem? i.e. what is the code you are running and how is the behavior different from what you expect?
Still awaiting symptoms of the problem. For now: Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
Switched to Hibernate due to poor support for complex generics and too much difficulty in getting issues resolved
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
