Servoy 2020.09 release candidate2

[jcompagner]

We are pleased to announce the availability of Servoy 2020.09 release candidate 2 (release number 3601)

For Windows the installer: exe
and for the MacOSX we have an native 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 with a Java VM (Java 14.0.1)

So for the platform specific archives you don't need to install or java have on your system.

The developer can be updated by the http://download.servoy.com/developer/la ... ecandidate update site url.
This is in our "latest" release stream (03,06,09,12) if you want to stick the 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 2020.03.1_lts to go back to an the LTS release branch


If you do update from a bit older version (then 09) then it could be that there is a left over driver in the drivers dir that has 0 bytes. Make sure you delete that one, and if you make war exports from this make sure you don't include this 0 byte driver jar. That will result in errors when deploying.

See whats new for the global changes

See the issues list for a complete overview of all the cases (with an updated list of rc2 cases)

We will release also new component and service packages shortly.

[steve1376656734]

Since downloading 2020.09 RC 2 (may have also happened with RC1 but did not test with that) I am getting the following error whenever I try to use the PDF viewer with a dataprovider:

PDF.js v2.3.200 (build: 4ae3f9fc)
Message: Unexpected server response (500) while retrieving PDF "http://localhost:8183/resources/dynamic/29438F81-5B3F-457F-A052-7DB4516CF9F3?clientnr".

Could this be related to this comment in the release notes:
"media urls generated in servoy for dynamic data (FilePlugin.open/writeFile and the serverside scription servoyapi.getMediaUrl) are now only accessible by the same session.
So those urls can't be shared and send to other users to download stuff."

The same code in 2020.06.01 works fine.

[steve1376656734]

Also, if I try pasting that URL directly into the browser I get:

HTTP Status 500 – Internal Server Error
Type Exception Report

Message For input string: ""

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

java.lang.NumberFormatException: For input string: ""
java.base/java.lang.NumberFormatException.forInputString(Unknown Source)
java.base/java.lang.Integer.parseInt(Unknown Source)
java.base/java.lang.Integer.parseInt(Unknown Source)
com.servoy.j2db.server.ngclient.MediaResourcesServlet.doGet(MediaResourcesServlet.java:228)
javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
com.servoy.eclipse.designer.rfb.startup.EditorContentFilter.doFilter(EditorContentFilter.java:197)
com.servoy.eclipse.ngclient.startup.resourceprovider.ResourceProvider.doFilter(ResourceProvider.java:339)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
org.sablo.filter.SeparateSessionFilter.doFilter(SeparateSessionFilter.java:80)
Note The full stack trace of the root cause is available in the server logs.

Apache Tomcat/8.5.57

[jcompagner]

"http://localhost:8183/resources/dynamic/29438F81-5B3F-457F-A052-7DB4516CF9F3?clientnr".

Could this be related to this comment in the release notes:
"media urls generated in servoy for dynamic data (FilePlugin.open/writeFile and the serverside scription servoyapi.getMediaUrl) are now only accessible by the same session.
So those urls can't be shared and send to other users to download stuff."

yes it is related to that, you url is not correct... it only has clientnr as a key but not the value (=xxxx)
so the question is why that is. How is that url exactly generated and used?

[steve1376656734]

All we do is set the data provider to a byte array. We do not generate the URL at all - that is done internally by the PDF Viewer component. I have checked the PDF Viewer repo and it looks like Paolo pushed a change last night that may be related to this - it would be good if we could get that package updated so we can pull it through the package manager?

Thanks

[rvanveen]

All we do is set the data provider to a byte array. We do not generate the URL at all - that is done internally by the PDF Viewer component. I have checked the PDF Viewer repo and it looks like Paolo pushed a change last night that may be related to this - it would be good if we could get that package updated so we can pull it through the package manager?

Thanks

Just made a new release for svyPDF (version 1.3.1) what contains a fix for this issue.

[steve1376656734]

Tested and works fine - thanks for the quick response.