All, As I've perused the various technologies out there, I've increasingly encountered references and usage of AOP (Aspect-Oriented Programming). Though I've not downloaded JBoss, I have seen statements about it having a significant amount of AOP code. I've also seen the strategy of using AspectJ as a method of isolating tested code for JUnit test cases. This second useage interested me enought to go out and buy "Mastering AspectJ."
In all the spare time I've had to read it, however, I've only managed to scratch the surface of that book. The language is starting to make more sense, but it doesn't seem to be intuitive enough that it would inspire my current or past clients to accept it. In addition, the idea of AspectJ's modification of byte code after javac or at runtime would probably trigger significant concern during external reviews (based on my one-time experience when I was in a hurry and used BCEL). So I'm curious: Who out there has considered or is using it? What arguements overcame the issues around learning curve and risk concerns (i.e., saved significant $ in coding labor)? How extensively do you use it? Anyone find significant pitfalls? Thanks, Phillip. --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] http://www.sys-con.com/fusetalk
