Doing this is of great utility in certain situations, but the majority
of cases it's unneeded. Further, it's ENORMOUSLY more difficult to
implement, because the AOP engine needs to weave it's stuff into the
application code, which means it's actually changing the code you
write, rather than just adding some new code (the proxy).
AspectJ is an example of an AOP framework that does weaving, though
it's for Java. Java's static typing and explicit compile cycle with
native AST transform support (via annotations) make compile-time
weaving fairly straightforward. AspectJ also supports runtime weaving
where it manipulates the bytecode of the application as classes are
loaded into the JVM. Again, Java provides great support with runtime
annotations and a couple different bytecode stream editing packages (I
believe AspectJ uses ASM). This runtime bytecode manipulation is also
the way Hibernate achieves a lot of it's magic.
cheers,
barneyb
> --
> You received this message because you are subscribed to the Google Groups "ColdSpring-Users" group.
> To post to this group, send email to coldspri...@googlegroups.com.
> To unsubscribe from this group, send email to coldspring-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/coldspring-users?hl=en.
>
>
--
Barney Boisvert
bboi...@gmail.com
http://www.barneyb.com/