> The objects have been detached. Ok. So the objects *have* been read from the datastore, since to detach them you obviously have to retrieve them first ... then detach them. And the exception is presumably coming from GWT, but then I don't see your stack trace so have no way more than guessing.
> This verbose log entry is really not very helpful, except perhaps to a dn > developer. Well it's very helpful to anyone who bears the JDO spec in mind :-P Things like "object lifecycle" ought to be understood when handling persistence., whether using JDO, JPA or any other persistence tool. Posting the stack trace would make more sense, since that tells everyone where your error comes from. Are you passing some detached objects to GWT at that point perhaps ? > I'm kind of amazed at the number of google hits > on this and similar errors. GWT+JDO+GAE/j+GEP sounds good, but it feels like > a house of cards and finger pointing. Well JDO is a JCP standard, and Google adopted it as part of their appengine. They also included GWT in appengine. It is for them to provide for interoperability between their chosen technologies; all I can do is point out the simple fact that JDO enhancement **for detachable** objects will add an Object[] field as per the JDO spec, and that you can make your classes non-detachable to avoid that particular issue (if you wish to do so). -- 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.
