What steps will reproduce the problem?
1. In some instances, the NHINDException is being created without setting an
error code. When an exception logger encounters this scenario and attempts to
print the error, a null pointer exception is thrown.
What is the expected output? What do you see instead?
It would be optimal if the NHINDException class defaulted to some exception
state upon initialization.
Original issue reported on code.google.com by gm2...@cerner.com on 27 Jan 2014 at 2:40
Original issue reported on code.google.com by
gm2...@cerner.com
on 27 Jan 2014 at 2:40