Thanks for pointing to this issue Thomas! A follow up question: how do we distinguish between the sub-classes on the client?
JPA queries are polymorphic, so on the server the sub-classes are distinguishable. For single table and joint inheritance strategy JPA internally uses a discriminator column. The discriminator column could be used to distinguish between sub-classes, but the problem is it is not accessible even on the server side. Thanks a lot for your help! On Jan 4, 10:02 am, Thomas Broyer <[email protected]> wrote: > It's not a "bug", it's the way RF works (for now): there's no polymorphism > on the client-side, you get objects of the exact type declared in your > service stub or proxy (EntityProxy/ValueProxy) interfaces. > See alsohttp://code.google.com/p/google-web-toolkit/issues/detail?id=5367 -- 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.
