Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Features added in this build

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-11167[JWS] Change of a JNLP template
NXPSR-11168[JWS] When JnlpServlet is used, Application server's port is outputted to a jnlp file.
NXPSR-11170An error takes place at the time of uninstallation of Nexaweb Platform.
NXPSR-11172A memory leak may be caused by PushConnectionManagerImpl$LivePushThread.
NXPSR-11173Issues with JSESSIONID in JWS
NXPSR-11174[JWS] The configuration request of the parameter addition function of JSESSIONID by openBrowser()
NXPSR-11177The window title is not shown when we run it as the java web start
NXPSR-11180[JWS] ClientInfo#getUserAgent() returns null.
NXPSR-11181[JWS] When URL without a parameter is opened by openBrowser(), an exception occurs.

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.

...