[kepler-dev] Kepler and AOP

[Edward A. Lee]

Thomas Feng (cc'd here) has done some work on this...
He started with AspectJ to implement a backtracking mechanism,
but then went a different route.  See:

http://ptolemy.eecs.berkeley.edu/publications/papers/06/incrementalCheckpointing_WSC06/index.htm

He is currently working a model transformation infrastructure
that in some ways becomes an actor-oriented (or block-diagram-oriented)
version of aspects...

Edward

At 05:13 AM 11/25/2007, Paul Allen wrote:
>Hi all,
>
>I'm wondering if anybody has taken an AOP (Aspect Oriented Programming, 
>http://en.wikipedia.org/wiki/Aspect_oriented) approach to extending Kepler? 
>For example, I think that it might not be too hard to layer a monitoring 
>scheme for actors on top of Kepler by using AOP with appropriate pointcuts. 
>After all, AOP is meant to deal with cross-cutting concerns without 
>completely re-implementing APIs to accomplish that. AspectJ 
>(http://en.wikipedia.org/wiki/AspectJ) is the most widely known Java 
>implementation of AOP.
>
>-Paul
>
>_______________________________________________
>Kepler-dev mailing list
>Kepler-dev at ecoinformatics.org
>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev

------------ 
Edward A. Lee
Chair of EECS and Robert S. Pepper Distinguished Professor
231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
phone: 510-642-0253, fax: 510-642-2845
eal at eecs.Berkeley.EDU, http://www.eecs.berkeley.edu/Faculty/Homepages/lee.html