Tuesday, April 12, 2005
AOP Presentation
AOP presentation at SD Forum, April 5th by Mr. Ramnivas Laddad
Similar presentation can be found on "IT Conversations" web site http://www.itconversations.com
Q What does AOP bring to the table ?
A. Way for a number of common use properties or 'aspects' of different objects to be implemented in one place; examples:
Profiling, thread safety checks, logging, transactions etc.
The basic design of AOP requires compiler modification, use of a java compiler with AOP keywords / enhancements. There are other ways to achieve this result, described later. However, AOP always results in some level of code instrumentation to add the 'aspect' code to each function call, even to the granularity of each instruction.
Mr. Laddad also showed how it was possible to add AOP support to 'eclipse' development environment.
Core concepts of AOP:
a) Join Point: Identifiable point of execution
b) Point cut: Selection where to apply the aspect
c) Advice: the actual implementation of aspect
No doubt that these terms sound funny in first look, the useful one to look at is (b): how to filter only those statements where you want AOP to apply.
Three different ways to add AOP into code:
1. New keywords based: need aspectj compiler
2. Metadata /XML based: new class added to code, plain javac compiler
3. Binary weaving: on pre compiled code
(2) and (3) are somewhat similar in terms of implementation, both acting at either link or load time into the code.
Apspectj should make life easy for you !
The talk presenter, Mr. Ramnivas Laddad has given number of AOP talks in the past, and has many more in the offering. Regular contributor to IBM developerworks, also has his own site: http://ramnivas.com
Similar presentation can be found on "IT Conversations" web site http://www.itconversations.com
Q What does AOP bring to the table ?
A. Way for a number of common use properties or 'aspects' of different objects to be implemented in one place; examples:
Profiling, thread safety checks, logging, transactions etc.
The basic design of AOP requires compiler modification, use of a java compiler with AOP keywords / enhancements. There are other ways to achieve this result, described later. However, AOP always results in some level of code instrumentation to add the 'aspect' code to each function call, even to the granularity of each instruction.
Mr. Laddad also showed how it was possible to add AOP support to 'eclipse' development environment.
Core concepts of AOP:
a) Join Point: Identifiable point of execution
b) Point cut: Selection where to apply the aspect
c) Advice: the actual implementation of aspect
No doubt that these terms sound funny in first look, the useful one to look at is (b): how to filter only those statements where you want AOP to apply.
Three different ways to add AOP into code:
1. New keywords based: need aspectj compiler
2. Metadata /XML based: new class added to code, plain javac compiler
3. Binary weaving: on pre compiled code
(2) and (3) are somewhat similar in terms of implementation, both acting at either link or load time into the code.
Apspectj should make life easy for you !
The talk presenter, Mr. Ramnivas Laddad has given number of AOP talks in the past, and has many more in the offering. Regular contributor to IBM developerworks, also has his own site: http://ramnivas.com
JDNC presentation
Pres 1: JDNC (Java Desktop network components) presented by one of contributors
JDNC is open source project focussed on closer and more powerful representation of database elements on the GUI. Mainly use J2SE and swing to give higher level APIs
Contrasted with JDO, JDNC is 'DB aware' and bypasses 'object model' in middle, directly think about DBMS.
The presenter talked about DataRelation: DataSet composed of DataTables : DataRows, DataColumns etc. Very DB centric.
DataModel is about "Data Aware components"; binding capabilities: PropertyChangeListernes , InputVerifiers etc.
Demo showed multiple package selection, union/intersection of different tables done in a snap.
Overall, not too impressive as the product is a very niche piece, very far away from my domain today...
JDNC is open source project focussed on closer and more powerful representation of database elements on the GUI. Mainly use J2SE and swing to give higher level APIs
Contrasted with JDO, JDNC is 'DB aware' and bypasses 'object model' in middle, directly think about DBMS.
The presenter talked about DataRelation: DataSet composed of DataTables : DataRows, DataColumns etc. Very DB centric.
DataModel is about "Data Aware components"; binding capabilities: PropertyChangeListernes , InputVerifiers etc.
Demo showed multiple package selection, union/intersection of different tables done in a snap.
Overall, not too impressive as the product is a very niche piece, very far away from my domain today...
