The closest thing I've found to a real-world usage for "normal" AOP was
temporary debugger-like pointcuts via AspectJ.
By "normal" I mean via AspectJ, XML, or the like.
Targeted byte-code weaving via ASM is daunting, but truly useful in very
limited cases.
On 12/20/2011 5:28 PM, Kevin Wright wrote:
In general though I distrust and avoid AOP -- until it's really
the only alternative.
I have yet to see either a theoretical or real-world usage of AOP
where it's not just a hack to deal with the lack of first-class &
higher-kinded functions.
Bring on the closures and method handles already, then it'll *never*
be the only alternative!
Or, if impatient, just use groovy/scala/clojure/jruby/mirah. If
you've gone AOP then you're already using a different language, either
AspectJ or - far, far worse - XML [1]. Seeing as you're flipping
language anyway, at least flip to a decent one :)
[1] e.g. defining pointcuts in Spring
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
