i had the same issue pop up after making some modifications to existing code that worked. turned out that one of the child classes was being referenced as a child from two different parent classes. this wasn't intended, it was just sloppy refactoring on my part.
for example: Knife child of Kitchen but also child of Drawer. for each child class, search for all references to that class in your project. the other way to do it is to comment out one child member in the parent class at a time and recompile/retest. you can narrow down the culprit that way, even if it doesn't end up being the same problem that i had. unfortunately, datanucleus exceptions are vague and sometimes even misleading. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
