Re: database backend best practice
Is the application Trackvia? ;-) On May 2, 7:43 am, Chris chris.b...@gmail.com wrote: I'm about to start a new application using GWT 1.6. I have a lot of programming experience, but very little with java. In my application I want to load a dozen or so different record types from a mysql database, send them to the client where the user can display/modify them in various ways, then send the data back to the database. I've looked over the basic DynaTable example and some jdbc examples and I've also read some about Hibernate. I'm trying to determine if Hibernate is worth the extra setup and configuration, vs a direct jdbc approach. Or is there a better solution I'm missing? If you were starting a new database GWT app with 1.6 what would be the best approach? Where best means both easiest to configure and easiest to deal with the code. Thanks for any suggestions, especially pointers to 1.6 tutorials. -- Chris --~--~-~--~~~---~--~~ 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-Toolkit@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 -~--~~~~--~~--~--~---
Re: database backend best practice
Unfortunately, GAE storage + GWT does not work together, since Domain classes are enhanced by DataNucleus and GWT RPC serialization process always fails on enhanced classes :-( As Gilead author, I am working on a dedicated adapter, to allow GWT to work fine with GAE data store, and hope a first release this month. Stay tuned ! Bruno On 3 mai, 13:33, Gilles B gilles.broch...@gmail.com wrote: It's interesting to have a look at google AppEngine solutions. If you planned to publish your GWT app using this environnement it's valuable to consider the technologies proposed like JPA, JDO...http://code.google.com/intl/fr/appengine/docs/java/gettingstarted/usi... My preference goes to JPA to start a new dev. Google example is mainly about JDO but JPA is the J2EE5 new API, JDO is a little old fashionned. Using App Engine this API utilisation is retricted to a subset (with google nucleus engine) but with your own env. you are free to use the full functionnalities set. Furthermore JPA is only an interface and you are free to select and change your background engine like Hibernate or Toplink. 2 very good and strong solutions. I can't see a real interest in a direct JDBC utilisation if you don't need to keep your project as small as possible with less jar. JPA or Hibernate can be used as a minimalist interface with good performances and no effort. Only describe your POJO classes and some annotations and he provide the column/fields mapping and basic CRUD methods. It's not necessary to define relations like ManyToMany, OneToMany... this way is close to JDBC but clean and easyest. Often I use Hibernate or JPA like a basic way to read/update my POJO. Working like an object oriented database or defining the navigationnal between classes is interesting but it require a deeper think to loading requests, foreign key management, sizes of data, lazy mode, request loading optimization, data collection transfer... this is not so easy to avoid beginners traps. You can choose this way latter. Gilles. --~--~-~--~~~---~--~~ 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-Toolkit@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 -~--~~~~--~~--~--~---
database backend best practice
I'm about to start a new application using GWT 1.6. I have a lot of programming experience, but very little with java. In my application I want to load a dozen or so different record types from a mysql database, send them to the client where the user can display/modify them in various ways, then send the data back to the database. I've looked over the basic DynaTable example and some jdbc examples and I've also read some about Hibernate. I'm trying to determine if Hibernate is worth the extra setup and configuration, vs a direct jdbc approach. Or is there a better solution I'm missing? If you were starting a new database GWT app with 1.6 what would be the best approach? Where best means both easiest to configure and easiest to deal with the code. Thanks for any suggestions, especially pointers to 1.6 tutorials. -- Chris --~--~-~--~~~---~--~~ 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-Toolkit@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 -~--~~~~--~~--~--~---
Re: database backend best practice
Hibernate will save you time and code in the long run. Sent from my BlackBerry® wireless device -Original Message- From: Chris chris.b...@gmail.com Date: Sat, 2 May 2009 06:43:42 To: Google Web ToolkitGoogle-Web-Toolkit@googlegroups.com Subject: database backend best practice I'm about to start a new application using GWT 1.6. I have a lot of programming experience, but very little with java. In my application I want to load a dozen or so different record types from a mysql database, send them to the client where the user can display/modify them in various ways, then send the data back to the database. I've looked over the basic DynaTable example and some jdbc examples and I've also read some about Hibernate. I'm trying to determine if Hibernate is worth the extra setup and configuration, vs a direct jdbc approach. Or is there a better solution I'm missing? If you were starting a new database GWT app with 1.6 what would be the best approach? Where best means both easiest to configure and easiest to deal with the code. Thanks for any suggestions, especially pointers to 1.6 tutorials. -- Chris --~--~-~--~~~---~--~~ 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-Toolkit@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 -~--~~~~--~~--~--~---
Re: database backend best practice
Dreamsource ORM can solve all problems you have when you use Hibernate. You don't need third party library for Dreamsource ORM. Please go to http://www.gwtorm.com/mail/Mail.html for an example. Jim http://www.gwtorm.com http://code.google.com/p/dreamsource-orm/downloads/list On May 2, 2:07 pm, Paul Grenyer paul.gren...@gmail.com wrote: Hibernate will save you time and code in the long run. Sent from my BlackBerry® wireless device -Original Message- From: Chris chris.b...@gmail.com Date: Sat, 2 May 2009 06:43:42 To: Google Web ToolkitGoogle-Web-Toolkit@googlegroups.com Subject: database backend best practice I'm about to start a new application using GWT 1.6. I have a lot of programming experience, but very little with java. In my application I want to load a dozen or so different record types from a mysql database, send them to the client where the user can display/modify them in various ways, then send the data back to the database. I've looked over the basic DynaTable example and some jdbc examples and I've also read some about Hibernate. I'm trying to determine if Hibernate is worth the extra setup and configuration, vs a direct jdbc approach. Or is there a better solution I'm missing? If you were starting a new database GWT app with 1.6 what would be the best approach? Where best means both easiest to configure and easiest to deal with the code. Thanks for any suggestions, especially pointers to 1.6 tutorials. -- Chris --~--~-~--~~~---~--~~ 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-Toolkit@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 -~--~~~~--~~--~--~---
