<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>shaokun305的专栏 - 设计模式</title><link>http://blog.csdn.net/shaokun305/category/25132.aspx</link><description>学习设计模式，做J2EE一流架构师。</description><dc:language>zh-CN</dc:language><lastUpdateTime>Sat, 19 Apr 2008 11:45:27 GMT</lastUpdateTime><ttl>60</ttl><item><dc:creator>shaokun305</dc:creator><title>测试需求的相关培训流水帐记录</title><link>http://blog.csdn.net/shaokun305/archive/2008/01/21/2057216.aspx</link><pubDate>Mon, 21 Jan 2008 17:55:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2008/01/21/2057216.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/2057216.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2008/01/21/2057216.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/2057216.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2057216</trackback:ping><description>测试需求的相关培训流水帐记录&lt;img src ="http://blog.csdn.net/shaokun305/aggbug/2057216.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>Java企业系统架构选择考量</title><link>http://blog.csdn.net/shaokun305/archive/2005/10/05/495420.aspx</link><pubDate>Wed, 05 Oct 2005 14:37:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2005/10/05/495420.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/495420.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2005/10/05/495420.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/495420.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=495420</trackback:ping><description>现在Java领域各种技术百花齐放，名目繁多，如何根据自己的需求选择这些框架呢？特别对于初学者，在学习选择方向上也非常迷茫，如何有针对性的根据自己项目特点进行学习就变的更加重要。
&lt;img src ="http://blog.csdn.net/shaokun305/aggbug/495420.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>痛苦的windows20003+oracle10g+tomcat连接池迁移之旅</title><link>http://blog.csdn.net/shaokun305/archive/2005/06/01/385679.aspx</link><pubDate>Wed, 01 Jun 2005 13:56:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2005/06/01/385679.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/385679.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2005/06/01/385679.aspx#Feedback</comments><slash:comments>4</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/385679.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=385679</trackback:ping><description>这次经历。我让我长了不少知识，认识到许多版本之间的区别。也感觉到了windows2003的糟粕，oracle10g驱动的烂。tomcat连接池的局限性等等。希望能给别人带来点小小的帮助。让我们引以为戒，深入研究。&lt;img src ="http://blog.csdn.net/shaokun305/aggbug/385679.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>AOP 软件革命的导火索？</title><link>http://blog.csdn.net/shaokun305/archive/2005/06/01/385419.aspx</link><pubDate>Wed, 01 Jun 2005 09:25:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2005/06/01/385419.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/385419.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2005/06/01/385419.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/385419.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=385419</trackback:ping><description>AOP（面向方面编程，是Aspect Oriented Programming的缩写） 是上世纪 90 年代施乐公司帕洛阿尔托研究中心 (Xerox PARC) 在Gregor Kiczales领导下发明的一种编程范式，它使开发人员可以更好地将本不该彼此纠缠在一起的任务（例如数学运算和异常处理）分离开来。 &lt;img src ="http://blog.csdn.net/shaokun305/aggbug/385419.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>结合struts和hibernate谈J2EE架构的数据表示 </title><link>http://blog.csdn.net/shaokun305/archive/2005/02/24/299987.aspx</link><pubDate>Thu, 24 Feb 2005 12:43:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2005/02/24/299987.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/299987.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2005/02/24/299987.aspx#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/299987.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=299987</trackback:ping><description>在 struts+ hibernate 这种结构中，是不应该把Hibernate产生的PO直接传递给JSP的，不管他是Iterator，还是List，这是一个设计错误。 &lt;img src ="http://blog.csdn.net/shaokun305/aggbug/299987.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>权限,角色,分组,部门</title><link>http://blog.csdn.net/shaokun305/archive/2005/01/25/267313.aspx</link><pubDate>Tue, 25 Jan 2005 12:57:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2005/01/25/267313.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/267313.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2005/01/25/267313.aspx#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/267313.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=267313</trackback:ping><description>最后一个概念
判断用户有没有访问资源的权限就看这个用户有没有访问这个资源的权限,也就是说分组，分部门,分角色最终是以权限来实现对资源的访问控制&lt;img src ="http://blog.csdn.net/shaokun305/aggbug/267313.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>任何人都可以重构---使用 Eclipse 自动重构特性的方法与原因     选择自 shanyou 的 Blog</title><link>http://blog.csdn.net/shaokun305/archive/2004/12/27/230402.aspx</link><pubDate>Mon, 27 Dec 2004 09:19:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2004/12/27/230402.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/230402.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2004/12/27/230402.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/230402.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=230402</trackback:ping><description>eclipse重构专家.......................&lt;img src ="http://blog.csdn.net/shaokun305/aggbug/230402.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>好书选看</title><link>http://blog.csdn.net/shaokun305/archive/2004/12/06/206306.aspx</link><pubDate>Mon, 06 Dec 2004 13:54:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2004/12/06/206306.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/206306.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2004/12/06/206306.aspx#Feedback</comments><slash:comments>2</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/206306.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=206306</trackback:ping><description>好书选看&lt;img src ="http://blog.csdn.net/shaokun305/aggbug/206306.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>大型 ERP 等数据库系统常见的几种设计     jacklondon [原作]  </title><link>http://blog.csdn.net/shaokun305/archive/2004/09/07/96519.aspx</link><pubDate>Tue, 07 Sep 2004 09:35:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2004/09/07/96519.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/96519.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2004/09/07/96519.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/96519.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=96519</trackback:ping><description>大型 ERP 等数据库系统常见的几种设计 &lt;img src ="http://blog.csdn.net/shaokun305/aggbug/96519.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>shaokun305</dc:creator><title>设计模式通俗演义(一)----中介者模式</title><link>http://blog.csdn.net/shaokun305/archive/2004/08/25/84439.aspx</link><pubDate>Wed, 25 Aug 2004 16:30:00 GMT</pubDate><guid>http://blog.csdn.net/shaokun305/archive/2004/08/25/84439.aspx</guid><wfw:comment>http://blog.csdn.net/shaokun305/comments/84439.aspx</wfw:comment><comments>http://blog.csdn.net/shaokun305/archive/2004/08/25/84439.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/shaokun305/comments/commentRss/84439.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=84439</trackback:ping><description>中介者(midiator)模式通过提供一种松耦合的方式,解决对个对象之间复杂的交换问题..在这种模式中,只有一个类彻底清楚其他类的方法,当类发生变化时,他们会通知中介者,在由中介者将改变通知其他相关的类(对象/组件).
拿一个男人和女人通过媒人约会的例子来实现这种设计模式...:)哈哈.这就是“通俗模式"
&lt;img src ="http://blog.csdn.net/shaokun305/aggbug/84439.aspx" width = "1" height = "1" /&gt;</description></item></channel></rss>