To see what's new, what's changed and known issues with each version of Nexaweb products.
Click here for Nexaweb's MR schedule
Overview
One of the goals of this GA release...
Defects resolved
| JIRA Issue No. | Details |
|---|---|
| NXPSR-11151 | [JWS] Migrating environment from Applet to JWS |
| NXPSR-11152 | [Java9] Fixed an issue where an exception occurred when Nexaweb Applet was started on Java9 |
NXPSR-11153 | [JWS] Added a feature where the HTTP session of the browser is correctly inherited when the Nexaweb application is started using Java Web Start (JWS) |
| NXPSR-11154 | [JWS] Added a feature where the cookie of the browser is now correctly inherited when the Nexaweb application is started using Java Web Start (JWS) |
| NXPSR-11159 | [JWS] Support the dynamic addition of a JAR archive to a dynamic JNLP file |
| NXPSR-11160 | [JWS] Added functionality in Nexaweb JWS application to support Pack200 files |
| NXPSR-11166 | [JWS] Added a feature where the browser opened using RequestService#openBrowser() method correctly inherits the session and cookie information of the Standalone Client |
NXPSR-11151 [JWS] Migrating environment from Applet to JWS
Following Oracle's announcement of deprecating java browser plugin in JDK9, Oracle has recommended the usage of JWS instead of applets. Changes have been made to Nexaweb Platform so that it supports Java Web Start.
Please refer to this how-to article for recommended approach of migrating nexaweb application to Java Web Start (JWS) https://nexaweb.jira.com/wiki/display/DevCenter/Migration+from+Applet+to+Web+Start
NXPSR-11152 [Java9] Fixed an issue where an exception occurred when Nexaweb Applet was started on Java9
This is the exception caused by change of the version-string by JEP 223.
NXPSR-11161
The <use-http-request-header-for-session-id> value in the JNLP does not override the value from nexaweb-client.xml when Nexaweb application is started using Java Web Start (JWS)
Nexaweb Platform Release Notes
Reference Framework Release Notes
RF 2.0 (view)
Backwards Compatibility
For a log of any changes impacting backwards compatibility see the backwards compatibility log (view).
Nexaweb Platform
- Starting with version 4.0 Nexaweb platform is backwards source compatible with 4.x versions.
- When new features are introduced there may be cases where syntax or interface changes - whenever possible a system flag will be introduced that provides backwards compatibility without modification of old code.
- Review release notes for any changes.
Nexaweb Studio
Nexaweb Studio is based on Eclipse and Web Tools - these products change from time to time and these changes impact project structure. Nexaweb will strive to ensure there is always a project migration path for projects.
https://nexaweb.jira.com/wiki/display/Nexaweb/Platform+MR+Build+and+Publish+Processes