Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Re: Detecting methods being called in the execution of another method (Dale Asberry)

This seems to be the classic case of trying to use AspectJ to police the existing hand-coded implentation of a cross-cutting concern (in your case the use of a JDBC connection manager) versus implementing that concern using aspects. I have experienced the same problem when trying to police a logging scheme e.g. do both entry & exit exist, are we passing the right arguments, etc. AspectJ is good at policing statically determinable policies e.g. layered architecture but falls short for more dynamic policies as we have seen with declare warning/error. I don't think this is a problem. I think it's better to implement a complex policy with an aspect than tell a human they are getting it wrong although I suspect you may just be using AspectJ in your sandbox/build and not deploying it.

Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM Hursley Park, Winchester,  SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
http://w3.hursley.ibm.com/~websterm/

Back to the top