I read Cédric's latest blog entries which mention Aspectwerkz. I was able to very quickly peruse the documentation today and I think it's the first time I have a clear and concise idea of what AOP could buy me without going down XML-config hell and having too much code to write. Even more so, contrary to what I wrote in my very first entry here (basically that I figured it was to difficult to introduce to programming teams) I believe that this could in fact be used in real life, real soon.
I think the reason is that you actually don't need the whole development team to understand it from outset to get it to work (quite unlike introducing a new technology like EJBs or Hibernate or others where everyone must get up to par at the same time).
Not everyone will be writing aspects as a daily activity and aspects are... well... things that are disjoint from the actual business logic so you don't everyone working on them all the time. You can probably get your few "cutting-edge" developers to work on it and let the word spread in the team...
I can really see the Logging advice being useful for us because the legacy app I am working on is sometimes deficient in that area. I can also see security being enforced throughout an application be done using this, even outside of the EJB framework.
My final question is : how dangerous would it be to run our weblogic production servers with Aspectwerkz once it finalizes ? Would it even be possible given the way apps are deployed in the server... I'll have to investigate.
Posted by pgirolami76 at April 12, 2003 01:38 PM | TrackBack