|
Quick Lists
|
|
Bug ID:
|
6770763
|
|
Votes
|
0
|
|
Synopsis
|
Add Install Stat (pings) for JavaFX installs
|
|
Category
|
java_deployment:download
|
|
Reported Against
|
|
|
Release Fixed
|
6u12(b03)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
2-High
|
|
Related Bugs
|
|
|
Submit Date
|
12-NOV-2008
|
|
Description
|
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.
Posted Date : 2008-11-12 19:45:57.0
|
|
Work Around
|
N/A
|
|
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.
Posted Date : 2008-11-17 20:53:34.0
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
Posted Date : 2008-12-06 01:44:57.0
|
|
Comments
|
Submitted On 24-DEC-2008
Please be careful when doing this because there are customers who have a secured network (no internet access) and want offline installations to go smooth without checking back home.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |