JDK-7112950 : Improve the blacklist exception message and make exception handling more consistent
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-11-17
  • Updated: 2013-09-12
  • Resolved: 2012-02-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 JDK 8
7u4Fixed 8 b26Fixed
Related Reports
Relates :  
JDK-7145672 - Unify error message between JNLP and non JNLP apps
Relates :  
JDK-7154862 - JarBlackList Exception not like as Exception in Java Console
Relates :  
JDK-7182109 - JavaWS blacklist exception message not clean
Relates :  
JDK-7112206 - Improve security dialog message when jar is blacklisted
Relates :  
JDK-7145932 - Move SystemUtils.getMethod() to a private method
Description
See comments.
Comments
SUGGESTED FIX Might suggest the following wording which would be more end user friendly: "An application component (JAR file) was blocked as requested by the vendor and the application is unable to load. Please contact the application vendor for more information." Currently the message appears only if the user clicks the Details button on an Application Error message dialog, which says nothing about the blacklist condition. This needs to be changed so that this message appears on the inital message dialog. Otherwise an end user would not be likely to discover why the application failed, and may not know to contact the application vendor -- instead they will contact us, forcing our support to track down the real issue.
08-02-2012