<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: An AJAX email contact form using DWR and Scriptaculous</title> <atom:link href="http://greatwebguy.com/programming/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/feed/" rel="self" type="application/rss+xml" /><link>http://greatwebguy.com/programming/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/</link> <description>Self-proclaimed greatness is a hard thing to prove.</description> <lastBuildDate>Fri, 10 Feb 2012 02:11:49 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Alek</title><link>http://greatwebguy.com/programming/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-70</link> <dc:creator>Alek</dc:creator> <pubDate>Tue, 06 Jan 2009 17:32:51 +0000</pubDate> <guid
isPermaLink="false">http://greatwebguy.com/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-70</guid> <description>Hi. Good site.</description> <content:encoded><![CDATA[<p>Hi. Good site.</p> ]]></content:encoded> </item> <item><title>By: webguy</title><link>http://greatwebguy.com/programming/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-69</link> <dc:creator>webguy</dc:creator> <pubDate>Mon, 07 Apr 2008 19:14:48 +0000</pubDate> <guid
isPermaLink="false">http://greatwebguy.com/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-69</guid> <description>Well the advantages of both would be if you&#039;re at home with Java, you&#039;re going to be able to write more Java to handle your Ajax development than you normally would.
With Google Web Toolkit you basically write all of your code in Java and GWT generates the pages and Javascript code for you, it even has a browser piece during development to do the Java to Javascript interpretation realtime, what you do with it after that as far as integrating it into an existing application or just using the html and javascript generated is up to you.  I believe GWT also has a bunch of widgets that will make construction of a full blown Ajax application easier.
DWR is more geared toward asynchronous interaction with Java-based applications.  With DWR you can expose existing API&#039;s that you&#039;ve written in Java and return your Javabeans converted to Javascript and DWR does all the heavy lifting for you.  DWR is great for adding Ajax to existing Java applications, it abstracts all of the difficulty of making asynchronous calls, but will in most cases still require a fair bit of Javascript in order to manipulate the DOM. It comes with a util.js with some DOM utilities, but I&#039;ve found in my experience that a library such as jQuery is much better suited for this type of work.
My recommendation would be if you&#039;re writing a new application that&#039;s going use a lot of Ajax, give GWT a try.  If you&#039;re adding functionality to an existing application DWR and jQuery make a great combination.</description> <content:encoded><![CDATA[<p>Well the advantages of both would be if you&#8217;re at home with Java, you&#8217;re going to be able to write more Java to handle your Ajax development than you normally would.</p><p>With Google Web Toolkit you basically write all of your code in Java and GWT generates the pages and Javascript code for you, it even has a browser piece during development to do the Java to Javascript interpretation realtime, what you do with it after that as far as integrating it into an existing application or just using the html and javascript generated is up to you.  I believe GWT also has a bunch of widgets that will make construction of a full blown Ajax application easier.</p><p>DWR is more geared toward asynchronous interaction with Java-based applications.  With DWR you can expose existing API&#8217;s that you&#8217;ve written in Java and return your Javabeans converted to Javascript and DWR does all the heavy lifting for you.  DWR is great for adding Ajax to existing Java applications, it abstracts all of the difficulty of making asynchronous calls, but will in most cases still require a fair bit of Javascript in order to manipulate the DOM. It comes with a util.js with some DOM utilities, but I&#8217;ve found in my experience that a library such as jQuery is much better suited for this type of work.</p><p>My recommendation would be if you&#8217;re writing a new application that&#8217;s going use a lot of Ajax, give GWT a try.  If you&#8217;re adding functionality to an existing application DWR and jQuery make a great combination.</p> ]]></content:encoded> </item> <item><title>By: Mithun.K.Mathew</title><link>http://greatwebguy.com/programming/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-68</link> <dc:creator>Mithun.K.Mathew</dc:creator> <pubDate>Sat, 05 Apr 2008 06:47:10 +0000</pubDate> <guid
isPermaLink="false">http://greatwebguy.com/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-68</guid> <description>can anyone give me the advantages of using DWR and google web toolkit over other ajax frameworks . also please mention , under which conditions which framework is best and why. Please help me out,I would be highly obliged.</description> <content:encoded><![CDATA[<p>can anyone give me the advantages of using DWR and google web toolkit over other ajax frameworks . also please mention , under which conditions which framework is best and why. Please help me out,I would be highly obliged.</p> ]]></content:encoded> </item> <item><title>By: webguy</title><link>http://greatwebguy.com/programming/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-67</link> <dc:creator>webguy</dc:creator> <pubDate>Wed, 14 Nov 2007 15:03:04 +0000</pubDate> <guid
isPermaLink="false">http://greatwebguy.com/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-67</guid> <description>If you&#039;re talking about the util methods in DWR, getValues() and setValues(), the mapping is done via the id&#039;s of the fields, in html/xhtml an id should always be unique, therefore multiple fields wouldn&#039;t have an issue with the automagic mapping.</description> <content:encoded><![CDATA[<p>If you&#8217;re talking about the util methods in DWR, getValues() and setValues(), the mapping is done via the id&#8217;s of the fields, in html/xhtml an id should always be unique, therefore multiple fields wouldn&#8217;t have an issue with the automagic mapping.</p> ]]></content:encoded> </item> <item><title>By: Johnny</title><link>http://greatwebguy.com/programming/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-66</link> <dc:creator>Johnny</dc:creator> <pubDate>Wed, 14 Nov 2007 06:39:47 +0000</pubDate> <guid
isPermaLink="false">http://greatwebguy.com/ajax/an-ajax-email-contact-form-using-dwr-and-scriptaculous/#comment-66</guid> <description>I believe it automagically maps the form field to Contact object.  But how about if we have multiple form having duplicate textfield? How do we map it?
Great simplistic tutorial!</description> <content:encoded><![CDATA[<p>I believe it automagically maps the form field to Contact object.  But how about if we have multiple form having duplicate textfield? How do we map it?</p><p>Great simplistic tutorial!</p> ]]></content:encoded> </item> </channel> </rss>
