> I think its the only one that doesn't make you deal with Keys > (including JDO) ... correct me if Im wrong here. You just use normal > object references to other entities and define them as @Parent's > @Child'ren or even @Component's so that its properties are embedded.
No reason why you can't do that in JDO. JDO itself doesn't want implementations to expose any vendor-specific "Key" class either, and that is solely down to implementation details on Google's behalf. You could have String or long identities in JDO easily enough and have all other fields as embedded. -- 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.
