Thomas, I don't want to start a flame war here, but I really didn't
get your point about generating interfaces.
The goal is: "automatically convert JPA-annotated entities to GWT
Records" so it means that you have:
- @Entity class DomainEntity {...}
- GWT 2.1 Record interface
and you want to get both of them in a result:
- class RecordDomainEntity extends DomainEntity implements Record
{...}So, deffered binding will works perfectly for that case. Same with the annotation processing. Peter On 30. Aug, 17:56 h., Thomas Broyer <t.bro...@gmail.com> wrote: > On 30 août, 15:34, Peter Simun <si...@seges.sk> wrote: > > > I assume that Joe didn't want to implement Record interface in his JPA > > entity and wanted to have no GWT dependecies in the domain objects. > > This transformation should be done transparently, so he can work with > > RequestFactory without any additional work. GWT generator should do > > this work. > > without any additional work... except writing client-side GWT record > interfaces for his server-side JPA entities. And if I understood his > question correctly, that's the thing he'd like to automate with code > generation, and then deferred binding won't work. Case made. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
