On Tue, 20 Dec 2011 22:40:20 +0100, Cédric Beust ♔ <[email protected]>
wrote:
I agree with the skepticism about AOP but strongly disagree about DI.
I think that DI is one of the most important things to write modular and
testable code.
For what concerns AOP, I think I disagree with others, but perhaps it's a
matter of what we mean with AOP. For sure I don't use it at full power,
e.g. to do dramatic changes to existing code. From this respect, yet, AOP
can be dangerous because it's the classic very powerful tool by which you
can kill yourself. But limited to the proper scopes, such as transactions
and security (in addition to the cited logging), it's very good. It's true
that with this limited use it's more a tool to implement a pattern (proxy
/ decorator) rather than a programming paradigm.
PS I also like it in Spring to perform DI to beans not managed by Spring
with static weaving.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
