Some examples of pushback when trying to introduce GWT into a legacy j2ee application
1) "We don't have time for a re-write" 2) "this is a website not an application" 3) "servlet template engines are sufficient for most UX and the rest can be done in javascript" 4) SEO requirements 5) I18n stuff needs to be in our familiar message.properties 6) UI designers don't want to live in hosted mode It's my observation that most J2EE developers who fight against GWT change their minds when they are asked to write jquery or native javascript. You'll however have to provide them with a easy way to inject gwt components into their servlet templates. Some things to consider: 1) consider consuming a smaller portion of a servlet template rather than the whole page 1a) design your MVP end to support a servlet template containing multiple sections earmarked for gwt (as independent widgets or working in unison) 2) add comments to the serlvet template file to reveal the entry point or presenter that will be boostrapped when the page loads 3) use http page requests instead of Place management when jumping around to new locations ( a single entry point with MVP and code splitting works very well with this model) 4) Use UIB templates!!! 5) demonstrate the ability to Junit test presenter logic ( mockito , jukito ..) - in contrast to the 10s of thousands of lines of .js code that go unwatched David On Tue, Oct 9, 2012 at 6:05 AM, Richard <[email protected]> wrote: > A couple warnings. > > I<http://www.thehubsa.co.za/forum/index.php?app=hubmarket&do=view_item&item_id=40056>'d > suggest starting off slowly, rather than dumping the whole team onto GWT on > day 1. There are a ton of gotchas or WTF's that the good GWT devs likely > don't remember. Adding an intermediate layer can frustrate you if you're > used to bare-metal web dev, so you'll definitely get some pushback at some > point. > > Also, since Java's now considered a bit of an older language compared to > the dynamic stuff the cool kids are using, that can affect resourcing. Are > the cool kids happy to write Java for their front-end work? Are they happy > that it'll have a positive effect on their career and not paint them into a > corner? > > Personally, I love it. It can drive me nuts at times, but it gives me too > many benefits to ignore. Once you learn the intricacies, it's very powerful. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/R436N4yJOKQJ. > 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. > -- 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.
