You may not need JavaScript
summary
Claims that a Java-only frontend can replace an SPA stack and cut complexity; the project migrates ~800 Oracle Forms screens over 2,000 DB tables and ~5,000 stored procedures into a server-side single-page app built with Vaadin Flow and SQL-first access via jOOQ. The team generates UI at runtime from DB configuration, uses Vaadin grids/binders for paging and validation, relies on Atmosphere websockets fallback, and reports the prototype working with faster development and maintainable DB-driven logic.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:46About me
- 1:11Code samples
- 1:27The Project
- 5:59UI Editor
- 7:05UI Generation
- 8:46History
- 11:52UI Models
- 13:11State
- 16:10Vaadin FLOW
- 17:35Vaadin FUSION
- 20:26Vaadin Hello World
- 25:12Routing
- 27:06Grid
- 28:03DataProvider
- 30:51Forms
- 33:04Server Push
- 34:36Testbench
- 37:37Spa, PWA et cetera
- 43:46Metamodel
- 45:47CRUD with jooo
- 49:26Conclusion
related talks
50mYou may not need JavaScript
44mFull-stack web apps, 100% Java
49mKicking JavaScript to the Curb with Vaadin
06mLightning Talk: Vaadin Flow framework in a nutshell
51mAll in on Java: Web Development with EclipseStore & Vaadin
44mJava developer-friendly frontends: Build UIs without the JavaScript hassle
40mModernizing Java UIs Without JavaScript: Escape the Multi-Stack Trap
50mThe State of Server Side Java Webapps
