This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | surround with try/catch adds poor code | ||
|---|---|---|---|
| Product: | java | Reporter: | Vince Kraemer <vkraemer> |
| Component: | Hints | Assignee: | Jan Lahoda <jlahoda> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
The javadoc speaks about default exception handling - so this does not strictly relate to explicit exception handling. Anyway, using FINER as default seems like sweeping problem under the rug. There is enhancement #116818 about more flexible (e.g. user customizable) logger statement. this is really a dup of 116818 *** This issue has been marked as a duplicate of 116818 *** |
When I use the surround with try/catch hint, I see the following code generated in the catch... catch (MethodCException ex) { Logger.getLogger(NewClass.class.getName()).log(Level.SEVERE, null, ex); } This use of log is not correct with respect to the recommended use of logging. It looks like the javadoc for Level would recommend using Level.FINER... See http://java.sun.com/j2se/1.5.0/docs/api/java/util/logging/Level.html#SEVERE and http://java.sun.com/j2se/1.5.0/docs/api/java/util/logging/Level.html#FINER...