GWT integration to the cloud

100 views
Skip to first unread message

Amit

unread,
Jun 24, 2011, 5:53:41 AM6/24/11
to Google Web Toolkit
On Google I/O 2010, the VMware- Spring Roo tool was demonstrated. It
shows how one can quickly build a simple GWT application, where Roo
got only small and simple input and generated the entire code. A year
later, in one of the sessions of Google I/O 2011, a question was asked
regarding the collaboration of Google with VMware and the future of
Roo and its GWT plugin, however this time no real answer was given.
I wonder what is the status of Roo and the GWT plug-in from your eyes,
is it going to be a tool ready for production (for real applications
rather than demo only).
Also what is the reccomended way for integration of GWT with the cloud
for an entrprise application - e.g., is there any intention to provide
integration with the VMware spring V-Fabric products?
What is the future of GAE in that sense given the following report
http://gigaom.com/cloud/can-google-app-engine-compete-in-the-enterprise

Waiting for your comments,

Amit Kleinmann

Aza Tek

unread,
Jun 24, 2011, 6:19:07 AM6/24/11
to google-we...@googlegroups.com
Wonderful, wonderful question Amit. I'm all ears for a genuine answer on this one (NOT the usual "This is a springsource-team problem", when it's clearly so important to GWT).

Thanks


--
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.


David Chandler

unread,
Jun 24, 2011, 9:11:56 AM6/24/11
to google-we...@googlegroups.com
We've seen very little interest in GWT-Roo integration on this forum. It seems that most folks want to use GWT RequestFactory and Activities & Places without code generation, so we've chosen to prioritize effort around making that easier (for example, ServiceLocators and issues 5807, 6234 make it possible to inherit generic service methods vs. generate them).

Technically, GWT-Roo integration is structured as a Roo add-on so Spring needs to be at least involved in any further work.

Are you just wanting to kick the tires or have you already adopted Roo and have a really strong use case for GWT integration also?

/dmc
--
David Chandler
Developer Programs Engineer, Google Web Toolkit
w: http://code.google.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools

Aza Tek

unread,
Jun 25, 2011, 5:14:56 AM6/25/11
to google-we...@googlegroups.com
"It seems that most folks want to use GWT RequestFactory and Activities & Places without code generation, so we've chosen to prioritize effort around making that easier..."
It's not clear to me why we can't push for both: 
1. Use Roo to generate and MANAGE boilerplate code (Roo allows you chop and change your code). 
2. Make it easier to write gwt code.
Am I missing something?
Thx

Amit

unread,
Jun 27, 2011, 12:03:55 PM6/27/11
to Google Web Toolkit
Hi David,
What we are trying to develop is GWT based enterprise application, to
be deployed in the cloud.
For such a product we need:

1. Tools for easy deployment to the cloud as well as monitoring and
control the application while running in the cloud, something like
what the Vmware V-Fabric is promised to deliver.
2. GWT generator that will make it easy:
a. To generate the basis of the application make application changes
b. To migrate to a newer GWT version

In regard to Roo, we had lots of hopes that it would provide a
solution for the second requirement. However we faced with major
performance problems as soon as scalability in the number of model
entities was needed. From our point of view, there is a need for a
tool that can support more than 5-8 entities, while not necessarily do
all the required updates in real-time. Also better coordination with
the GWT team is needed in order to support requirement 2.b.
We initiated this session in the GWT forum in order to learn if there
is someone here who faced the same issues, and to understand what
people consider the best practices for in this environment.

Amit Kleinmann

On Jun 25, 12:14 pm, Aza Tek <azat...@gmail.com> wrote:
> "It seems that most folks want to use GWT RequestFactory and Activities &
> Places without code generation, so we've chosen to prioritize effort around
> making that easier..."
> It's not clear to me why we can't push for both:
> 1. Use Roo to generate and MANAGE boilerplate code (Roo allows you chop and
> change your code).
> 2. Make it easier to write gwt code.
> Am I missing something?
> Thx
>
> On Fri, Jun 24, 2011 at 3:11 PM, David Chandler <drfibona...@google.com>wrote:> We've seen very little interest in GWT-Roo integration on this forum. It
> > seems that most folks want to use GWT RequestFactory and Activities & Places
> > without code generation, so we've chosen to prioritize effort around making
> > that easier (for example, ServiceLocators and issues 5807, 6234 make it
> > possible to inherit generic service methods vs. generate them).
>
> > Technically, GWT-Roo integration is structured as a Roo add-on so Spring
> > needs to be at least involved in any further work.
>
> > Are you just wanting to kick the tires or have you already adopted Roo and
> > have a really strong use case for GWT integration also?
>
> > /dmc
>
> > On Fri, Jun 24, 2011 at 6:19 AM, Aza Tek <azat...@gmail.com> wrote:
>
> >> Wonderful, wonderful question Amit. I'm all ears for a genuine answer on
> >> this one (NOT the usual "This is a springsource-team problem", when it's
> >> clearly so important to GWT).
>
> >> Thanks
>

Amit

unread,
Jun 27, 2011, 12:04:32 PM6/27/11
to Google Web Toolkit

Bademus -

unread,
Jul 26, 2011, 6:10:58 AM7/26/11
to google-we...@googlegroups.com
I would like to test new feature [(Issue 6234) RequestContext interfaces can be composed]. But simply by inherite base interface it didn't work. Did I miss new annotation?
(Tested with gwt 2.4 beta)

Raphael André Bauer

unread,
Jul 26, 2011, 7:49:01 AM7/26/11
to google-we...@googlegroups.com
Hi,


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

Reply all
Reply to author
Forward
0 new messages