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: | [67cat] [j2ee] Superfluous ISE about accessing file from default package in message log | ||
---|---|---|---|
Product: | serverplugins | Reporter: | giorgio42 <giorgio42> |
Component: | JBoss | Assignee: | sandiprasetyaningsih |
Status: | STARTED --- | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | error message log |
Description
giorgio42
2009-04-14 22:40:10 UTC
[Note aside: the text area in the simplified 67cat submit form should have the same width as this one to avoid this ugly line wrapping...]. If you downgrade the priority of a bug report, please add comment stating the reason. Not a bug basically - just exception in log. If you log an exception it indicates to the user that something seriously is wrong which needs investigation. Otherwise there is no point in printing the stack trace. You as the developer may know that the exception is harmless, but the user not. If you are crying fire for no reason it will become hard to decide if actually something is burning. Especially if you spam the output window 14 times with the same stack trace... So I suggest to just log an information or warning message, but not the exception. I don't think there is any disagreement - just severity is P4. BTW I'm not logging the exception. It is org.netbeans.ProxyClassLoader which is not a thing you should change on will. The warning is caused by log4j that is invoked by jboss code that is invoked by the server plugin code (so my code is not the cause and there is no way how this could be fixed in my code). Ok, thanks for the explanation (and your patience). Created attachment 103005 [details]
error message log
|