--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
I tried Roo and GWT integration some months ago and the results were
devastating. Not only was Roo (coupled with GAE) totally unstable -
the GWT support was that limited that it's better to write your own
stuff. At the beginning I though that AspectJ is cool. But now I think
that AspectJ will be the reason why Roo will fail (if it fails).
Or solution is the following setup:
- Backend: play framework (http://www.playframework.org/) / App Engine / Siena
- Clean rest / json api
- restygwt as json/gwt wrapper
- GWT for fat js clients
This setup works like a charm and is really rapid (superfast server
reloads / quick debugging and such). It also unites the best of both
worlds - a great backend server + gwt's development mode and it's
supercool way to develop large scale js apps....
Sorry for that negative opinion about Roo - prove me wrong :)
Best,
Raphael
> --
> 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/-/LgKvprYhY2kJ.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-tool...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
--
inc: http://ars-machina.raphaelbauer.com
tech: http://ars-codia.raphaelbauer.com
web: http://raphaelbauer.com