What steps will reproduce the problem?
1. Write an extension for ZAP
2. Register your extension to startup when ZAP starts
3. Construct code that produces an exception during initialization
What is the expected output? What do you see instead?
Expected: At least a log message with the exception being shown
Instead: Nothing, besides that the extension is not loaded and there is no
indication why...
What version of the product are you using? On what operating system?
Java 7 on OS X with ZAP 2.0.0
Please provide any additional information below.
The code which suppresses the exception being shown is in
org.zaproxy.zap.control.AddOnLoader.java, Line 460:
logger.debug(e.getMessage(), e);
It is written there that: //Often not an error
but since the debug-stream is usually not displayed in the console and
redirecting the exceptions to debug there effectively supresses ALL exceptions
occuring in extensions during initialization - which could be potentially
dangerous.
Original issue reported on code.google.com by marcel.k...@gmail.com on 22 Apr 2013 at 12:17
Original issue reported on code.google.com by
marcel.k...@gmail.comon 22 Apr 2013 at 12:17