We are pleased to announce the immediate availability of Servoy 6.1.6 (releaseNumber 1439).
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 open Check for updates via help menu.
Thanks to the external testers for helping out to get a solid release!
All the issues addressed:
Client Changes
[fix] SVY-4521 Unexpected release when open the Smart Client
[fix] SVY-4444 listbox shown as combobox
[fix] SVY-4443 Valuelist showing realvalue instead of displayvalue sometimes.
[fix] SVY-4423 FoundsetUpdater fails when a foundset contains newly created records.
[fix] SVY-4349 databaseManager.getEditedRecords(foundset) inconsistent returns
[fix] SVY-4332 foundset.getQuery() doesn’t always return a query object reflecting the current state of the foundset.
[fix] SVY-4329 IllegalArgumentException in TimSort.mergeHi() when opening a form.
[fix] SVY-4317 NPE inside JSFoundSetUpdater.js_performUpdate().
[fix] SVY-4311 FoundsetUpdater only updating from selectedIndex forward, and not entire foundset
[fix] SVY-4288 Column converters aren’t called to translate values when using FoundsetUpdater.
[fix] SVY-4749 Java update 7.25 breaks some bean loading
[fix] SVY-4729 selectOnEnter and TEXT_FIELD issue
[fix] SVY-4609 Can’t see field value in calc
[fix] SVY-4423 FoundsetUpdater fails when a foundset contains newly created records.
Web Client Changes
[enh] SVY-3728 give wrapper div around
Problem: Can’t export WAR file after upgrading from 6.1.3 to 6.1.6. Clicking on ‘Next’ to select the destination you want the WAR file placed in just gives you a blank page. See pictures
[attachment=1]ExportWAR1.png[/attachment]
[attachment=0]ExportWAR2.png[/attachment]
I just tested it with both an upgraded Developer and with a clean install. In both instances I get the proper dialog where I can select a destination file.
So I can’t reproduce what you are seeing.
Perhaps you should try a clean install.
Interesting. I later did an upgrade of a copy I’d made just to 6.1.5 and that was fine. But when I upgraded that to 6.1.6 that too failed in exactly the same way. I guess a clean install is the way to go.
I just upgraded Server from 6.1.2 to 6.1.6, and now get an “Invalid Foundset” error on Solution opening
My Opener script uses Controller.Find to find a non-existent value ( record -1 ), so as to start with an empty found set. It used to work. Now it shows record 0
gdurniak:
My Opener script uses Controller.Find to find a non-existent value ( record -1 ), so as to start with an empty found set.
Use databaseManager.setCreateEmptyFormFoundsets() in order to start all your foundsets as empty foundsets. (which in my opinion is always good, because how should the developer know what the user is looking for?)
Otherwise you can just call a foundset.clear() for this specific foundset.
Do you have sample code to show this difference? Or a small solution with that sample code… I’d like to see what changed, even if one would normally do that with .clear().
I went back to Server 6.1.2, so no longer a problem ( and no way to test further )
Note: servoy_updater.bat reported that 2 zip files were not found. The upgrade did finish, but not sure it is complete. I then tried a clean install of 6.1.6, and server would not start ( insufficient heap ). This is way too hard
I did try a small sample with such a find/search. But for me it worked fine.
Can you file a case that contains the exact message reported by servoy_updater.bat (about the missing zip files) and a sample solution that shows changed behavior between 6.1.2 and 6.1.6?
Then about the “Insufficient heap” - if you can’t fix that by tuning (lower/higher) the -Xmx setting from servoy_server.bat please file another case and specify the exact/complete error message & Java version . Your system should have at least that amount of memory available (even if it’s swap memory). That setting hasn’t changed between the two versions so I don’t see why it would happen.