Releases: vaadin/multiplatform-runtime
Vaadin Multiplatform Runtime 5.0.5
Vaadin Multiplatform Runtime 5.0.5
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 20+ (Flow) applications.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Fixes since the 5.0.4 Release
Vaadin Multiplatform Runtime 5.0.4
Vaadin Multiplatform Runtime 5.0.4
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 20+ (Flow) applications.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Fixes since the 5.0.3 Release
- Unlock after session access.
- Report a possible reason of FW UI absence in RPC handling (Issue: #80).
- LegacyComponent should handle enabled change (Issue: #82).
A LegacyComponent should set the framework component to the correct enabled state if the wrapper state changes due to a parent component being disabled/enabled. - Hide tooltip on mouse out event (Issue: #89).
Adds a tooltip mouse move handler to the root panel to ensure a tooltip is being hidden properly. - Message processing to be after initial UIDL (Issue: #86)
This delays the purging of the pending response queue until the initial UIDL is being processed and makes sure everything from the initial UIDL is processed by using a deferred command to purge the queue. - Allow MprNavigator deal with SingleComponentContainer (Issue: #36).
- Store navigator created using a component in a field (Issue: #39).
- Set up response handler if wrapper element is hidden (Issue: #91).
- Clean up legacy UI and content on session destroy and UI detach.
Adds session destroy listener to clean up legacy session and detach listener to remove legacy UI from session to avoid potential memory leaks: legacy UI holds reference to Flow UI. Removes MprUIContent from session when detached. MprUIContent holds Flow UI reference, thus possible memory leak preventing Flow UI's getting GC'd.
Vaadin Multiplatform Runtime 5.0.3
Vaadin Multiplatform Runtime 5.0.3
Built on top of latest Flow version 7.0.2 (Vaadin 20). No other user facing changes.
Supports Vaadin 17+. But please note that Vaadin 17+18 are end of life, like soon is version 19. Upgrade to Vaadin 20 instead.
Vaadin Multiplatform Runtime 5.0.2
Vaadin Multiplatform Runtime 5.0.2
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 17+ (Flow) application.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
No user facing changes since 5.0.1
Supported Technologies
Applications running MPR are Flow applications, and they support the same set of browsers, servers and Java versions as pure Flow applications. See the Vaadin platform release notes for details.
MPR for Vaadin 7 supports Vaadin 7.7.14 or newer, and MPR for Vaadin 8 supports Vaadin 8.6 or newer.
Known Limitations
- MPR has some limitations when running with legacy Vaadin frameworks. Make sure you are aware of those before starting porting your project with MPR.
Vaadin Multiplatform Runtime 5.0.1
Vaadin Multiplatform Runtime 5.0.1
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 14.5 (Flow) application.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Fixes Since the 5.0.0 Release
Breaking change
- MPR Annotations now read from the AppShellConfigurator class (Fixes #83 by unifying with Vaadin annotation usage)
MPR annotations are not read from the AppShellConfigurator class and not the top most layout
Supported Technologies
Applications running MPR are Flow applications, and they support the same set of browsers, servers and Java versions as pure Flow applications. See the Vaadin platform release notes for details.
MPR for Vaadin 7 supports Vaadin 7.7.14 or newer, and MPR for Vaadin 8 supports Vaadin 8.6 or newer.
Known Limitations
- MPR has some limitations when running with legacy Vaadin frameworks. Make sure you are aware of those before starting porting your project with MPR.
MPR 5.0.0 Release
Vaadin Multiplatform Runtime 5.0.0
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 17+ (Flow) application.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
No user facing changes since 5.0.0.rc1
Supported Technologies
Applications running MPR are Flow applications, and they support the same set of browsers, servers and Java versions as pure Flow applications. See the Vaadin platform release notes for details.
MPR for Vaadin 7 supports Vaadin 7.7.14 or newer, and MPR for Vaadin 8 supports Vaadin 8.6 or newer.
Known Limitations
- MPR has some limitations when running with legacy Vaadin frameworks. Make sure you are aware of those before starting porting your project with MPR.
MPR 5.0.0.rc1 Release
Vaadin Multiplatform Runtime 5.0.0.rc1
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 17+ (Flow) application.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
No user facing changes since 5.0.0.beta1
Supported Technologies
Applications running MPR are Flow applications, and they support the same set of browsers, servers and Java versions as pure Flow applications. See the Vaadin platform release notes for details.
MPR for Vaadin 7 supports Vaadin 7.7.14 or newer, and MPR for Vaadin 8 supports Vaadin 8.6 or newer.
Known Limitations
- MPR has some limitations when running with legacy Vaadin frameworks. Make sure you are aware of those before starting porting your project with MPR.
MPR 5.0.0.beta1 Release
Vaadin Multiplatform Runtime 5.0.0.beta1
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 19+ (Flow) application.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes Since 4.0.1
- Updated license to version CVDL 4.0
- Use V19 snapshot with Flow 6
- Update Vaadin 8 to version 8.12.0
MPR for Vaadin 7 supports Vaadin 7.7.14 or newer, and MPR for Vaadin 8 supports Vaadin 8.11 or newer.
MPR 4.0.1 Release
Vaadin Multiplatform Runtime 4.0.1
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 17+ (Flow) application.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Features and Fixes Since 4.0.0
MPR for Vaadin 7 supports Vaadin 7.7.14 or newer, and MPR for Vaadin 8 supports Vaadin 8.11 or newer.
Vaadin Multiplatform Runtime 2.2.5
Vaadin Multiplatform Runtime 2.2.5
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 14 (Flow) applications.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Fixes since the 2.2.4 Release
- Catch IllegalStateException on detach (Issue: #93)
Catches IllegalStateException thrown upon attribute removal on the closed session and logs the corresponding message.