AOP Design Pattern Examples - Release Notes



Version 1.11 - April 2004


Minor Updates
=============

- Added an AspectJ implementation for the Facade pattern.
- Extended the AspectJ implementation for FactoryMethod
- Renamed role methods in the Java implementation of the Observer pattern
  to comply with the new naming scheme (see below).  




Version 1.1 - February 2004


General Information
===================

- Please refer to the readme file(s) in /docs for details on how to
  run the examples.
  
- Currently, the individual examples all contain a Main class which
  acts as the driver for the example. It also includes a description
  of the example setup (in ajdoc).



Changes from version 1.0
========================


Structural changes:

	The directory structure of the examples has changed. This is to 
	reflect the proper package name fo the various examples. In
	addition, the folder "docs" now contains readme files.
	
Changes to the examples:

	Some example implementations have been changed to either make the
	Java and AspectJ implementations more similar (and thus more
	comparable), to provide a better motivation for the examples (i.e.,
	avoiding non-descriptive type names), or to show additional facets
	of a given solution.
	
Name changes:

	Some implementations in the 1.0 version used role names from pattern 
	descriptions as actual type names. For example, the Abstract Factory
	pattern example contained a class called AbstractFactory. This makes
	it difficult to distinguish between the implementation level (i.e.,
	concrete types) and the design pattern level (abstract types). All
	examples now use type names different from role names.
	
	Note that some AspectJ library implementations use empty interfaces
	internally to describe roles. In these cases, it is actually a good
	thing to be able to use the same names for these abstract concepts as
	the pattern role names (since they are not bound to a particular
	example, but to a general pattern implementation).  
	
ajdoc documentation changes:

	The existing ajdoc documentation has been corrected (where necessary)
	and extended. All ajdoc comments now consistently use italics to 
	indicate elements from the abstract pattern description as provided
	by the Design Patterns (GoF) book. Names from the concrete examples
	(usually type names) are represented by unispaced code font.
	
	Note that ajdoc is not compatible with the latest AspectJ releases.
	Fortunately, the AspectJ team is working on an updated version of 
	ajdoc. We will provide the HTML documentation when the new ajdoc has
	been released. 
	
Other changes:

	The license statement included in every file now contains the web
	address of the AOP design pattern home page.