[8u60, 9] Review request for RT-40482: The image in application rotates only 1 time, but the image in browser rotates all the time.
Jim, Could you please review the fix: https://javafx-jira.kenai.com/browse/RT-40482 The patch is inline in JIRA. Thanks, Vadim
Re: slightly ot: java9 runtime images
On 07.05.15 14:27, Tom Eugelink wrote: On 7-5-2015 02:15, Danno Ferrin wrote: You can already do some of that today with Java 8 and the Java Packager. You can create a file tree that can be zipped up that includes the runtime and all of the application files, as well as native installers for windows, linux, and mac that will install this file tree (or “image”). We haven’t announced many public plans for Java 9 yet (since many parts are still TBD) so I cannot comment on how jigsaw and java packager will integrate, but I would expect that they will work together in some fashion. From all the documentation I find, I understand that even though with Java packager you can create an executable including the (required parts of the) JVM, you still need to unpack and repack all the jars into a single jar. This has the problem of breaking signed jars. Classloader based solutions like onejar get into all kind of conflicts with possible other classloaders in the application. No this is not required - we are even packaging Equinox-OSGi-Applications who consist of 30 different jars. Tom -- Thomas Schindl, CTO BestSolution.at EDV Systemhaus GmbH Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck http://www.bestsolution.at/ Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
Re: slightly ot: java9 runtime images
[...] In 8u40 we added an option to install your application as service or daemon, so you can use the java packager to install your microsoervices. [offtopic] Interesting where is this documented - google did not show up any results? Do I get callbacks in my Java code to react on a shutdown request? Tom -- Thomas Schindl, CTO BestSolution.at EDV Systemhaus GmbH Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck http://www.bestsolution.at/ Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
Re: slightly ot: java9 runtime images
On May 7, 2015, at 6:27 AM, Tom Eugelink t...@tbee.org wrote: On 7-5-2015 02:15, Danno Ferrin wrote: You can already do some of that today with Java 8 and the Java Packager. You can create a file tree that can be zipped up that includes the runtime and all of the application files, as well as native installers for windows, linux, and mac that will install this file tree (or “image”). We haven’t announced many public plans for Java 9 yet (since many parts are still TBD) so I cannot comment on how jigsaw and java packager will integrate, but I would expect that they will work together in some fashion. From all the documentation I find, I understand that even though with Java packager you can create an executable including the (required parts of the) JVM, you still need to unpack and repack all the jars into a single jar. This has the problem of breaking signed jars. Classloader based solutions like onejar get into all kind of conflicts with possible other classloaders in the application. I don’t know where you got your information, it has never been the case for as long as i’ve used it and worked on it before my employ at Oracle that you have to rely on a single jar for Java Packager. Repacking jars is completely unneeded and the Java Packager takes the library jars you provide without alteration, preserving external signatures and structure essential to stuff like OSGi. In fact, you can provide assets that are not jars and you can set the class path to only include certain jars, no need to unpack jars at runtime. It would be a major improvement (not only for JavaFX applications, but also standalone servers) if it would become possible to create a truly single distributable, without having to repack the jars. So either by automatic unpacking to a tmp and setting the classpath prior to stating java (cleaning up afterwards), or allowing jars-in-jars or jars-in-distributable. In 8u40 we added an option to install your application as service or daemon, so you can use the java packager to install your microsoervices.
Re: slightly ot: java9 runtime images
On 7-5-2015 15:52, Danno Ferrin wrote: I don’t know where you got your information, it has never been the case for as long as i’ve used it and worked on it before my employ at Oracle that you have to rely on a single jar for Java Packager. Repacking jars is completely unneeded and the Java Packager takes the library jars you provide without alteration, preserving external signatures and structure essential to stuff like OSGi. In fact, you can provide assets that are not jars and you can set the class path to only include certain jars, no need to unpack jars at runtime. That is good to hear. It is hard to retrace all the sites I visited this morning, but this was one of them. http://java.dzone.com/articles/creating-executable-uber-jar%E2%80%99s Tom
Re: slightly ot: java9 runtime images
On 7-5-2015 16:44, Mike Hearn wrote: Do you actually need JAR signatures anyway? The JVM is bundled, it's not like you have to pass some system security policy beyond Gatekeeper/Windows code signing. Well, I remember the official Sun mail.jar being signed and causing headaches if it was repacked. But the newer mail.jar is no longer signed, so maybe it is less of an issue now than back when I wrote the appjar tool (unpack a jar-of-jar to a tmp folder). Time to update my knowledge then. Tom
Re: slightly ot: java9 runtime images
Do you actually need JAR signatures anyway? The JVM is bundled, it's not like you have to pass some system security policy beyond Gatekeeper/Windows code signing.
Re: slightly ot: java9 runtime images
I looked at the man pages, and it’s not there. That is strange because I remember working with the docs people to get them the info they needed. The best docs are from my JavaOne presentation: https://oracleus.activeevents.com/2014/connect/fileDownload/session/3B139AAF656DC1741328669FE873981E/CON2247_Ferrin-8u20%20packager.pdf https://oracleus.activeevents.com/2014/connect/fileDownload/session/3B139AAF656DC1741328669FE873981E/CON2247_Ferrin-8u20%20packager.pdf As far as java callbacks… the support is fairly basic at the moment. You own the JVM w/o a security sandbox so you can add standard shutdown hooks as well as other libraries that react to unix signals. Signals are non-standard as the current Java signal classes exist in sun.misc.*, hence they an internal API and will not be accessible in JDK 9 (without contortions). For windows a custom service executable is created. For Linux init.d scripts are added. For Mac launchd is used. On May 7, 2015, at 8:04 AM, Tom Schindl tom.schi...@bestsolution.at wrote: [...] In 8u40 we added an option to install your application as service or daemon, so you can use the java packager to install your microsoervices. [offtopic] Interesting where is this documented - google did not show up any results? Do I get callbacks in my Java code to react on a shutdown request? Tom -- Thomas Schindl, CTO BestSolution.at EDV Systemhaus GmbH Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck http://www.bestsolution.at/ Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
Re: slightly ot: java9 runtime images
On 7-5-2015 02:15, Danno Ferrin wrote: You can already do some of that today with Java 8 and the Java Packager. You can create a file tree that can be zipped up that includes the runtime and all of the application files, as well as native installers for windows, linux, and mac that will install this file tree (or “image”). We haven’t announced many public plans for Java 9 yet (since many parts are still TBD) so I cannot comment on how jigsaw and java packager will integrate, but I would expect that they will work together in some fashion. From all the documentation I find, I understand that even though with Java packager you can create an executable including the (required parts of the) JVM, you still need to unpack and repack all the jars into a single jar. This has the problem of breaking signed jars. Classloader based solutions like onejar get into all kind of conflicts with possible other classloaders in the application. It would be a major improvement (not only for JavaFX applications, but also standalone servers) if it would become possible to create a truly single distributable, without having to repack the jars. So either by automatic unpacking to a tmp and setting the classpath prior to stating java (cleaning up afterwards), or allowing jars-in-jars or jars-in-distributable. Just my 2 cents, Tom
