Dear fomba, I highly recommend db4o and for you to forget about ORMs altogether. I asked a similar question on this forum a little while back: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/ef782ee131afbe60/b465803910bce469 .
db4o is absolutely, utterly, and splendidly awesome. The native query system is type-checked and done in your Java code so you don't have to worry about SQL errors etc. Also, you can configure it to receive only the parts of the object that you explicitly access (the other properties are set to null, numbers are set to 0) so that you don't have to load the entire object/system state every time, saving memory on the server side, and saving bandwidth when transferring the objects to the client-side via GWT-RPC, and thereby making an efficient persistence engine. Using it is incredibly simple, allowing you to save everything to and retrieve everything from a single file, to which you give any single name you like (and which is automatically created the first time). On May 31, 6:00 pm, fomba collins <[email protected]> wrote: > Hi, > I wish to know which of the following ORMs is the best to use with GWT > and why. > Regards > -- 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.
