Sorry Erem, that was an earlier attempt to fix the problem in a quick and dirty way. It turned out to be far too quick and far too dirty. There is a newer bug to support inheritance that is currently open: http://code.google.com/p/datanucleus-appengine/issues/detail?id=25
I've merged the bug you referenced into that one. I'm working on it right now, targeting the next SDK release. Max On Thu, Oct 22, 2009 at 11:15 AM, Erem <[email protected]> wrote: > > The wiki states that "There is currently a bug preventing persistent > fields on superclasses from being saved to the datastore. This will be > fixed in a future release." > (http://code.google.com/appengine/docs/java/datastore/usingjdo.html) > > Meanwhile, the pertinent DataNucleus issue seems to have been closed > (http://code.google.com/p/datanucleus-appengine/issues/detail? > id=5&can=7<http://code.google.com/p/datanucleus-appengine/issues/detail?%0Aid=5&can=7> > ) > > Does this mean that this bug is resolved and the wiki out of date? Can > we safely persist subclasses and expect persistence annotated > superclass fields to also be persisted? > > Thanks, > Erem > > > --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
