This feature adds IcedTea-Web 1.0.2 to Fedora. The IcedTea-Web project provides a Free Software web browser plugin running applets written in the Java programming language and an implementation of Java Web Start, originally based on the NetX project.
- Name: Deepak Bhole
- Email: firstname.lastname@example.org
- Targeted release: Fedora 15
- Last updated: 2011-04-11
- Percentage of completion: 100%
Previously, the Java plugin and Web Start implementations shipped in Fedora were build with the java-1.6.0-openjdk RPM as the development for those items happened in the IcedTea tree. Starting with IcedTea6 1.10 (which is in Fedora 15), the plugin and Web Start components were split into a separate project named IcedTea-Web. IcedTea-Web brings numerous functional improvements to the Java plugin and Web Start implementations in Fedora.
Benefit to Fedora
IcedTea-Web provides numerous improvements over the previous plugin and Web Start implementations shipped in Fedora. These include:
- NetX and plugin configuration can now be specified via a deployment.properties file
- System-level as well as user-level deployment.properties files with locked configuration are supported
- Applications and applets can now have a Look and Feel different from rest of IcedTea-Web
- Native directories are correctly cleaned on exit
- Cached files with special characters in file names are now handled correctly
- Interfaces javax.jnlp.IntegrationService and javax.jnlp.DownloadService2 are now available
- javaws now supports a new -Xclearcache option
- Applications with non-public main classes are now supported.
- JNLP files containing <component-desc> as well as <application-desc> will now work
- JNLP files referenced in the applet tag are now parsed to detect applet properties
- Applets are now double-buffered to eliminate flicker in ones that do heavy drawing
Furthermore, because the package no longer requires a JDK rpm respin, bug fixes will be available much sooner starting with F15.
The goal of IcedTea-Web is to allow faster distribution of fixes to end-user. The fast-turnaround goal also means that the project is a lot simpler to build. It involves simply checking out the sources from the mercurial repository at  and running configure and make and make install.