Ahh, good point. Perhaps ValueProxy is what I'm looking for. I noticed mention of it in the RequestFactory_2_1_1 docs, but I didn't realize that it might be used that way. I'll have to give it a try. Thanks.
-Brian On Tue, Dec 14, 2010 at 10:55 AM, Thomas Broyer <[email protected]> wrote: > > > On Tuesday, December 14, 2010 4:38:54 PM UTC+1, Brian Reilly wrote: >> >> What I was hoping for in 2.1.1 is something with, I suppose, the >> functionality of AutoBean and the simplicity of use of @ProxyFor. >> Unless I'm missing something about AutoBean, it looks too cumbersome >> to use outside of a tool that does code generation. >> >> In my case, I don't need a proxy for my entities. I just need >> something to help make it easier to create and maintain appropriate >> DTOs that I can then use with GWT-RPC. I don't need the complexity of >> something trying to manage DAO methods, entity versions, etc. and the >> various requirements that puts on the entities. The proxy idea is fine >> for CRUD applications, but not as useful for presenting an entity with >> some actions that the user can perform that don't necessarily change >> the entity. > > Couldn't you then use a ValueProxy instead of EntityProxy? > > -- > 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. > -- 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.
