Comments on: Wicket suits complex Ajax better than RoR+RJS? http://martijndashorst.com/blog/2006/12/27/wicket-suits-complex-ajax-better-than-rorrjs/ Ramblings on Java, Wicket, cats and other stuff Wed, 27 Jan 2010 00:31:04 +0100 http://wordpress.org/?v=2.9.1 hourly 1 By: Wicket Impressions, moving from Spring MVC / WebFlow « Incremental Operations http://martijndashorst.com/blog/2006/12/27/wicket-suits-complex-ajax-better-than-rorrjs/comment-page-1/#comment-317 Wicket Impressions, moving from Spring MVC / WebFlow « Incremental Operations Fri, 02 Mar 2007 13:53:47 +0000 http://martijndashorst.com/2006/12/27/wicket-suits-complex-ajax-better-than-rorrjs/#comment-317 [...] I came across this quote that Ajax in Wicket could be better and much easier than how you do Ajax in Rails, and I wouldn’t be surprised if this is true. [...] [...] I came across this quote that Ajax in Wicket could be better and much easier than how you do Ajax in Rails, and I wouldn’t be surprised if this is true. [...]

]]> By: Jacob Hookom http://martijndashorst.com/blog/2006/12/27/wicket-suits-complex-ajax-better-than-rorrjs/comment-page-1/#comment-2 Jacob Hookom Wed, 27 Dec 2006 19:25:14 +0000 http://martijndashorst.com/2006/12/27/wicket-suits-complex-ajax-better-than-rorrjs/#comment-2 I agree, component references have their advantages over implied elements in the page: http://weblogs.java.net/blog/jhook/archive/2006/10/rjs_api_for_jav_1.html I agree, component references have their advantages over implied elements in the page:

http://weblogs.java.net/blog/jhook/archive/2006/10/rjs_api_for_jav_1.html

]]>