Major browsers have discontinued support for applets, but many enterprises still rely on applet-based applications. Oracle introduced Java WebStart (JWS) as a replacement but didn’t maintain it as an open-source feature of OpenJDK. Azul continues to update a fork to IceTeaWeb, a viable alternative, to ensure compatibility and security for modern implementations. This blog post explains how to run applets without making code changes.
Java applets were once a cornerstone of interactive web applications. Introduced in the mid-1990s, they provided a way to run Java code inside web browsers, enabling dynamic content, real-time applications and enterprise solutions that required complex client-side functionality. Over time, applets became widely used in various industries, especially in financial services, healthcare and enterprise applications like Oracle E-Business Suite (EBS) and Oracle Forms.
However, as browser security tightened and the web evolved, applets fell out of favor. Major browsers removed support for Java plug-ins, and even Oracle itself discontinued support in later Java versions. Despite their decline, many enterprises still rely on applet-based applications, and finding a way to keep them running has become a significant challenge.
Common use cases for applets
While modern web applications have largely replaced applets, many critical business systems still depend on them. Some of the most notable examples include:
- Oracle EBS and Oracle Forms: These enterprise applications use Java applets for their user interface and business logic execution.
- Financial and Banking Applications: Many online trading platforms and banking systems historically used applets for secure data entry and processing.
- Industrial and Manufacturing Systems: Legacy systems in automation, quality control and monitoring often rely on applets for graphical data visualization and control panels.
- Healthcare and Scientific Applications: Many hospitals and research institutions use applet-based tools for imaging, diagnostics, and remote monitoring.
Even though alternative solutions exist, replacing an applet-based application is often expensive and time-consuming, requiring significant rewrites and business process changes. This makes migration a major concern for enterprises.
Migration path: moving from applets to Java WebStart
To address the phasing out of applets, Java WebStart (JWS) was introduced as a viable alternative. JWS allows Java applications to be deployed via a web link, but instead of running inside the browser, they execute as standalone applications on the user’s system.
Unfortunately, JWS was never open-sourced by Oracle, and is not included in OpenJDK. For businesses considering a transition from applets to JWS, Azul provides a fully supported implementation of IcedTeaWeb (ITW), which is a functionally equivalent, open-source alternative to Oracle’s discontinued Java WebStart. While the original project is no longer maintained by the community, Azul continues to update an ITW fork to ensure compatibility and security for modern implementations.
Azul’s IcedTeaWeb solution for Java WebStart applications
For enterprises looking to migrate away from applets, transitioning to Azul’s ITW-based solution may be a good approach. Because Azul continues to maintain a version of ITW, companies can benefit from:
- Regular bug fixes and security updates
- Enterprise-grade support and compatibility
- A stable migration path for existing Java applications
You can find detailed release notes on Azul’s ITW implementation here: IcedTeaWeb Release Notes.
How to run Java applets in 2025 without making code changes
While migrating applets to an ITW-based solution can be a viable option, some enterprises may not be ready to transition their applications just yet. Business-critical applications often require stability, and rewriting them or modifying deployment methods may introduce unforeseen issues.
At Azul, we recognize that many organizations still need to run applets as they are on whatever version of Java they currently use, including Java 6 and 7. That’s why Azul Platform Core offers a way to continue running Java applets with no code changes, minimal modifications, and no disruptions. This solution ensures that:
- Existing Java applets can continue to run despite the lack of modern browser support.
- There is no need for costly rewrites or migration efforts.
- Enterprises can maintain their business processes without interruptions.
Azul’s approach allows companies to extend the life of their applet-based applications while planning long-term migration strategies at their own pace.
Viable paths forward for applets
Organizations relying on Java applets have multiple options available to them. The best approach depends on your business needs, resources, and long-term IT strategy:
- Migration to other technologies: Rewriting applications in modern web frameworks (such as Angular, React, or Blazor) offers a long-term solution.
- Migration to JWS: While JWS has been discontinued by Oracle, you can still use Azul’s IcedTeaWeb solution to migrate applets to a JWS-like implementation.
- Keep running applets with Azul: Leverage Azul Platform Core to continue running applets with minimal modifications.
Conclusions: Java applet support
Java applets may be considered a thing of the past, but many enterprises still need them for their mission critical applications. Whether you choose to migrate to JWS, rewrite your applications, or continue running applets with Azul, there is a solution available to fit your needs.
Azul is committed to providing enterprise-grade Java solutions and support that ensure continuity, performance and security for businesses relying on Java technology.
👉 Interested in learning more? Contact us today to discuss your options for keeping Java applets running smoothly.
