[jug-discussion] More Shameless Self Promotion

2005-05-18 Thread Lesiecki Nicholas
IBM developerWorks has published both parts of Nick Lesiecki’s two-part
article series Enhance design patterns with AspectJ. This article is a
part of the peer-reviewed [EMAIL PROTECTED] series.

In this article, Nick shines a new light on traditional OO design patterns
from an AOP perspective:

For OOP, we have the GoF patterns, which give us a consistent, though
sometimes cumbersome, way of working with common concepts like observers
and decorators. AOP builds on OOP to give us a direct way of expressing
crosscutting concerns. It turns out that some of the GoF patterns are about
crosscutting and can be expressed directly in AOP. So what you'll notice is
that some of the patterns that involve many classes can be expressed with a
single aspect. Some patterns become easier to use because they involve less
code. Some are so well supported that they almost disappear.

As series lead (and author of the article), I welcome commentary from the
community regarding individual articles and the series as a whole.

Read the article :
http://www-128.ibm.com/developerworks/java/library/j-aopwork5/

Read the series:
http://www.ibm.com/developerworks/search/searchResults.jsp?searchType=1searchSite=dWsearchScope=javaZ[EMAIL
 PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jug-discussion] More Shameless Self Promotion

2005-05-18 Thread jon
All this from the man who brought us
com.eblox.AssholeException;
Gratz Nick, you know I love you
On May 18, 2005, at 9:48 AM, Lesiecki Nicholas wrote:
IBM developerWorks has published both parts of Nick Lesieckis two- 
part
article series Enhance design patterns with AspectJ. This article  
is a
part of the peer-reviewed [EMAIL PROTECTED] series.

In this article, Nick shines a new light on traditional OO design  
patterns
from an AOP perspective:

For OOP, we have the GoF patterns, which give us a consistent, though
sometimes cumbersome, way of working with common concepts like  
observers
and decorators. AOP builds on OOP to give us a direct way of  
expressing
crosscutting concerns. It turns out that some of the GoF patterns  
are about
crosscutting and can be expressed directly in AOP. So what you'll  
notice is
that some of the patterns that involve many classes can be  
expressed with a
single aspect. Some patterns become easier to use because they  
involve less
code. Some are so well supported that they almost disappear.

As series lead (and author of the article), I welcome commentary  
from the
community regarding individual articles and the series as a whole.

Read the article :
http://www-128.ibm.com/developerworks/java/library/j-aopwork5/
Read the series:
http://www.ibm.com/developerworks/search/searchResults.jsp? 
searchType=1searchSite=dWsearchScope=javaZ[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]