Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
See also Release Notes on Github
|Download • Git
|Forums • Blog • Twitter • G+
Eclipse Scout becomes a Java Web Framework
With Release 6.0 the frontend part of the Scout framework becomes a powerful Java web framework.
A new HTML5 Renderer
Scout comes with a completley new HTML5 rendering component.
- Full styling/theming with CSS3/Less
- Add project specific custom widgets
The HTML5 renderer is highly optimized for Scout
- Minimize download size for initial download
- Avoid unnecessary server rountrips
Frontend development in Java
The goals of the Scout framework remain unchanged:
- Boost developer productivity
- Long term strategy (enterprise apps often live > 10 years)
As in previous releases the Scout developer implements against the Scout model classes. Developing frontends and UI logic in Java remains independent of the new HTML5 renderer technology.
Plain Java/Maven Projects
Scout applications are now plain Java/Maven projects.
The move to plain Java with the Neon release brings the following benefits:
- "Maven by the books": Simplified build setups for Scout projects
- Simpler integration of widely used Java libraries and frameworks
Upgrade of existing Projects
Great care has been taken to reduce the API breakage of the Scout Neon release to a minimum. As a result, only moderate efforts are required to upgrade an existing Scout project to the new Scout release.
The migration process has been verified with several productive Scout applications in the last months. This migration guide helps projects to migrate to Scout 6.0. This document is not static in nature but will be updated according to new feedback from the community and projects that migrate to the new Scout release.