I've been thinking some more about your remarks and all my solutions are dead-ends: - use EntityProxies for all objects. Not possible because I cannot execute a complete RF server call in a single Hibernate session (because Hibernate runs one a different server encapsulated by web services) - use a mix of EntityProxy (for CRUD operations on a single entity) and ValueProxy (for list operations with more than one entry. This should theoretically work but some of the ValueProxy objects are not transmitted if they are part of an EntityProxy (I think someone else also had the same problem). - use only ValueProxies. This disregards most of the advantages that RF brings over straight RPCs. Maybe someone can comment on these scenarios? Does anyone have a good solution for using RF with a backend that is integrated using Spring and HttpInvoker services?
Cheers Jerome -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en.
