JDK-7075885 : Improve ErrorEvent support
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7-client
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-08-06
  • Updated: 2011-09-22
  • Resolved: 2011-08-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 JDK 8
7u2 b03Fixed 8Fixed
Description
Current handling of error events has some inconsistencies. 
In particular:
   - if preloader is not fully initialized by the time error is generated then error could be visulaized by default preloader.
     And yet this may not about custom preloader initialization. So eventually it could become visible ...

   - sometimes user decisions (e.g. decline to grant permissions) are echoed as additional error event on attempt to exit

Comments
EVALUATION To make behavior consistent we can wait for custom preloader to init before handling error events. If custom preloader fail itself we will use default preloader and submit all pending events to it. I.e. only one preloader will be active at the time. Exceptions we use to notify about exit requests as reaction to user action are marked silent. We do not need to notify preloader about them as errros ...
06-08-2011