Re: [cinjug-users] Ajax frameworks

["Rogelio Flores" <rogelio.flores@xxxxxxxxx>]

I've played with GWT a bit as well, and agree with your comments
except I don't mind the extra step of compilation.
I also don't like the dependency placed on your DTOs, but the way I
see it, it is a necessary evil to have DTOs that can be converted to
javascript objects.

Some good things:
+ you can reuse java classes for both client and server validation of
data or other utilities (provided it can be converted to javascript)
+ you can be proficient very quickly if you have Swing experience
(probably even if you don't have any) and there are tools out there
already to build GUIs visually in some IDEs

On the down side:
- Although it is easy to gather and send data from your pages to the
server, I think GWT should have more built-in support for sending
lumps of data, similar to a request that takes everything in a form
tag, or how JSPs can access JavaBeans with very little code. It can be
time-consuming to do the granular type of data gathering required
(even if it is useful in many cases). So you create your own widgets
that will do this automatically, but still it means you have to do it
at least once. Or maybe I haven't found some utilities in the docs ;-(
- I don't know about production-env performance since I'm in a
prototype stage, and being a beta release, it would be hard to find
anyone that knows about it (I've found nobody).


--
Rogelio



On 2/7/07, Timothy Dennison <denti07@xxxxxxxxx> wrote:
> My $0.02 on GWT (in case you're considering it)...
>
> GWT sounds great and in fact is very impressive for prototyping.  All java
> (no javascript), debugging capabilities, special browser (hosted mode) that
> allows on the fly modifications.
>
> The problems arise when you try to hook up real services and use the GWT
> serialization mechanism.  First of all, java.io.Serializable is not
> supported (Google has their own "IsSerializable" interface that all objects
> passed to/fro the client have to implement).  This seems "klunky" and
> requires my domain layer to have a dependency on GWT interfaces or support a
> DTO pattern.  Also, good luck trying to hook up a Spring-enabled service
> layer with the hosted mode browser (the recommended development mode for
> GWT).  Your forced to either monkey with the *generated* web descriptor (GWT
> actually creates a tomcat deployment on the fly for hosted mode) to load
> your Spring context or support the -noserver option (which defeats the whole
> rapid prototyping model).
>
> In addition, I've found two other things I don't like about GWT.  Each RPC
> service is actually a subclass of a servlet.  I had to resort to using a
> modified Spring ServletWrappingController in order to put my GWT services
> behind a DispatcherServlet.  The last thing? That extra compile from Java to
> Javascript.  It just gets in the way and forces you to use an Ant build (or
> eclipse builder with an ant build).  Having to do that extra step before
> each deploy was not much fun IMHO.
>
> My diatribe is over :)
> tim
>  Timothy S. Dennison
> mobile#(513)377-5102
>
>
> ----- Original Message ----
> From: "jim_garrett@xxxxxxxx" <jim_garrett@xxxxxxxx>
> To: users@xxxxxxxxxx; twcrone@xxxxxxxxxxxxx; Abdul Habra <ahabra@xxxxxxxxx>
> Sent: Wednesday, February 7, 2007 2:10:37 PM
> Subject: Re: [cinjug-users] Ajax frameworks
>
> As I understand Echo2, every click of the screen could require a server call
> to resolve the action being done.  Can you comment on how well Echo2
> performed on a system with several hundred simultaneous users?
>
>
> --
> Jim Garrett
> email:jim_garrett@xxxxxxxx
>
> ---- Abdul Habra <ahabra@xxxxxxxxx> wrote:
> > My favorite is Echo2:
> >   http://www.nextapp.com/products/
> >
> >   Fully OO, Java only (no xml, html, ...), built on top of AJAX.
> >   I used Echo1 in 2 projects and was very happy with it.
> >   Did not use Echo2 in any live project, but a friend of mine did, and he
> loved it.
> >   Sounds like I am making a commercial :)
> >
> >   I would also look at Tapestry/Tacos. Tapestry is a mature product.
> >
> >
> > twcrone@xxxxxxxxxxxxx wrote:
> >   I'm currently researching Ajax packages.  I have experimented with DWR
> for RPC stuff and played with GWT very little.  Other than that I am looking
> primarily at Dojo and maybe ICEFaces if my shop decides to use JSF.  I'm
> curious about TIBCO GI since TIBCO now sponsors DWR.  I saw Stuart
> Halloway's session notes on Prototype and Script.aculo.us.
> >
> > My shop is currently very committed to using Spring and has used OpenLazlo
> in the past but we don't want to use it for our future work.
> >
> > What is everyone's favorites now?
> >
> > As always, thanks for the info...
> >
> > - Todd
> >
> >
> > Thank You,
> > Abdul Habra
> >
> > ---------------------------------