Are you sure the GWT long acts differently than a true Java long? My understanding was that as of 1.5 the long on the client correctly emulates a real long primitive.
No? http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thread/thread/3c768d8d33bfb1dcseems to be the thread that discusses the issue in your thread. I think the conclusion is (I only skimmed the thread) that JPA injects other code & that's where the problem comes in, because GWT doesn't know how to serialize that. On Sat, Apr 11, 2009 at 4:45 AM, Dean S. Jones <[email protected]> wrote: > > If you look at the Java source for BitSet, you'll see it uses an array > of long[].... JavaScript has no concept of long, so GWT has an > "simulation" of long, but it's not perfect. > > One could easily write an emulation class and serializers, but it's > not likely the bit math would be correct without totally rewriting the > classes using int. > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
