Re: Spring Roo & 2.1 M3, not recommended if you haven't tried.

I just finished a project on Roo but we were using Spring also for
front end. What we figured out is that Roo is very good to generate
that initial structure and than better be on your own. We still used
roo to manage the domain entities (generating getters and setters) but
not more than that.

Now I am in a project with GWT and Spring. From my earlier experience
we generated the initial code structure using roo and than we are on
our own.

Also I would second Daniel about UIBinder. It's an easier way of doing
things. and the same goes for annotations also.

On Sep 25, 6:48 pm, Supercobra Thatbytes <superco...@gmail.com> wrote:
> Kevin,
>
> My experience with Roo is not much better than yours. I was able to
> get it running after an hour or so. It is an early stage product that
> shows potential. Not ready for prime time yet.
>
> Regarding UiBinder: If it turned you off 'immediately' as you said,
> you have not created enough widgets in GWT yet, because once you'll
> have done that, you'll see that creating widget UI in XML with
> UiBinder is the simpler and more efficient way.
>
> Daniel

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.