1. I don't think so. They're meant to be used from the server side of GWT. For exposing server objects you use RequestFactory in combination with ValueProxy 2. I suggest you take a look at the "expenses" sample that comes with GWT.
http://code.google.com/p/google-web-toolkit/source/browse/#svn%2Ftags%2F2.4.0%2Fsamples%2Fexpenses You can see the Employee object in its server version here: http://code.google.com/p/google-web-toolkit/source/browse/tags/2.4.0/samples/expenses/src/main/java/com/google/gwt/sample/expenses/server/domain/Employee.java and its client representation here: http://code.google.com/p/google-web-toolkit/source/browse/tags/2.4.0/samples/expenses/src/main/java/com/google/gwt/sample/expenses/shared/EmployeeProxy.java RequestFactory intro here: http://code.google.com/webtoolkit/doc/latest/DevGuideRequestFactory.html 3. MVP won't really touch this since it's client side so it only sees proxy types So if you want to expose an AppEngine key, you would use KeyFactory to convert it to a string for the client and back to a string for the server. If you want to expose AppEngine's User object, you would use a ValueProxy instead of an EntityProxy, e.g., @ProxyForName("com.google.appengine.api.users.User") public interface UserProxy extends ValueProxy { String getNickname(); String getEmail(); } -- 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/-/Jwbi4juIGvkJ. 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.
