Thank you for the explanation. It did help.
However, in this case, the exception message could have been worded at least in JPA vocabulary; much like your lucid explanation.
So the solution is one of :
1. Make Parent a concrete class
2. Make Child extend Parent or convert to 'has a'
3. Change the object model such that this kind of situation will not arise.
-Prashant
[Message sent by forum member 'cprashantreddy' (cprashantreddy)]
http://forums.java.net/jive/thread.jspa?messageID=206583