JDK-6684361 : splashscreen.[so|dll] error messages should be L10N'able, and be able to be reported under javaw
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-04
  • Updated: 2018-09-05
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-6603312 - Segmentation fault running java -jar SwingSet2.jar in 256 color mode
Relates :  
JDK-6685121 - (launcher) make ReportErrorMessages accessible by other launcher subsystems
Description
Currently the splashscreen native library uses a plain fprintf(stderr, "") approach to report any critical issues. Actually the library should be considered a part of the java launcher, and hence it should use the launcher error reporting facilities:

1. The error message texts should be located in emessages.h file. This might enable L10N of the messages.
2. To report the warnings and errors we should use the ReportErrorMessage function in java.h. This enables to report the messages correctly even if we're running under javaw.
Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
EVALUATION The fix depends on CR 6685121. As soon as it is fixed, we can proceed with this CR.
22-05-2008
EVALUATION See the description.
04-04-2008