-
Bug
-
Resolution: Fixed
-
P2
-
alpha
-
None
-
1.0fcs
-
generic
-
solaris_2.6
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2113040 | alpha | J. Duke | P2 | Closed | Fixed | alpha |
Dumping a stack trace to the console is not an acceptable method of error handling in FCS software. It's fine for debugging purposes.
Though I havn't tried it, presumably providing a file or stream with invalid contents to one of the MailcapCommandMap constructors will cause the same behavior.
The net result for addMailcap is a no-op. For a file or stream, it's currently unknown if prior, or subsequent valid data will take effect.
Though I havn't tried it, presumably providing a file or stream with invalid contents to one of the MailcapCommandMap constructors will cause the same behavior.
The net result for addMailcap is a no-op. For a file or stream, it's currently unknown if prior, or subsequent valid data will take effect.
- backported by
-
JDK-2113040 MailcapCommandMap.addMailcap("&invalidString") dumps stack trace
-
- Closed
-