<?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"
	>
<channel>
	<title>Comments on: Choosing a Java Web Framework (Revisited)</title>
	<atom:link href="http://evolutionarygoo.com/blog/?feed=rss2&#038;p=233" rel="self" type="application/rss+xml" />
	<link>http://evolutionarygoo.com/blog/?p=233</link>
	<description></description>
	<pubDate>Sun, 05 Sep 2010 13:23:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Evolutionary Goo &#187; Blog Archive &#187; Choosing a Java Web Framework</title>
		<link>http://evolutionarygoo.com/blog/?p=233#comment-8051</link>
		<dc:creator>Evolutionary Goo &#187; Blog Archive &#187; Choosing a Java Web Framework</dc:creator>
		<pubDate>Sat, 24 Jul 2010 21:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://evolutionarygoo.com/blog/?p=233#comment-8051</guid>
		<description>[...] See Choosing a Java Web Framework (Revisited) for updates to this [...]</description>
		<content:encoded><![CDATA[<p>[...] See Choosing a Java Web Framework (Revisited) for updates to this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Ultimate Web UI Framework &#171; The Holy Java</title>
		<link>http://evolutionarygoo.com/blog/?p=233#comment-8049</link>
		<dc:creator>The Ultimate Web UI Framework &#171; The Holy Java</dc:creator>
		<pubDate>Sat, 22 May 2010 15:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://evolutionarygoo.com/blog/?p=233#comment-8049</guid>
		<description>[...] Evolutionary Goo: Choosing a Java Web Framework (Revisited)&#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] Evolutionary Goo: Choosing a Java Web Framework (Revisited)&nbsp; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose Maria Arranz</title>
		<link>http://evolutionarygoo.com/blog/?p=233#comment-6993</link>
		<dc:creator>Jose Maria Arranz</dc:creator>
		<pubDate>Fri, 17 Oct 2008 10:01:57 +0000</pubDate>
		<guid isPermaLink="false">http://evolutionarygoo.com/blog/?p=233#comment-6993</guid>
		<description>I forget to say that for me "beta" != "with bugs" 
For me "beta" = missing some features and API may change.

I'm not saying ItsNat hasn't bugs, it may have, but they aren't identified.</description>
		<content:encoded><![CDATA[<p>I forget to say that for me &#8220;beta&#8221; != &#8220;with bugs&#8221;<br />
For me &#8220;beta&#8221; = missing some features and API may change.</p>
<p>I&#8217;m not saying ItsNat hasn&#8217;t bugs, it may have, but they aren&#8217;t identified.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose Maria Arranz</title>
		<link>http://evolutionarygoo.com/blog/?p=233#comment-6992</link>
		<dc:creator>Jose Maria Arranz</dc:creator>
		<pubDate>Fri, 17 Oct 2008 09:50:48 +0000</pubDate>
		<guid isPermaLink="false">http://evolutionarygoo.com/blog/?p=233#comment-6992</guid>
		<description>Very nice classification really. Some time ago I wrote something similar:

http://www.theserverside.com/news/thread.tss?thread_id=47824#243768

Steal any idea you like for your "feature list".

This is the categorization of ItsNat

http://www.itsnat.org

the framework I'm working on (to fully understand my explanations read before the introduction to the framework on the web page).

* Is it action based? 

Yes and No. Page based navigation is not the focus, you can build the classic page based application but ItsNat doesn't provide very much, the focus is AJAX. Anyway ItsNat introduces a new technique named "referrers", the previous page is accessible to the next page, the new page can steal markup and data from the previous reducing the data hold in the client. 

As ItsNat doesn't impose a concrete servlet I think ItsNat  can be plug into Struts or similar and ItsNat template rendering can be used as the view technology.

* Is it component based?

Yes, reusing Swing data and listeners models as possible. Components are highly customizable and new components can be built very easily. Anyway you can live without components, they are optional. 

* Is it page based? 

 As said before you can do page navigation but the focus is pure AJAX: the application running in the same page with no reload.

* Is the Web tier generated? 

Yes, ItsNat is server-centric and no client code is necessary, but isn't "markup intrusive" because the markup is highly controlled by the developer so JavaScript can be mixed with some care including DHTML. Anyway ItsNat provides a bridge to call the server code from custom JavaScript code received as special DOM events in the server (user events).

* Is it JSP based? 

No, ItsNat has an alternative templating technique. I just use a starter JSP to launch the app server and the browser :) ItsNat in no way depends on JSP.

* Is it template based?

Yes. ItsNat templates are *absolute* pure HTML (and SVG) pages with absolutely no logic (this view logic is done using Java W3C APIs). Furethermore "fragments" are pure HTML/SVG too, fragments are pieces of markup that can be included into the main page when needed.

* Is it Rails like?

No, ItsNat promotes best practices: static view separated of the view logic and business logic and persistency logic.

* Does it support a dynamic scripting language?

Yes and No. ItsNat is developed in Java and the focus is Java, but user code can be coded in a JVM scripting language.

* Does it support IoC?

ItsNat approach is "classic", that is, imperative, as you say an IoC container can be used to manage user code.

* Does it support Web conversations?

Web conversations have sense in page based navigation. In a single page/pure AJAX application there is no need to share data between pages (in fact the session object is not needed anymore). 

* Is it testable?

Yes, functional testing is built-in. ItsNat AJAX applications can be functionally tested simulating user actions using a technique called "server-sent events", basically W3C DOM events are fired from server and sent to the client simulating user actions. The advantage is: testing code and normal code/data are together, testing code can see server data to check if the task was done correctly.

* How well does it support security?

  Security is a primary concern, the server-centric nature helps very much. 

* Is it well supported and maintained? 

 ItsNat is open source but it isn't a free time-pet project, is business driven and professional open source.  

 The learning curve is very very flat, you won't need very much support. 

* Is it stable? 

 ItsNat is pre v1.0 but API is becoming stable. An ItsNat applications is mainly coded using Java W3C APIs and pure HTML/SVG code this prevents any ItsNat specific API change doesn't impact very much your application.

* Will it help me adhere to standards?

As said before your code is basically Java W3C APIs and pure HTML/SVG code, aren't they standards?

Regards
Jose Maria Arranz</description>
		<content:encoded><![CDATA[<p>Very nice classification really. Some time ago I wrote something similar:</p>
<p><a href="http://www.theserverside.com/news/thread.tss?thread_id=47824#243768" rel="nofollow">http://www.theserverside.com/news/thread.tss?thread_id=47824#243768</a></p>
<p>Steal any idea you like for your &#8220;feature list&#8221;.</p>
<p>This is the categorization of ItsNat</p>
<p><a href="http://www.itsnat.org" rel="nofollow">http://www.itsnat.org</a></p>
<p>the framework I&#8217;m working on (to fully understand my explanations read before the introduction to the framework on the web page).</p>
<p>* Is it action based? </p>
<p>Yes and No. Page based navigation is not the focus, you can build the classic page based application but ItsNat doesn&#8217;t provide very much, the focus is AJAX. Anyway ItsNat introduces a new technique named &#8220;referrers&#8221;, the previous page is accessible to the next page, the new page can steal markup and data from the previous reducing the data hold in the client. </p>
<p>As ItsNat doesn&#8217;t impose a concrete servlet I think ItsNat  can be plug into Struts or similar and ItsNat template rendering can be used as the view technology.</p>
<p>* Is it component based?</p>
<p>Yes, reusing Swing data and listeners models as possible. Components are highly customizable and new components can be built very easily. Anyway you can live without components, they are optional. </p>
<p>* Is it page based? </p>
<p> As said before you can do page navigation but the focus is pure AJAX: the application running in the same page with no reload.</p>
<p>* Is the Web tier generated? </p>
<p>Yes, ItsNat is server-centric and no client code is necessary, but isn&#8217;t &#8220;markup intrusive&#8221; because the markup is highly controlled by the developer so JavaScript can be mixed with some care including DHTML. Anyway ItsNat provides a bridge to call the server code from custom JavaScript code received as special DOM events in the server (user events).</p>
<p>* Is it JSP based? </p>
<p>No, ItsNat has an alternative templating technique. I just use a starter JSP to launch the app server and the browser <img src='http://evolutionarygoo.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> ItsNat in no way depends on JSP.</p>
<p>* Is it template based?</p>
<p>Yes. ItsNat templates are *absolute* pure HTML (and SVG) pages with absolutely no logic (this view logic is done using Java W3C APIs). Furethermore &#8220;fragments&#8221; are pure HTML/SVG too, fragments are pieces of markup that can be included into the main page when needed.</p>
<p>* Is it Rails like?</p>
<p>No, ItsNat promotes best practices: static view separated of the view logic and business logic and persistency logic.</p>
<p>* Does it support a dynamic scripting language?</p>
<p>Yes and No. ItsNat is developed in Java and the focus is Java, but user code can be coded in a JVM scripting language.</p>
<p>* Does it support IoC?</p>
<p>ItsNat approach is &#8220;classic&#8221;, that is, imperative, as you say an IoC container can be used to manage user code.</p>
<p>* Does it support Web conversations?</p>
<p>Web conversations have sense in page based navigation. In a single page/pure AJAX application there is no need to share data between pages (in fact the session object is not needed anymore). </p>
<p>* Is it testable?</p>
<p>Yes, functional testing is built-in. ItsNat AJAX applications can be functionally tested simulating user actions using a technique called &#8220;server-sent events&#8221;, basically W3C DOM events are fired from server and sent to the client simulating user actions. The advantage is: testing code and normal code/data are together, testing code can see server data to check if the task was done correctly.</p>
<p>* How well does it support security?</p>
<p>  Security is a primary concern, the server-centric nature helps very much. </p>
<p>* Is it well supported and maintained? </p>
<p> ItsNat is open source but it isn&#8217;t a free time-pet project, is business driven and professional open source.  </p>
<p> The learning curve is very very flat, you won&#8217;t need very much support. </p>
<p>* Is it stable? </p>
<p> ItsNat is pre v1.0 but API is becoming stable. An ItsNat applications is mainly coded using Java W3C APIs and pure HTML/SVG code this prevents any ItsNat specific API change doesn&#8217;t impact very much your application.</p>
<p>* Will it help me adhere to standards?</p>
<p>As said before your code is basically Java W3C APIs and pure HTML/SVG code, aren&#8217;t they standards?</p>
<p>Regards<br />
Jose Maria Arranz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: robbiecheng</title>
		<link>http://evolutionarygoo.com/blog/?p=233#comment-6869</link>
		<dc:creator>robbiecheng</dc:creator>
		<pubDate>Fri, 19 Sep 2008 17:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://evolutionarygoo.com/blog/?p=233#comment-6869</guid>
		<description>Here is another Java, Server-centric framework, &lt;a href="http:\\www.zkoss.org" rel="nofollow"&gt;ZK&lt;/a&gt;. 

ZK is Ajax Java framework without JavaScript. With direct RIA, 200+ Ajax components and markup languages, developing Ajax/RIA as simple as desktop apps and HTML/XUL pages. Support JSF/JSP/JavaEE/Hibernate/.., and Ajax script in Java/Ruby/Groovy/Python/..</description>
		<content:encoded><![CDATA[<p>Here is another Java, Server-centric framework, <a href="http:\\www.zkoss.org" rel="nofollow">ZK</a>. </p>
<p>ZK is Ajax Java framework without JavaScript. With direct RIA, 200+ Ajax components and markup languages, developing Ajax/RIA as simple as desktop apps and HTML/XUL pages. Support JSF/JSP/JavaEE/Hibernate/.., and Ajax script in Java/Ruby/Groovy/Python/..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
