What steps will reproduce the problem?
1. Configure log4j to NOT have a root Level
2. Make an esapi logging call that WOULD normally fall through to the root
logger, but does not.
What is the expected output? What do you see instead?
We would expect to see nothing--with no level configuration on the root logger
we expect calls that would fall through to be silent, however we get an NPE.
What version of the product are you using? On what operating system?
2.1.0 on Windows && RedHat
Does this issue affect only a specified browser or set of browsers?
No.
Please provide any additional information below.
Attached a patch for fix.
Original issue reported on code.google.com by xeno6...@gmail.com on 1 May 2014 at 12:17
Original issue reported on code.google.com by
xeno6...@gmail.com
on 1 May 2014 at 12:17Attachments: