4.5.69(December 2021)

Defects

The following defects are resolved in this build.

NXPSR-11225	When a combo editor is closed by a double click in <gridTable/>, an onStateChange event does not fire.
NXPSR-11229	Nexaweb Launcher: OpenBrowser function issue - when the load balancer or system needs cookies other than JSESSIONID
NXPSR-11232	When using load balancer, appbase address is not always the same.
NXPSR-11236	Nexaweb Launcher: OpenBrowser function doesn't work in the weblogic server
NXPSR-11240	Provide functionality to dynamically change the window title of the Standalone Client

NXPSR-11225 When a combo editor is closed by a double click in <gridTable/>, an onStateChange event does not fire.

A configuration has been added to nexaweb-client.xml. The value should be set to true.

    <!-- This parameter provides backwards compatibility support for customers which require		-->
	<!-- the bug where a state change is reported on the client when the mouse is double clicked	-->
	<!-- on a row or cell.  When set to true the client will report an onStateChangeEvent			-->
	<!-- when the mouse is double clicked on a row or cell,even when the state has not changed.		-->
	<ensure-pre-bugfix-gridtable-statechange-behavior-ondoubleclick>true</ensure-pre-bugfix-gridtable-statechange-behavior-ondoubleclick>

NXPSR-11229 Nexaweb Launcher: OpenBrowser function issue - when the load balancer or system needs cookies other than JSESSIONID

OpenBrowser function: When the application runs on non-applet env, we use the URL rewriting to transfer jesssionId from the launcher to browser.

We only pass jsessionid which worked for some environment. But when we run on load balancer and weblogic, the load balancer stores the serverip in cookie and weblogic stores the auth flag in cookie.

For eg.
BIGipServersample=1879642142.64211.0000;
sample-ServerSessionId=nx-2767-782;
JSESSIONID=02qiJmG9HIh_x_a-EEG2a2qybMUj9DHKeyrnQ4I2TYfMzJkcvTbR!225964139;
_WL_AUTHCOOKIE_JSESSIONID=.shKE7xgDHI-IIc5qLCR

So we need to transfer all cookies via URL not just jsessionid. When we call openBrowser function, we compress all cookies and send as a parameter to server.

NXPSR-11232 When using load balancer, appbase address is not always the same.

When you run runNexaweb in the browser to get the runNexaweb.nexaweb, sometimes the appbase is different.
We get the appbase from request. When using load balancer, the request is sent from the land balance( maybe more then one machine) rather than from client directly .

We made changes in how we set appbase. The priory is #1>#2>#3.

Get host name from <host-name><<http://localhost:8080</host-name>> which is defined in the nexaweb-client.xml.
Get host name from header.
Get from URL.

NXPSR-11236 Nexaweb Launcher: OpenBrowser function doesn't work in the weblogic server

When we call openBrowser in launcher, we send jessionid via parameters.
When you run application in weblogic, it needs two cookies - jessionid and_WL_AUTHCOOKIE_JSESSIONID for authentication. Since we only send jessionId, so weblogic returns login page for re-authentication. So we removed the jessionId and let the server will handle all cookies.

NXPSR-11240 Provide functionality to dynamically change the window title of the Standalone Client

A method setWindowTitle has been added to DisplayService to set the window title. com.nexaweb.client.displayservice.DisplayService#setWindowTitle(String title)