The Disco Blog

While defensive programming techniques (like checking if a parameter is null or not) effectively guarantees the condition of a method’s input, these conditionals become repetitive if they’re used across a wide expanse of code. In this month’s In pursuit of code quality series on IBM developerWorks, I introduce an easier way to add reusable validation constraints to your code using the power of AOP, design by contract, and a handy library called OVal. Check out “Defensive programming with AOP” and don’t forget to boogie over to the “Improve Your Java Code Quality” forum and let it all hang out, man!

Trackback this Post | Feed on comments to this Post