Servoy 7.4 rc 3

We are pleased to announce the availability of Servoy 7.4 release candidate 3 (releaseNumber 2025).

This version is available through the download option on the Servoy website and auto-update.
Always make a backup of your current Servoy installation (directory and database) before installing/upgrading.

To update a Servoy eclipse add an Eclipse update site:
https://www.servoy.com/developer/70x_up … ecandidate
followed by “Check for updates” via help menu.

Read all about the enhancements and new features at:
https://wiki.servoy.com/display/DOCS/New+in+7.4

The issues addressed, since Servoy 7.4 rc2 release:

Client changes
[fix] SVY-6104 UI Converters Interfere with onDataChange events
[fix] SVY-5976 foundset.deleteAllRecords leaves phantom records in client
[fix] SVY-5847 Smartclient doesn’t react to setting OnSort to none

WebClient changes
[fix] SVY-6115 New HTML objects does not always load in IE10
[fix] SVY-6085 HTML editor does not update dataprovider in Chrome and IE8
[fix] SVY-6057 CSS issues
[fix] SVY-5983 TYPEAHEAD fields in Web Client do not select correct value when used with valuelists based on relation
[fix] SVY-5730 Using Down-arrow don’t works in web-client
[fix] SVY-5657 onAction() and onDataChange() don’t fire in the webclient for a radiobutton

Developer changes
[fix] SVY-5838 Explain why we wrap foundset sql
[fix] SVY-6095 Using the result from utils.dateFormat() results in warning
[fix] SVY-6093 Incorrect warning when using the “var self = this” idiom in custom types
[fix] SVY-5901 valuelist not showing when non-stored calc is used (two relations deep)
[fix] SVY-5837 Allow “with” besides “select” in dataset sql queries

Server changes
[fix] SVY-6064 DBF JDBC driver “error getting data from global method valuelist”
[fix] SVY-5980 Updated DBI information for database views is not imported correctly in Servoy Application Server
[fix] SVY-5900 Error thrown by relation ‘create’ constraint is not triggering onError event
[fix] SVY-5695 branding is changed in Servoy 7.3.1
[fix] SVY-6009 Servoy doesn’t startup after installing 7.4rc
[fix] SVY-5588 Error in foundset > 200 with SQL

Plugins changes
[fix] SVY-5851 Spell checks plugin’s dialogs and wizard always returns english messages
[fix] SVY-6114 from created with plugins.window.showFormPopup does not close when clicking on a HTML field in the background
[fix] SVY-5881 TYPE_AHEAD field closes overlay form created with plugins.window.showFormPopup

The newest versions of the Servoy Jasper plugin - v4.0.1.2b1 deploy the commons-logging bundle. Why doesn’t it use the commons-logging jar deployed with the servoy server (contained in the /lib directory)? It is even the same version (with Servoy 7.4). What happens now when the same jar is deployed twice - once from the server and once from the plugin?
I by the why, added the jasper plugin to Servoy Server 7.4 and removed its commons-logging jar. It did not work - it could not load the classes from commons-logging deployed with the server. I tried the same with Servoy Server 7.3. and there were no issues. Can someone explain to me what has changed?

Servoy is no longer directly depending on commons-logging, only some libs are using it.
Since it gave problems in developer with SQLExplorer we removed commons-logging from the exposed class path in developer.
Note this is only a Servoy developer change.

OK, then does that mean that if we want to use the servoy jasper plugin in the developer we need to deploy the commons-logging jar in the plugins directory but we do not need to do it for the Servoy Server?

correct, the last beta of this plugin does this already

Thanks for the information.

But what happens on the server? Do we need to change the jasper plugin “deployment” package and delete the included commons-logging jar? How does this work with the WAR exports?