> Most of the AOP engines in Java don't use dynamic proxies anymore; they
> prefer to do direct bytecode manipulation, which really doesn't give a whit
> whether methods are virtual or not. (See Javassist and AspectJ for
> references.)
Ok, though these require special compilers, correct? I think I indeed
overexxagerated a bit with respect to dyn. proxy, it's just that I couldn't
find a way without disadvantages to weave in methods at compile time either.
The thing is that what I'm after, and I think everyone in AOP, DI or O/R
mapper land, is that it should be transparent and pluggable when you want,
like weaving in metrics testers and what not at runtime without effort nor
requirements that the code running has to be recompiled or rewritten with
factories.
As the CLR could offer facilities for this without effort, I've always
wondered why this hasn't been added, besides the eventual security risk.
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
