best practices pertaining to NullPointerException
Posted on 2006-06-15
Any thoughts on best practices pertaining to NullPointerException handling...
Should all methods make it their business to be null-safe in order to be robust and invokable by any future client code that may feed it null input OR is it better to not trash up the code and to just always make sure that there's a code layer (such as validation) that handles null input and to allow the rest of the code to not handle null input.
It has become a point of contention on our team, so I decided to turn this matter over to you, experts.