Chris Richardson (author of Pojos in Action) in his blog tell us about Simplifying Spring XML with Arid Framework. This is a very interesting idea, and it's on the same line as actual trends about "Convention over Configuration".
This approach to the problem, it's based in autowire and custom namespace in Spring 2.0 XML.
I don't like especially autowire by type, it's useful for test proposes, but when you have two classes that implements the same interface, you must disabled. I see beginners developers crash with this, many times in test classes.
Another very useful thing about classic Spring XML, it's that you have a mirror of the architecture. You can use Spring IDE or another tool to see the real architecture, not an obsolete UML diagram. With annotations or conventions it's more difficult to see the architecture.
In my humble opinion, with expert developers Arid framework and other solutions about Convention over Configuration can be fantastic, but with beginners the best approach is the classic style.
No comments:
Post a Comment