<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://java.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Duncan Mills</title>
 <link>http://java.sys-con.com/</link>
 <description>Latest articles from Duncan Mills</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Thu, 28 Aug 2008 20:13:03 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Effective Page Authorization In JavaServer Faces</title>
 <link>http://java.sys-con.com/node/250254</link>
 <description>Application security - the art of applications defending themselves - represents an important line of defence in an overall in-depth security strategy. Web applications that follow the Model-View-Controller (MVC) architecture can, and should, have security implemented on all three layers. Normally it&#039;s the controller component that handles page authorization in MVC, the view layer that hides controls and information based on user authorization, and the model that enforces the business rules and input validation. However, it&#039;s up to the developer, based on an individual security policy and the programming technology used, to decide where to put security. Using pluggable validator components in JavaServer Faces (JSF), for example, developers may decide to verify user input on the view layer as well as on the model layer.&lt;p&gt;&lt;a href=&quot;http://java.sys-con.com/node/250254&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 10 Aug 2006 17:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://java.sys-con.com/node/250254</guid>
</item>
<item>
 <title>i-Technology Viewpoint: Thoughts on the Java Community</title>
 <link>http://java.sys-con.com/node/108471</link>
 <description>&#039;Is it reasonable to insult and mock those with differing viewpoints? To publicly denigrate a fellow community member or group because they use the wrong IDE, Framework or design pattern (in your opinion) shows ignorance and lack of respect?&#039; Duncan Mills thinks not. Read his essay here and join in the debate below.&lt;p&gt;&lt;a href=&quot;http://java.sys-con.com/node/108471&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 08 Jul 2005 06:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://java.sys-con.com/node/108471</guid>
</item>
<item>
 <title>J2EE vs .NET: Where Is Application Development Going?</title>
 <link>http://java.sys-con.com/node/49198</link>
 <description>The reason .NET &#039;presses a lot of the right buttons,&#039; writes Duncan Mills, is that: &#039;It&#039;s a Meta-Framework - a one-stop shop.&#039;  In the J2EE world, on the other hand, while there is no doubt that there are a lot of fantastic point solutions and frameworks out there, as standalone islands of functionality they have a much harder sell in the corporate market. &#039;Are fully fledged meta-frameworks possible in the open standards J2EE space?&#039; Mills asks, then goes on to show why in his view the answer is yes.&lt;p&gt;&lt;a href=&quot;http://java.sys-con.com/node/49198&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 15 Apr 2005 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://java.sys-con.com/node/49198</guid>
</item>
</channel>
</rss>
