* Maninder, Singh wrote (10/01/2006 06:57):> Hello Everyone,
>
> Does anyone have any insight into the DWR library
> (http://getahead.ltd.uk/dwr/index)?
>
> I want to know the pros/cons of using DWR Vs Prototype/Scriptaculous
> libraries.
>
> I am a great fan of the prototype/scriptaculous combination and have
> been working with them for the last 3-4 months but for some reasons I
> have been asked to look into DWR.
>
> Due to it''s tight integration with Java and unnecessary learning
> curve, I am not too ga ga over it. So, looking out for more cons than
> pros ;)
DWR and prototype/scriptaculous do very different things. There is a
tiny bit of overlap, but hardly any.
The javascript part of DWR manages ajax calls to java back-end code.
That''s more or less all. It ships with a few utility functions that you
can ignore if you like.
You can then use prototype and scriptaculous all you like.
Most of the value of DWR is the java code installed on the server, which
enables you to expose java classes really nicely without writing extra
server code. So if you already have java classes that output objects
that you want to make available to the client, DWR is an obvious choice.
The only place the two would conflict is if you''re using the prototype
Ajax object, in which case you would need to change a few things.
I can testify that scriptaculous and DWR work well together, and the
author of DWR uses it heavily as far as I know (from reading the DWR
mailing list).
DWR is extremely well documented and well supported.
If you don''t like java (I don''t, but we use it, so
that''s that), your
ajax requirements are very simple, or you have an aversion to mixing
libraries, then stick with just prototype. Otherwise, give it a go.
Chris