Speaking strictly from my opinion and based upon a very similar experience, a lot of this is going to be a complete rewrite. If your original development did a good job of separating true "server" functionality from "client" struts functionality, then the server objects could be reused in some matter. But all of your UI and it's interaction is pretty much a do over. A lot of work, but I can say when our app goes into production in January, the support team is going to be very happy to say goodbye to the old Struts based product.
Later, Shaffer On Dec 9, 3:33 pm, sunitkatkar <[EMAIL PROTECTED]> wrote: > Hello, > > I have dabbled with GWT and understand how to build UIs and use the > Ajax features and RPC mechanism. > > I seek advise from you about the following > How should I go about if I were to reimplement an existing Struts, JSP > and handwritten Ajax web application in GWT? > The current application has > 1) many screens, > 2) user role based privileges that decide if a page is visible, if > buttons can be clicked, if a menu option is available, etc. > 3) uses Hibernate and some Spring (for logging) on the server side. > 4) uses struts tiles for layout. > > I understand that the layout will have to be a complete rewrite using > the GWT methodology of creating widgets and pages. > > Before I can embark on creating a prototype for evaluating if its the > right thing to do by adopting GWT, I wanted your advise and inputs. > > Thanks, > Sunit --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
