I may be dated on this with not keeping up on the latest gwt advances. The problems is a JPA or JDO augmented class is not directly portable (serialize/deserialize) from the GAE/J class to a GWT/js class like non-persistent classes are.
The classic DTO case (and not elegant) is to copy+paste your persistent classes into a shared model w/o the database twist and write the transporters. Many folks today have decided to skip the JPA layer and use Objectify for GAE database access. Its led to less headaches for some bloggers. -- 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.
