CSC/ECE 517 Fall 2010/ch3 3d mr: Difference between revisions
No edit summary |
No edit summary |
||
Line 15: | Line 15: | ||
* Aspects - Classes that implement functionality needed in many parts of a program, but are not part of the business logic or core concern of the program. | * Aspects - Classes that implement functionality needed in many parts of a program, but are not part of the business logic or core concern of the program. | ||
* Advice - Aspect methods or code to be applied around existing business logic. | * Advice - Borrowed from AspectJ terminology, refers to Aspect methods or code to be applied around existing business logic. | ||
* Join Point - Places in the core business logic that advice should be applied or wrapped around. | * Join Point - Places in the core business logic that advice should be applied or wrapped around. | ||
Line 21: | Line 21: | ||
== The AspectR API == | == The AspectR API == | ||
AspectR provides a simple mechanism for wrapping methods in a program. One begins by creating an "aspect" class that inherits from the AspectR Aspect class. | AspectR provides a simple mechanism for wrapping methods in a program. One begins by creating an "aspect" class that inherits from the AspectR Aspect class. For example, we define a new aspect class to implement a code profiler: | ||
=== | require aspectr.rb | ||
include AspectR | |||
class Profiler < Aspect | |||
end | |||
You then define the wrapper methods which will be called at the join points in the program. These methods are called Advice methods. | |||
def method_start(method, object, exitstatus, *args) | |||
@begin = Time.now | |||
end | |||
def method_end(method, object, exitstatus, *args) | |||
timeElapsed = Time.now - @begin | |||
puts "#{object.class}.#{method} took #{timeElapsed} secs" | |||
end | |||
profiler = Profiler.new | |||
AspectR currently supports only two method join points, <code>PRE</code> and <code>POST</code>. Given the simple example, | |||
class SomeClass | |||
def some_method | |||
puts "hello" | |||
sleep 5 | |||
end | |||
end | |||
One can add advice to be invoked before or after a single target method as follows: | |||
profiler.add_advice(SomeClass, :PRE, :some_method, :method_end) | |||
This advice can be removed using <code>remove_advice</code>: | |||
profiler.remove_advice(SomeClass, :PRE, :some_method, :method_end) | |||
:The AspectR API provides the <code>add_advice</code> method to add an advice method to be invoked before or after a single target method. | |||
To add an advice method to be invoked before or after a single target method, use the <code>add_advice</code> and <code>remove_advice</code> instance methods on the Aspect class: | To add an advice method to be invoked before or after a single target method, use the <code>add_advice</code> and <code>remove_advice</code> instance methods on the Aspect class: |
Revision as of 11:51, 6 October 2010
Aspect-oriented programming and AspectR
AspectR is a programming library that enables Aspect-oriented programming for Ruby programs by providing ways to wrap code around existing methods in a program. It is simpler but similar in functionality to the AspectJ library for Java, but less well known. AspectR is distributed under the GNU General Public License.
Aspect-Oriented Programming
Aspect-Oriented Programming is an approach to modularizing concerns that cut across the core concerns or business logic, of a program.
Motivation
The model code in a typical program will often contain not only the business logic but also secondary concerns such as transactions, security, logging, etc. This clutters the code in the model, making it hard to distinguish the business logic from the secondary code, complicating maintenance and reuse. Furthermore, these secondary concerns cut across multiple core concerns in the program, which violates the separation of concerns. As a result, changing to a different transaction API, for example, results in code modifications throughout the program.
Terminology
- Aspects - Classes that implement functionality needed in many parts of a program, but are not part of the business logic or core concern of the program.
- Advice - Borrowed from AspectJ terminology, refers to Aspect methods or code to be applied around existing business logic.
- Join Point - Places in the core business logic that advice should be applied or wrapped around.
The AspectR API
AspectR provides a simple mechanism for wrapping methods in a program. One begins by creating an "aspect" class that inherits from the AspectR Aspect class. For example, we define a new aspect class to implement a code profiler:
require aspectr.rb include AspectR class Profiler < Aspect end
You then define the wrapper methods which will be called at the join points in the program. These methods are called Advice methods.
def method_start(method, object, exitstatus, *args) @begin = Time.now end def method_end(method, object, exitstatus, *args) timeElapsed = Time.now - @begin puts "#{object.class}.#{method} took #{timeElapsed} secs" end
profiler = Profiler.new
AspectR currently supports only two method join points, PRE
and POST
. Given the simple example,
class SomeClass def some_method puts "hello" sleep 5 end end
One can add advice to be invoked before or after a single target method as follows:
profiler.add_advice(SomeClass, :PRE, :some_method, :method_end)
This advice can be removed using remove_advice
:
profiler.remove_advice(SomeClass, :PRE, :some_method, :method_end)
- The AspectR API provides the
add_advice
method to add an advice method to be invoked before or after a single target method.
To add an advice method to be invoked before or after a single target method, use the add_advice
and remove_advice
instance methods on the Aspect class:
add_advice (target, joinpoint, method, advice) remove_advice (target, joinpoint, method, advice)
Parameters:
target
- target classjoinpoint
- must be eitherPRE
orPOST
method
- target methodadvice
- advice method in the aspect class
To wrap both the before and after join points, and specify multiple target methods, use the wrap
and unwrap
instance methods on the Aspect class:
wrap (target, pre, post, *args) unwrap (target, pre, post, *args)
Parameters:
target
- target classpre
- advice method to call before target method invocationspost
- advice method to call after target method invocations*args
- target methods, or regular expression matching method names in the target class
Alternatively, you may wrap target methods to blocks of advice code using the wrap_with_code
instance method. Has performance advantages but cannot be unwrapped:
wrap_with_code (target, preCode, postCode, *args)
To wrap methods from multiple target classes, the AspectR library defines a global wrap_classes
method. This is an experimental method and the API is likely to change:
wrap_classes (aspect, pre, post, classes, *methods)
Parameters:
aspect
- aspect classpre
- advice method to call before target method invocationspost
- advice method to call after target method invocationsclasses
- regular expression to match target class names*methods
- target methods, or regular expression matching method names in the target classes
Methods for controlling dispatching
disable_advice_dispatching
- Disables all dispatching to advice methods by the API. Provided as an instance method so must be called on an instance of the aspect class (any instance).
dispatch?
- Indicates if dispatching to advice methods is enabled.
Specifying methods that should never be wrapped
new (never_wrap = "^$ ")
- Class method to create a new instance of the aspect class and specify methods that should never be wrapped.
wrappable? (method)
- Indicates if the specified method can be wrapped. See [new] below.
Other utility methods
The following methods are used by the API itself but also made public:
get_methods (targret, args)
prepare (target)
all_classes (regexp = /^.+$/)
- Returns all classes whose class name matches a given regular expression.
Example
The following code examples implement a code profiler to measure the duration of method calls.
AspectR
require aspectr.rb include AspectR class Profiler < Aspect def method_start(method, object, exitstatus, *args) @begin = Time.now end def method_end(method, object, exitstatus, *args) timeElapsed = Time.now - @begin puts "#{object.class}.#{method} took #{timeElapsed} secs" end end #if $0 == __FILE__ class SomeClass def some_method puts "hello" sleep 5 end end Profiler.new.wrap(SomeClass, :method_start, :method_end, /some/) SomeClass.new.some_method #end