JDK-6770763 : Add Install Stat (pings) for JavaFX installs
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-11-12
  • Updated: 2010-09-17
  • Resolved: 2008-12-21
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.
6u12 b03Fixed 7Fixed
JavaFX team requests insertion of omniture pings (Install Stats) for the three cases of JavaFX installation into the common deployment cache:
1.) Installation triggered by Java Installation.
2.) Installation triggered by JavaFX Auto Update.
3.) Installation triggered on demmand by use of JavaFX applet or Java Web Start application.

In each case, we would send send 2 pings to omniture, one when installation begins, and second ping saying installation completed or got some error.

There should also be 2 pings that can come from JavaFX eula code, but they are implemented in the javaFX libraries and are not part of this RFE.

EVALUATION we will address JRE preload and auto-update case in 6u12. on-demand case is for 6u14 and javafx 1.5 engineering spec: http://j2se.sfbay.sun.com/web/bin/view/Deployment/JavaFXPing

EVALUATION for the on demand case, there really is no such thing as install completed, since any subset of the lazily loaded extensions may be used by an app - we need to define this further.