<?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: Apache Wicket : The greatest Java Web Framework Ever!</title>
	<atom:link href="http://anirudhvyas.com/root/index.php/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/feed/" rel="self" type="application/rss+xml" />
	<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/</link>
	<description></description>
	<lastBuildDate>Wed, 13 May 2009 14:36:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: me</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-428</link>
		<dc:creator>me</dc:creator>
		<pubDate>Wed, 13 May 2009 14:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-428</guid>
		<description>I think that Wicket is nice, but if you part of a software team and you develop a Web application - choosing Wicket over Spring MVC will be very bad choice. The concept of mixing Java and Presentation - there is nothing good in it.
No matter what you will do with Wicket and no matter how many code Wicket will generate, you will finally stuck with some presentations problems.
But then you will realize, that much logic of the presentation is done in Java, with some hierarchy between classes and so on... so what kind of programmer you need for it?
A Java expert who is GUI HTML developer? The Java hierarchy between classes that will finally make an HTML page is also not a good idea, what for you need this in 
presentation? Choose Velocity, Spring MVC, Tiles 2 and hire an HTML expert. That&#039;s it.</description>
		<content:encoded><![CDATA[<p>I think that Wicket is nice, but if you part of a software team and you develop a Web application &#8211; choosing Wicket over Spring MVC will be very bad choice. The concept of mixing Java and Presentation &#8211; there is nothing good in it.<br />
No matter what you will do with Wicket and no matter how many code Wicket will generate, you will finally stuck with some presentations problems.<br />
But then you will realize, that much logic of the presentation is done in Java, with some hierarchy between classes and so on&#8230; so what kind of programmer you need for it?<br />
A Java expert who is GUI HTML developer? The Java hierarchy between classes that will finally make an HTML page is also not a good idea, what for you need this in<br />
presentation? Choose Velocity, Spring MVC, Tiles 2 and hire an HTML expert. That&#8217;s it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antony Stubbs</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-197</link>
		<dc:creator>Antony Stubbs</dc:creator>
		<pubDate>Thu, 19 Feb 2009 16:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-197</guid>
		<description>You should do yourself a favour and check out Grails too.</description>
		<content:encoded><![CDATA[<p>You should do yourself a favour and check out Grails too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Thomas</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-30</link>
		<dc:creator>Peter Thomas</dc:creator>
		<pubDate>Fri, 30 May 2008 05:56:49 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-30</guid>
		<description>Anirudh:  Great write up!  I agree with your analysis and recently tried to capture the flaws in the MVC Action / JSP approach in a set of slides.  It would be great if you can have a look and let me know if there are any points I have missed - based on your experience.

You can find the slides here:

http://ptrthomas.wordpress.com/2008/05/26/migrating-to-apache-wicket-presentation-slides/</description>
		<content:encoded><![CDATA[<p>Anirudh:  Great write up!  I agree with your analysis and recently tried to capture the flaws in the MVC Action / JSP approach in a set of slides.  It would be great if you can have a look and let me know if there are any points I have missed &#8211; based on your experience.</p>
<p>You can find the slides here:</p>
<p><a href="http://ptrthomas.wordpress.com/2008/05/26/migrating-to-apache-wicket-presentation-slides/" rel="nofollow">http://ptrthomas.wordpress.com/2008/05/26/migrating-to-apache-wicket-presentation-slides/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Silbermann</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-15</link>
		<dc:creator>Frank Silbermann</dc:creator>
		<pubDate>Tue, 15 Apr 2008 22:28:43 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-15</guid>
		<description>What I like about Wicket is that you can make self-documenting code that respects the DRY (Don&#039;t Repeat Yourself) principle.

What I mean by &quot;self-documenting&quot; is that I can modularize a page into panels, give those panels names oriented towards the business logic, and describe my page in those simple, hierarichical terms -- just as I can modularize a batch program as a hierarchy of well-named subroutines.  This is much more readable than a HUGE tree of deeply nested tags.

If I am using similar panels in many places, I can write a single panel class to cover all the cases, with the differences in each usage configured via the constructor parameters of my panel subclass.  Or, I can design my panel subclass with default or abstract methods to be overriden by (possibly anonymous) subclasses.  Or I can combine both techniques.  This gives me the same abstraction and re-use capabilities for the presentation logic that I already enjoy when coding the business logic.

If I want aspects of my application to have declarative configuration, I can simply include a configuration textfile in my application and write my code to read, parse, and use the information contained therein (without relying on the framework creator to guess the aspects I want to be declaratively configured).

Once you get the Wicket way of doing things, it&#039;s as flexible and powerful as Java itself.</description>
		<content:encoded><![CDATA[<p>What I like about Wicket is that you can make self-documenting code that respects the DRY (Don&#8217;t Repeat Yourself) principle.</p>
<p>What I mean by &#8220;self-documenting&#8221; is that I can modularize a page into panels, give those panels names oriented towards the business logic, and describe my page in those simple, hierarichical terms &#8212; just as I can modularize a batch program as a hierarchy of well-named subroutines.  This is much more readable than a HUGE tree of deeply nested tags.</p>
<p>If I am using similar panels in many places, I can write a single panel class to cover all the cases, with the differences in each usage configured via the constructor parameters of my panel subclass.  Or, I can design my panel subclass with default or abstract methods to be overriden by (possibly anonymous) subclasses.  Or I can combine both techniques.  This gives me the same abstraction and re-use capabilities for the presentation logic that I already enjoy when coding the business logic.</p>
<p>If I want aspects of my application to have declarative configuration, I can simply include a configuration textfile in my application and write my code to read, parse, and use the information contained therein (without relying on the framework creator to guess the aspects I want to be declaratively configured).</p>
<p>Once you get the Wicket way of doing things, it&#8217;s as flexible and powerful as Java itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Sonchocky-Helldorf</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-6</link>
		<dc:creator>Lars Sonchocky-Helldorf</dc:creator>
		<pubDate>Mon, 14 Apr 2008 22:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-6</guid>
		<description>Sadly you completely missed out WebObjects, the mother of all Web Frameworks and still one of the best. WebObjects is not only the Framework that invented component based web development but also comes with one of the best and most mature persistence layers, &quot;Enterprise Objects Framework&quot; or short &quot;EOF&quot;. You find a short introduction here: http://en.wikipedia.org/wiki/WebObjects and more information (including JavaDoc) here: http://developer.apple.com/referencelibrary/DeveloperTools/idxWebObjects-date.html

regards,

    Lars (Wicket and WebObjects user)</description>
		<content:encoded><![CDATA[<p>Sadly you completely missed out WebObjects, the mother of all Web Frameworks and still one of the best. WebObjects is not only the Framework that invented component based web development but also comes with one of the best and most mature persistence layers, &#8220;Enterprise Objects Framework&#8221; or short &#8220;EOF&#8221;. You find a short introduction here: <a href="http://en.wikipedia.org/wiki/WebObjects" rel="nofollow">http://en.wikipedia.org/wiki/WebObjects</a> and more information (including JavaDoc) here: <a href="http://developer.apple.com/referencelibrary/DeveloperTools/idxWebObjects-date.html" rel="nofollow">http://developer.apple.com/referencelibrary/DeveloperTools/idxWebObjects-date.html</a></p>
<p>regards,</p>
<p>    Lars (Wicket and WebObjects user)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-4</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Tue, 01 Apr 2008 03:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-4</guid>
		<description>Hey Jon,

Btw, we are fans of you, Igor and co. :)

I am involved with a project that is using Wicket officially and i was kind of &quot;forced&quot; to look into it ( I was going in ... oh no not again mode, but was surprised)  Yeah, i tried Flex recently; it has this incredibly slick feel to it. Slick as in the interface it generates is just unbelievably sweet looking. I am pretty sure that It will be something to watch out for in Next 3 years or so.

(My only problem is that I am not familiar with actionScript that much, granted that there are tools that can do that for you).

So yes, if there is a patch which bridges Wicket &lt;---&gt; Flex; that will AWESOME!. Btw, I am not so excited about GWT ...


Regards
Vyas, Anirudh</description>
		<content:encoded><![CDATA[<p>Hey Jon,</p>
<p>Btw, we are fans of you, Igor and co. <img src='http://anirudhvyas.com/root/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I am involved with a project that is using Wicket officially and i was kind of &#8220;forced&#8221; to look into it ( I was going in &#8230; oh no not again mode, but was surprised)  Yeah, i tried Flex recently; it has this incredibly slick feel to it. Slick as in the interface it generates is just unbelievably sweet looking. I am pretty sure that It will be something to watch out for in Next 3 years or so.</p>
<p>(My only problem is that I am not familiar with actionScript that much, granted that there are tools that can do that for you).</p>
<p>So yes, if there is a patch which bridges Wicket < ---> Flex; that will AWESOME!. Btw, I am not so excited about GWT &#8230;</p>
<p>Regards<br />
Vyas, Anirudh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Locke</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-3</link>
		<dc:creator>Jonathan Locke</dc:creator>
		<pubDate>Sun, 30 Mar 2008 05:38:22 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-3</guid>
		<description>BTW, I would not write an ordinary web application in anything but Wicket, but I think there is a place for Flex or GWT integration on sites built in Wicket.  I look forward to GWT integration in the future.

   Jon</description>
		<content:encoded><![CDATA[<p>BTW, I would not write an ordinary web application in anything but Wicket, but I think there is a place for Flex or GWT integration on sites built in Wicket.  I look forward to GWT integration in the future.</p>
<p>   Jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Locke</title>
		<link>http://anirudhvyas.com/root/2008/03/20/apache-wicket-the-greatest-java-web-framework-ever/comment-page-1/#comment-2</link>
		<dc:creator>Jonathan Locke</dc:creator>
		<pubDate>Sun, 30 Mar 2008 05:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhvyas.com/root/?p=3#comment-2</guid>
		<description>&quot;Wicket reminds me of Swing Model of programming&quot;

Well, i did work on Swing.  Perhaps some of that experience rubbed off. ;-)

Thanks for the kind words.  Always nice to read a blog post like this.

     Jon</description>
		<content:encoded><![CDATA[<p>&#8220;Wicket reminds me of Swing Model of programming&#8221;</p>
<p>Well, i did work on Swing.  Perhaps some of that experience rubbed off. <img src='http://anirudhvyas.com/root/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Thanks for the kind words.  Always nice to read a blog post like this.</p>
<p>     Jon</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.393 seconds -->
