Modernizing Java UIs Without JavaScript: Escape the Multi-Stack Trap
summary
Shows a concrete path to move Swing/JavaFX/Eclipse RCP apps to the browser using WebSwing (server-side AWT capture, canvas rendering) and then modernize UI with webforj (Java-only component framework, Spring Boot integration). Demonstrates overnight web-enabling, a hybrid connector that embeds legacy screens, shared classloader options, and debugging via server-side breakpoints. Reports a customer shipping first modules in four months with six Java devs and zero JavaScript, reusing existing logic from codebases of 500k–2M lines.
AI-written summary · about
chapters (8)
- 0:00The challenges of legacy apps
- 2:49Modernizing with a Java stack
- 11:16Understanding Webswing
- 15:11Stepwise modernization strategy
- 20:31Developing with webforJ
- 25:30Case study and real-world results
- 30:07Strategic implementation plan
- 36:49Closing and Q&A
related talks
52mHistory of Java UI Development: Live. Die. Repeat.
49mThree Different Methods to Build Web UIs in Java
47mRich Client Java: Still Going Strong
46mJavaFX in the Web
27m"Full-stack from the back: Building for the web with Java"
30mJava-Centric Web Development: The Advantages of a Single Stack Approach
52mYou may not need JavaScript
41mFull-stack development is dead, long live full-stack development!