That's a very interesting situation. Actually, this is a decision between "full-ajax site" and "js-enhanced site", and for that question it doesn't even really matter which JS framework is used.
Server-side templating has always been a somewhat crazy idea (a hack, if you want - but then again, AJAX is a hack, too). It's surprising, that GWT can handle even this scenario well, and although it can't show its full set of advantages then, it's still a great choice. It's possible with GWT to eliminate server-side templating, if you want, because GWT makes it so easy to move the UI logic to the client. There are simply things that should live on the server side and things that should live on the client side. With traditional web development techniques, this decision was biased - now you can make a balanced decision. On Tuesday, October 9, 2012 2:10:16 PM UTC+2, David wrote: > > Some examples of pushback when trying to introduce GWT into a legacy j2ee > application > > -- 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/-/Jz9n8x8JjQwJ. 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.
