Servoy Forum

We are pleased to announce the availability of Servoy 2023.12 release candidate 1 (release number 3920)

See whats new for the global changes and the case list

For Windows the installer: exe
and for the MacOSX_86_64 we have an native dmg
and for the MacOSX_Aarch64 (M1) we have an native m1 dmg
for linux it is tar.gz

For windows we also still have just the zip

An installation (coming from the normal installer or from a platform specific archive) is shipping with a Java VM (Java 21.0.1)
So for the platform specific archives you don't need to install or have java on your system.

This release is build on Eclipse 2023.09 (4.29)


The developer can be updated by the https://download.servoy.com/developer/l ... ecandidate update site URL.
This is in our "latest" release stream (03,06,09,12) if you want to stick the LTS release then disable that releasecandidate url and stick to the URLs with "lts" in the name
If you update to this release you have to do a new install of 2023.03.4_LTS to go back to an the LTS release branch

it could be that the update fails if you come from a much older release (like 2021.06 -> 2022.12) that you can get errors like:

Code: Select all

An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,com.servoy.eclipse.core,2022.12.0.3840_rc.
Error reading signed content:C:\Users\jcomp\AppData\Local\Temp\signatureFile11879913363204093521.jar


Or that you can't install it completely (you can't pass the update dialog, because it says incompatibilities found)
This is because from 2022.12 on we depend on java 17. (so the developer that you run should already be on java 17)

You can fix both issues to first jump to an older version like a 2022.03.x release, you can do this by making this URL:

https://download.servoy.com/developer/latest/3743/

first the only update site in the preferences -> install/update -> sites, so add that URL and make sure that is the only one.

Then it updates to that release first, then you can enable the release candidate URL again.

There are also updates of various webpackages, bootstrap-components, servoy-extra-components, bootstrap-extra-components and ng-grid to the 2023.12 releases
The NGGrid 2023.12 is mandatory to upgrade to the 09 release won't run fully correct on a Servoy 2023.12 release.

Hi Johan,

In the release notes it mentions support for FontAwesome Pro and recommends forking or cloning a blueprint project but if you click the link, the issue it refers to (SVY-18694) is not public so cannot be viewed.

Thanks
Steve

i changed the link to the actual project (instead of the case)

it is this: https://github.com/Servoy/fontawesomepro

Can you expand on what this means in the Whats New page...

As a heads up, The majore release after this one so 2024.03 will be te last release that will include SmartClient,WebClient and the NGClient (angularjs).

sbutler wrote:Can you expand on what this means in the Whats New page...

As a heads up, The majore release after this one so 2024.03 will be te last release that will include SmartClient,WebClient and the NGClient (angularjs).

Johan talked about this in the Q&A session at ServoyCamp 7.
He talks about it in this video from this timestamp.

Hope this helps

yes so i explained it also in that video.

So also then in words here a bit more,

2023.12 and 2024.03 nothing will really happen for this topic.

But 2024.06 will very likely not have support anymore for the SmartClient, WebClient and the NGClient1 (so the angularjs version)

So the only clients we will support by then are TiNGClient (angular based one), Headless (batch, rest), and of course we still have wrappers like NGDesktop but that will just be wrappers around TiNGClient.

This way we can kill a lot of entry points that we need to expose and clean up a lot of code and remove a lot of older 3rd party libs that are not supported anymore (or we can't move to a newer version because of dependencies)

Of course 2024.03 is an LTS release so that will have support for 2 years so until 2026.03, and we will bring out patches and bugfixes in those years on top of the 2024.3.x_LTS

Besides clean up a lot of code and removing at lot of older libs, we can then (not directly but in the coming year) also move to the new jakarta api, so then we run on tomcat 10 (natively) and not on tomcat 9 anymore (same holds for other containers that you want to use). if you look here: https://tomcat.apache.org/whichversion.html then it is the 3rd line and up (so servlet spec 5 and higher)

We have upgraded from 2023.3 to 2023.12_rc1 and are having an issue with database stored procedures. I can see from 2023.9 release notes that the DB driver has been updated and specifically affects this area.

We were using the stored procedures namespace to retrieve the next value from a Postgres sequence using the following code:

Code: Select all

var seqNo = datasources.sp.tmle.nextval(sequnce_name)

How can this now be done in 2023.12 ?

Thanks
Steve

Hi Steve,

can't you use a scope function doing something like this:

Code: Select all

function getNextSequence(_sSeqName) {
   var _ds = databaseManager.getDataSetByQuery('tmle', "select nextval(?)", [_sSeqName], -1);
   
   return _ds.getValue(1,1);
}

[EDIT] but to be fully complete: probably your stored procedure was a function instead of a real stored procedure? According to Johan real stored procedures should still work.

That’s great thanks Marc. From what I’ve read though a real stored procedure doesn’t return values.

the problem is its more a driver update, that suddenly only really returns SP and not functions anymore.. And because of the query we need to do to call (you call SP differently) we also needed to change that because now sp from postgresql are really sp's and they where always just functions (because back then you couldn't make sp)

But you should be able to return values i think, you have in and output params (and in/out)
https://dba.stackexchange.com/questions ... postgresql

The CTRL + H search functionality seems to be not working anymore in this version.

Seems to work fine for me, does the menu itself still reports that that that is the accelerator?

jcompagner wrote:Seems to work fine for me, does the menu itself still reports that that that is the accelerator?

There was no issue indeed. I wasn't using the search functionality properly.
Thx for looking into it!