Well then I'd rather have getMortarScope() throw if the scope is destroyed. A NullPointerException is less informative then a clear "the scope has been destroyed" exception. I call this "Null Driven Development" :-P