<?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: Aspect-oriented programming with AspectJ</title>
	<atom:link href="http://saulosilva.com/2009/03/aspect-oriented-programming-with-aspectj/feed/" rel="self" type="application/rss+xml" />
	<link>http://saulosilva.com/2009/03/aspect-oriented-programming-with-aspectj/</link>
	<description>On technology, programming, et cetera</description>
	<lastBuildDate>Wed, 01 Dec 2010 03:53:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Saulo</title>
		<link>http://saulosilva.com/2009/03/aspect-oriented-programming-with-aspectj/comment-page-1/#comment-209</link>
		<dc:creator>Saulo</dc:creator>
		<pubDate>Tue, 31 Mar 2009 17:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://pensador.org/?p=276#comment-209</guid>
		<description>I see what you mean. As I wanted to get into a simple practical example quickly, I might have provided a rather unsatisfactory definition (for a layman, at least).

Thanks much for reading the article and thanks for your comments.</description>
		<content:encoded><![CDATA[<p>I see what you mean. As I wanted to get into a simple practical example quickly, I might have provided a rather unsatisfactory definition (for a layman, at least).</p>
<p>Thanks much for reading the article and thanks for your comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saulo</title>
		<link>http://saulosilva.com/2009/03/aspect-oriented-programming-with-aspectj/comment-page-1/#comment-208</link>
		<dc:creator>Saulo</dc:creator>
		<pubDate>Tue, 31 Mar 2009 17:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://pensador.org/?p=276#comment-208</guid>
		<description>I agree–you can really break encapsulation with AspectJ if you are not careful.</description>
		<content:encoded><![CDATA[<p>I agree–you can really break encapsulation with AspectJ if you are not careful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fogus</title>
		<link>http://saulosilva.com/2009/03/aspect-oriented-programming-with-aspectj/comment-page-1/#comment-57</link>
		<dc:creator>fogus</dc:creator>
		<pubDate>Tue, 31 Mar 2009 15:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://pensador.org/?p=276#comment-57</guid>
		<description>&lt;blockquote&gt;...an aspect can be used to implement a concern that is crosscutting among different components.&lt;/blockquote&gt;

I was a little worried when I read this as it is one of those self-licking lollipop kind of definitions that only makes sense if you already know what AOP means.  However, you pull it together after that and explain the essentials nicely.
-m</description>
		<content:encoded><![CDATA[<blockquote><p>&#8230;an aspect can be used to implement a concern that is crosscutting among different components.</p></blockquote>
<p>I was a little worried when I read this as it is one of those self-licking lollipop kind of definitions that only makes sense if you already know what AOP means.  However, you pull it together after that and explain the essentials nicely.<br />
-m</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Achim Demelt</title>
		<link>http://saulosilva.com/2009/03/aspect-oriented-programming-with-aspectj/comment-page-1/#comment-56</link>
		<dc:creator>Achim Demelt</dc:creator>
		<pubDate>Mon, 30 Mar 2009 15:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://pensador.org/?p=276#comment-56</guid>
		<description>Good summary, and I completely share your concerns. I really love the AO paradigm, but AspectJ is simply too powerful. The Java programming language is too low-level for successful AO application.

I prefer applying aspects on a higher level of abstraction (e.g. models). Under no circumstances must aspects be allowed to break the encapsulation of classes or components.</description>
		<content:encoded><![CDATA[<p>Good summary, and I completely share your concerns. I really love the AO paradigm, but AspectJ is simply too powerful. The Java programming language is too low-level for successful AO application.</p>
<p>I prefer applying aspects on a higher level of abstraction (e.g. models). Under no circumstances must aspects be allowed to break the encapsulation of classes or components.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

