Servoy 8.3.2

Classic Servoy
1

We are pleased to announce the availability of Servoy 8.3.2 (releasenumber 3207)

This version is available through our download site

The update site is: http://download.servoy.com/developer/8xx_updates/

There are, compared to the 8.3.2rc a few fixes:

fixes

fixes done in 8.3.2rc:
8.3.2RC fixes and feature

see for the changes in 8.3:

Whats new

Bootstrapper did get a standalone version (starting without webstart)

Also check the new feature out for parsing/validating javascript code, we like to have that tested and looked at so we can enable that by default for 8.4

2

Hi, we are testing an application under 8.3.2 and everything seems fine running Servoy server.

However, I have tried setting up Tomcat to run Servoy 8.3.2 and the deploy fails because the repository fails to update. It fails after 10 tables, very much like described here on the forum a few years ago. I saw a bug [SVY-10742] had been fixed in Servoy 8.1.x.

I’m on PostgreSQL 9.6.2, Java build 1.8.0_181-b13, PostgreSQL driver postgresql-42.2.5.jar.
I have even tried making a repository on another computer under PostgreSQL 9.3 and moving it across to see if I could avoid the repository upgrade.

I may be doing something wrong, any suggestions? Or others who have come across the same problem?

3

Hi, I’m testing the new parsing/validation on our codebase

Without the feature, I’ve had a few instances, where the parsing failed (because of the max 3 level deep parsing of code), which works now when @return and @constructor are properly set.

But I’m still having problems with prototypes. Methods defined on prototype are accessible only in the same scope:

test.js

var init = function() {
	Base.prototype.prototypeMethod = function() {}
}();

/**
 * @public 
 * @constructor 
 */
function Base() {
	this.methodName = function() {};
}

/**
 * @public 
 * @return {Base}
 */
function getBase() {
	return new Base();
}

function test() {
	var base = getBase();
	base.methodName(); //works
	base.prototypeMethod(); //works
}

other_scope.js

function test() {
	var base = scopes.test.getBase();
	base.methodName(); //works
	base.prototypeMethod(); //generates warning
}

Is there another way to do this?

4

Hi Jozef,

Yes, I asked the same thing in the 8.3.1 RC thread: viewtopic.php?f=1&t=22228#p118902 (see bottom few posts).
I think that solves your issue.

5

There appears to be an issue with % formatted fields in Smart Client. Format a field as ##.00%.
Type a percentage, let’s say 14%. The database stores it as 14.01%…

It happens with both PostgreSQL 9.6.6 and SQL Server 2012.

I have opened a case, SVY-12773.

6

swingman:
Hi, we are testing an application under 8.3.2 and everything seems fine running Servoy server.

However, I have tried setting up Tomcat to run Servoy 8.3.2 and the deploy fails because the repository fails to update. It fails after 10 tables, very much like described here on the forum a few years ago. I saw a bug [SVY-10742] had been fixed in Servoy 8.1.x.

I’m on PostgreSQL 9.6.2, Java build 1.8.0_181-b13, PostgreSQL driver postgresql-42.2.5.jar.
I have even tried making a repository on another computer under PostgreSQL 9.3 and moving it across to see if I could avoid the repository upgrade.

I may be doing something wrong, any suggestions? Or others who have come across the same problem?

but that exact problem is a driver problem, are you sure you are using a latest postgresql driver? (in the WAR or maybe configured somewhere else)

on another system this works fine?

7

This is old-style servoy server, on WAR-deployment. The same thing happens with SQL Server as database. The problem goes away the reverting to 8.2.x.

8

swingman:
This is old-style servoy server, on WAR-deployment. The same thing happens with SQL Server as database. The problem goes away the reverting to 8.2.x.

which problem are we now talking about here?
formatting or the repo upgrade/create?

9

Sorry1

Sorry, my fault for not reading your post properly. I was talking about the percentage formatting and you were asking about the repository upgrade.

I somehow got it working. I tried a few things including copying repositories from other versions of PostgreSQL and in the end it worked, so it may be specific to the PostgreSQL version I’m on.