In our project, we are using the following: 1. Persistence with Hibernate through JPA. However, my preference is OpenJPA, Kodo (same as OpenJPA but commercial), Toplink (in this order) since they have more configuration features for performance. I have done a proof concept of OpenJPA using Autofetch (http:// www.theserverside.com/news/thread.tss?thread_id=48540) capability and it improved a lot on the number of queries. The extension is very minimal since OpenJPA has a very good API set (based on JDO).
2. We are using GXT using best practices (http:// googlewebtoolkit.blogspot.com/2009/05/widget-best-practices-widget- building.html) by wrapping widget in composite. Note that the composite in GXT is used in this case since the GWT composite does not work well with GXT. Even the GXT composite does not work well in most of the case so we end up simply wrapping the widget. GXT is not the perfect UI toolkit but it is the best so far since it gives you the ability to bind your widget with your model without having to modify your existing domain (through the BeanModelMarker). 3. We have built our MVC similar to GXT but using annotation instead for event name to have strongly typed token checked at compile time. We are using extensively deferred binding for example to support security (hide, disable widget or protect controller method). We are using EJB3 within Weblogic since it is a simpler model than before. GIN is also used on the GWT side. We have extended the gwt bean validation to truly use JSR-303 annotation for validation integrated with the GXT Validator. UIBinder is used for screen design but we had to extend it to support GXT. Note that you will need to modify GWT RPC to support ORM retrieval of your domain object (unless you use framework like Gilead). It is more efficient than what existing framework can do since there is no need to transfer state from original to DTO. It is necessary since the ORM instruments your object. We have done such enhancement as well on GWT RPC. Finally, we are following this pattern for caching: http://www.techhui.com/profiles/blogs/simpler-and-speedier-gwt-with GWT rocks! On 30 oct, 01:30, Satish <[email protected]> wrote: > Hello > > We are starting a new project to done using GWT and MySQL. > I have couple questions to choose which libraries to make the development > easier. > > 1. What kind of persistence library should be better to integrate GWT & > MySQL. Any suggestions on compatible ORMs? If at all necessary. > 2. Is it good to use an extra widget library like GXT/GWT-EXT/any other > libraries. > 3. Any other best practices for using GWT? like Google Guice etc.. > > Any help would be very grateful. > > Regards, > Satish. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
