We spent too long hunting down a bug in a database method call that consistently returned “null” in our integration environment, but returned the correct value in a development unit test.
Do you see the problem here? Compare these two screenshots. Both screenshots show a look into two different jars on our classpath. The title of this article is a big hint.
Two points goes to the first person to explain the problem. (-2 points for any of my teammates that answer first!)
The moral of the story is that namespaces are one heck of a good idea and that we should always be very careful when relying on classpath-based resources.Â I’ll write more about the problem after giving others a chance to solve the puzzle.