DashboardView and GridStackView rendered the same three charts from the
same hardcoded data, so every chart factory method existed twice. The
dashboard is now the GridStackLayout variant at @Route(""):
- GridStackView deleted, its grid/toolbar/chart factories moved into
DashboardView, which keeps the point-click notifications the old
dashboard had.
- Charts size to their widget (100%/100%) instead of a fixed 400px.
- MainLayout has one dashboard entry; nav.gridstack/page.gridstack keys
dropped from all three bundles.
- Storage key is "dashboard" (was "gridstack-demo"), so a saved layout
from the old route is not reused.
- GridStackViewTest renamed to DashboardViewTest, plus a test asserting
the three charts render.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0124BiJikbhbiEsNfJxdWM69
My Application
A Spring Boot + Vaadin project. Build your UI in pure Java — no HTML, no JavaScript.
New to Vaadin? The 5-minute Quickstart walks you from here to your first running app, a live code change, and an AI-assisted edit with Copilot.
Fastest start — no plugin needed
From the project folder:
./mvnw spring-boot:run # Windows: mvnw.cmd spring-boot:run
Then open http://localhost:8080.
The first start takes ~30 seconds while Maven downloads dependencies.
Port 8080 already in use? Stop the other process, or set
server.port=8081insrc/main/resources/application.propertiesand open that port instead.To stop the app: press
Ctrl+Cin the terminal (or the red Stop button if you launched from your IDE).
Optional upgrade — instant hotswap
Running with spring-boot:run works, but Java code changes need a server restart. For live reload — edit Java, see it in the browser without restarting — install the Vaadin plugin and start the app through it:
- IntelliJ IDEA: install Vaadin from the JetBrains Marketplace → Debug using Hotswap Agent (dropdown next to Run). Just installed it? Let IntelliJ finish indexing, or restart it, if the menu item isn't there yet.
- VS Code: install the Vaadin extension → Vaadin: Debug using Hotswap Agent from the command palette.
- Eclipse: install the Vaadin plugin → right-click the project → Run As → Vaadin Application.
This is what makes the edit-and-see-it loop feel instant — and it's required for the AI edits in Vaadin Copilot.
Ask your AI assistant about Vaadin (optional)
If you use Claude Code, Cursor, or another AI coding assistant, connect it to the Vaadin MCP server so it answers against real Vaadin docs and the exact API of your installed version — instead of guessing from outdated training data.
# One-time setup — see https://vaadin.com/docs/latest/building-apps/mcp
A .mcp.json is included (commented out by default). Uncomment it, or run the setup command above, to activate.
Build for production
./mvnw package
java -jar target/*.jar
Learn more
- Vaadin Quickstart — the 5-minute getting-started path
- Components — 50+ UI components, all callable from Java
- Vaadin Copilot — visual + AI editing in the browser
- Full documentation