Hi Phillip,
I have been started using the AspectJ.At first is was a painful
experience.In addition most of the IDE at the time I was using it , does not
support AspectJ.You 'll need to really understand the concept before using
it. It approach is similar to the Paradigm in Eiffel ( Design by Contract
).Also to look into is Jcontract which share a similiarity with AspectJ.But
the difference it AspectJ is free and you won't have the first class
commercial support specificially tailored for you only.
The rest than that is a good and economical tool for the
developer.It is more like a 'contract' added to the existing java api.So if
you use the ide which always check your syntax it will fail to recognise the
aspectJ api/syntax.
In term of learning curve is all depend on where you are and
the nature of your job.If you're in R & D department or architect or similar
post then you'll have the time to play around with the new tool and share
your knowledge woth others.Otherwise I guess unless you're very keen on it ,
you'll need someone to teach you or drop the ideal off ... and start working
on the conventional verification method i.e by QA or buy sometime like
Jtest for instance.
Regards,
Kok Cheong
-----Original Message-----
From: Phillip DuLion [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 10:37 PM
To: jdjlist
Subject: [jdjlist] AspectJ and AOP in JUnit, JBoss, etc.
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
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
