This content has been marked as final. Show 17 replies
i just want to follow the previous post. Does someone know the right department/person at oracle to conntact for this problem. I hope this is just a failure.
Please help and thanks in advance,
My guess is that the right person to talk to at Oracle for the jar signing issue would be Nicolas Lorain, contactable via firstname.lastname@example.org.
On the more general issue of moving on to JavaFX 2, you and I both will be very interested in the Visage project. Stephen Chin heads this and is contactable via email@example.com.
~ Chris Murphy
We are aware of this issue, and we will have a new certificate in place within a couple of weeks.
However, all JavaFX 1.3 application developers should be aware that the end of life (EOL) for the JavaFX 1.2 and JavaFX 1.3 product lines (this includes the JavaFX 1.x Runtimes, JavaFX 1.x SDKs, JavaFX 1.x Production Suite) will take place later this year.
We highly recommend you start migrating your JavaFX 1.x application to JavaFX 2.0 if you haven't done so already, as once JavaFX 1.x reaches this EOL deadline, the JavaFX 1.2/1.3 Runtimes will no longer be available to new users.
If you'd like to discuss how to manage the transition to JavaFX 2.0, you can reach me at javafx4you at sun dot com
Java Client Product Management
Santa Clara, CA, USA
Nicolas, thank you very much for a new certificate.
Please, make sure that you don't kill JavaFX 1.x until there's an official way to support JavaFX 2.0 applets on Mac and Linux!
So if we are making petitions, then mine would be please don't kill JavaFX Script until either a decent translator exists or Visage does the job.
Has anyone moved their code to Visage??
Thanks for the information.
Could it be possible from you or from Oracle to get more precision on "will take place later this year" ?
I think Oracle management like to know from their team when roadmaps ends... so do our company heads :)
We do not decide about the way javaFX has evolve, but now that we should deal with the big non-compatibility between FX1.3 and FX2.0, it would be "kind" from Oracle to say clearly when they decide to stop FX1.xx availibility.
Please help and thanks in advance,
An End Of Life announcement for JavaFX 1.x will be sent out in the next few days, and will include the date by when JavaFX 1.2 and Java 1.3 will no longer be available
Great, many thanks (for the announcement, not for EOL of javafx 1.x) ;).
Edited by: tibO on 14 févr. 2012 09:17
An update version of the JavaFX 1.2.3 and 1.3.1 runtimes, signed with a new certificate, has been released. There is no incremental version number, and JavaFX runtime downloads will work just as they did before the Sun certificate expired two weeks ago
thanks, that just saved my life.
I've tried to get the latest re-release of the 1.3.1 runtimes for the past 2 days and all I get either:
Either: after clearing javaws resource and app cache (note: with Java 1.7.0_02 and 1.7.0_03):
Or: the JavaFX runtimes files gets downloaded and when looking at them in the javaws app & resource viewer, their expiration date is marked as of today.
javaws -import http://dl.javafx.com/1.3/javafx-rt.jnlp java.lang.RuntimeException: java.lang.NullPointerException at com.sun.javaws.progress.PreloaderDelegate.waitTillLoaded(Unknown Source) at com.sun.javaws.Launcher.prepareResources(Unknown Source) at com.sun.javaws.Launcher.prepareAllResources(Unknown Source) at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source) at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source) at com.sun.javaws.Launcher.launch(Unknown Source) at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResourcesHelper(Unknown Source) at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResources(Unknown Source) at com.sun.javaws.Launcher$1.run(Unknown Source) at com.sun.javaws.LaunchDownload$3.run(Unknown Source)
Frankly I do not really know what to think; I've been complaining for months that Java Web Start is broken (in the OTN JWS forum and directly at the face of the deployment team at JavaOne 2011) but this gets ridiculous...
did you try to delete your temporary files using the Java control panel ?
As indicated before (2nd line of my message), everything has been cleared from the cache.
Now, that being said, JWS also has an habbit of screwing its own cache sometimes...