After we moved to Servoy 8 (8.1.3) and Tomcat (9.0.0.M20) we do not get the desktop icon any more. Instead we get as desktop icon the Java coffee cup.
As small as the problem seems, it is sort of a blocker to deploy, as clients do not recognise our applications any more and are contacting the 1st level support for help. Which generates a lot of work. On the other hand, we should asap deploy the new application version based on the aforementioned environment.
It is the same behaviour on Windows and macOS. Interestingly, the same icon is used as window icon (top left in application window) and is displayed as expected (on Windows).
Thanks a lot for your feedback. We also use Profile(s), but unfortunately it doesn’t work even with them. I tried quite a view format and sizes for the image, but never had any success. I have also set up PNG-Format as standard (as you), but still no luck. Strange.
This is the profile:
servoy.branding.windowtitle=SkyServer
servoy.branding.windowicon=/lib/images/hades_desktop_icon.png
servoy.branding.webstart.splash=/lib/images/7r-logo.png
servoy.branding.webstart.vendor=7r AG
servoy.branding.webstart.shortcuttooltip=Schulverwaltungs- und Informationssystem
servoy.branding.webstart.shortcuttitle=Hades
servoy.branding.loadingbackground=/lib/images/hades_background.png
servoy.branding.webstart.loadinglogo=/lib/images/hades_desktop_icon.png
servoy.branding.loadingimage=/lib/images/hades_splash_screen.png
I also remember this kind of problem on a windows client the problem solved by itself upgrading java
I think it was something like java jre 1.7.xxx to 1.8.yyy but I had never been sure that it was a version problem or the upgrade process that has refreshed few resources and solved the problem
I made in the past the same expense. Starting with Servoy 8, Tomcat and WAR-Deployment, I did not get it to work any more. It seems that it’s stable in not working
Problem is, I have no more ideas where to look at.
erdione:
I also remember this kind of problem on a windows client the problem solved by itself upgrading java
I think it was something like java jre 1.7.xxx to 1.8.yyy but I had never been sure that it was a version problem or the upgrade process that has refreshed few resources and solved the problem