JDK-6685121 : (launcher) make ReportErrorMessages accessible by other launcher subsystems
  • Type: Enhancement
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-07
  • Updated: 2011-05-17
  • Resolved: 2011-05-17
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
7 b36Fixed
Related Reports
Relates :  
JDK-6684361 - splashscreen.[so|dll] error messages should be L10N'able, and be able to be reported under javaw
Relates :  
JDK-6603312 - Segmentation fault running java -jar SwingSet2.jar in 256 color mode
Description
In JDK7 the launcher has an error reporting functionality. This must be made
accessible to other subsystems of the launcher, for example the splashscreen
which would need to report an error. Giving this functionality will proide
a unified launcher user experience.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/tl/jdk/rev/2c65a59dd48d
27-08-2008
EVALUATION ReportErrorMessage is a private interface, the entry point needs to be exported and renamed to JLI_ReportErrorMessage so that it is consistent, with the other exported entry-points. This requires some renaming/refactoring.
07-04-2008