Features added in this build
JIRA Issue No. | Details |
---|---|
NXPSR-11161 | The "use-http-request-header-for-session-id" value in the jnlp should override the value from Nexaweb-client.xml |
NXPSR-11184 | use-http-request-header-for-session-id set to true does not allow multiple sessions |
NXPSR-11187 | [JWS] The window title by JWS is not supporting the multi-byte character. |
NXPSR-11189 | [JWS] Cookie encoding |
NXPSR-11188 | [JWS] JNLP does not work correctly in implementation according to a template and a guide. |
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 .
Defects resolved
Issue No. | Details |
---|---|
NXPSR-11177 | The window title is not shown when we run it as the java web start |
NXPSR-11183 | [Compatibility] When timeout of Nexaweb Session occurs, NullPointerException occurs by the server side. |
NXPSR-11185 | When Platform 4.5.62GA is used, the error message of ProtocolQueue is printed to a server log. |