On Jul 13, 2:16 am, Shawn Brown <big.coffee.lo...@gmail.com> wrote: > Hello, > > I'm seeing "Attempt was made to manually set the id component of a Key > primary key. If you want to control the value of the primary key, set > the name component instead." > > Do I have to fetch an object before updating it? > > I'm fetching (dataClass) from the store with detachable=true > then copying the data to a bean for serialization to my GWT client > when it returns, I create a new (dataClass) instance containing the id > of the original. > > Does that make sense? > > Should be trying something > likehttp://www.datanucleus.org/products/accessplatform_1_1/jdo/attach_det... > > Thanks for your good advice!
I am getting the same error in a similar, but different, scenario with JPA+DataNucleus+GAE ... I *think* it may be as a result that the PersistenceProvider believes that it is in control of the PK value allocation strategy, and not the application, and it is complaining because the app is setting the PK field (which would be a bad thing if the PP thought it was in charge of that field and it's contents)! That's what I think the route of my problem is ... sadly I am not sure how to resolve it! :) --~--~---------~--~----~------------~-------~--~----~ 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-java@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 -~----------~----~----~----~------~----~------~--~---
