Servoy 6.0.11

We are pleased to announce the immediate availability of Servoy 6.0.11 release (releaseNumber 1241).

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.

All the issues addressed:

Client Changes
[chg] SmartClient libs signed with new Servoy certificate
[fix] SVY-5824 Type Ahead’s accept entered values from Fallback Valuelist

Server Changes
[chg] SVY-4315 SQL Server 2012 Warning in log file
[enh] SVY-7618 Add support for database sequences in sql server 2012

I upgraded a client’s 6.0.10 to 6.0.11 but got the j2db blocked by java security.
I checked with the Codesigner8 and found all the jar files expired 2015 Feb 13.
I also loaded the complete installation jar file into a new folder but still the same result.

Besides signing with self signing is there another build available (that does not have the four missing jar files referenced in a Servoy 7.4.3 release recently).

i made quickly a update zip file: http://download.servoy.com/downloads/6x … oy6011.zip

where you can download the application server contents (so extract application_server\ dir) which is has all the jars that are correctly signed.

Thanks Johan.
I extracted the files from the zip and copied them over the existing files. I noted that not all the jar files are in the zip file.
However when I install in my client machine and try to run the solution in smart client I get an error message that not all jars are signed with the same certificate.
Not sure what that means.

Anyway, I will abandon 6.0.11 and attempt to move the solution to Servoy 7.4.3.

thats weird that should really be all of them, which files are missing?

I will also have a look and update the zip file

i have updated the zip (should be a bit bigger now 38MB)

Thanks for checking and fixing the zip file.
Yes the files are all updated now with the latest certificates. The client application now works again.