A 100% Java framework for building reactive client-side web apps with POJO traffic, declarative views, and jUnit GUI testing.
VertxUI is a Java framework for building reactive client-side web applications entirely in Java. It allows developers to write frontend code using Java 8 features like lambdas and streams, with strong-typed POJOs shared between client and server. The framework includes a virtual DOM for efficient UI updates, automatic browser reloading, and integrated jUnit testing for GUI components.
Java developers building single-page applications or microservices who prefer writing frontend logic in Java rather than JavaScript or TypeScript. It's ideal for teams already using Vert.X or looking for a strong-typed, tooling-friendly web framework.
VertxUI offers a pure Java solution for modern web development, eliminating the need for JavaScript/TypeScript while providing reactive UI patterns, seamless client-server communication, and professional Java tooling integration. Its declarative view-on-model approach and jUnit testing support streamline development and testing workflows.
Pure 100% java reactive-style client-side webpages with POJO traffic, jUnit GUI testing, declarative view-on-model, automatic browser reloading and more.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables writing entire client-side logic in Java 8, compiled to ES5 JavaScript, eliminating the need for separate JavaScript/TypeScript tooling, as highlighted in the README's emphasis on '100% java'.
Uses the same Java POJOs for all client-server traffic (ajax, websockets, SockJS), ensuring type safety and reducing serialization errors, a core feature described in the POJO examples.
Allows GUI testing against a virtual DOM without a browser, making frontend testing fast and seamless with Java's standard testing framework, as demonstrated in the jUnit section.
Includes FigWheely for automatic browser reloading when code or resources change, preserving state and speeding up development, explicitly mentioned as a key feature.
Does not provide a GUI toolkit; relies on external CSS libraries like Bootstrap, requiring manual CSS work and integration, as admitted in the README's 'not a new GUI toolkit' disclaimer.
Uses GWT for Java-to-JavaScript compilation, which can be slower and more resource-intensive compared to modern JavaScript bundlers, as noted in the 'More' section discussing compilation trade-offs.
As a Java-based frontend solution, it has a smaller community and fewer third-party libraries than mainstream JavaScript frameworks, limiting support and integration options.