What if moving your Java desktop app to the web didn’t require a full rewrite?

If you’re maintaining a Swing, JavaFX, Eclipse RCP, or even Oracle Forms application, you’ve probably heard the same advice: rebuild everything, adopt a JavaScript framework, expose REST APIs, and brace for a long, complex migration.

But that’s not the only path.

In this session, we challenge the assumption that modern web apps require a dual-stack architecture. Instead, we explore a pragmatic approach that lets you stay entirely in Java—leveraging your existing codebase, your team’s expertise, and years of proven business logic.

You’ll see two powerful approaches in action:

* Webswing – run your existing desktop applications directly in the browser with minimal changes
* webforJ – build modern, web-native UIs using pure Java

Together, they enable a phased modernization strategy: bring your current app to the web today, while gradually evolving toward a modern user experience—without writing JavaScript.

We’ll walk through real-world migration scenarios, highlight trade-offs (no magic here), and share lessons learned from production deployments.

Whether you’re dealing with a 20-year-old legacy system or planning your next greenfield project, this talk will give you practical, low-risk strategies to deliver web applications—without leaving the Java ecosystem.

Presented by Stephan  Wald (BASIS International Ltd.) at JavaOne 2026 (CA, March 2026).

All https://www.youtube.com/playlist?list=PLX8CzqL3ArzUMVSzm-z_-if8BIB55EGl4 talks.

*Resources*
* https://webforj.com/
* http://docs.webforj.com/

Tags: #Java #JavaOne #UI

LRN1463 18 104

Java (Official Oracle)

A conference talk presenting a Java-only strategy for modernizing legacy desktop applications (Swing, Eclipse RCP, Oracle Forms) to run in the browser without adopting JavaScript frameworks like React or Angular. The approach uses two products: WebSwing, which renders existing Java GUI apps in a browser via a server-side canvas, and Web4J, a component-based Java UI framework for building modern responsive web UIs. The talk argues against full rewrites and the 'multi-stack tax' of maintaining separate Java and JavaScript teams, advocating instead for an incremental migration path: immediately web-enable with WebSwing, then gradually replace screens with Web4J while reusing existing business logic. A real-world case study from Dutch ERP vendor Prodin shows six Java developers shipping first modules in four months with zero lines of JavaScript.

Modernizing Java UIs Without JavaScript: Escape the Multi-Stack Trap