The app I have been working on to test this is as small of an app that I can figure out how to write that utilizes RequestFactory and JDO at the same time (since it's the interplay between them that is the problem). Currently it only does 4 things to test this functionality:
- generate an entity on the client and send it to the server for saving in the datastore - generate a new entity on the server, save it in the datastore and send the new entity back to the client - count the number of entities in the datastore and send the count to the client - *send a list of all entities in the datastore to the client* All but the last work fine. It's only when I try to get an entity out of the datastore and send it to the client that the problem presents itself. In fact, I have commented out the code for the first 3 tests just to make sure there wasn't a problem with with the interaction of the different tests. Can you extrapolate on what you mean by using a DTO in this situation? Are you suggesting that I do not use the same object for client-server transfer as I do for server-datastore transfer? This method seems to be contrary to the method outlined at http://code.google.com/webtoolkit/doc/latest/DevGuideRequestFactory.html where the JDO and RequestFactory objects are one and the same. [RequestFactory] is designed to be used with an ORM layer like JDO or JPA on the server, although this is not required. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/O02ysUU8l_UJ. 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-web-toolkit?hl=en.
