Servoy Forum

Hi jan,

I meant to send you the whole unreacted trace via the forum, but the forum does not allow me to send it to you.
The login page is public, right now we are testing a version without the panel, but I can upload one of the versions that fail so you can see the errors. I just need to give you the URL.

Christian

We experienced this exact issue yesterday when deploying our first 2022.06 build as a WAR file. The solution was to set servoy.ngclient.enableWebResourceOptimizer to False on the Servoy Admin page. When this is True it tries to optimise the Javascript files from the components and this is what was causing the issue. As soon as we set this to false and restarted the Tomcat server, everything sprang into life and worked as expected.

HTH

Steve

Thanks, Steve, I'm going to try this later today. @jcompagner: I have messaged you the address of the test server in case you want to look at the error later. Right now the server is hosting a build without the Outlook integration. We can agree a time and I will upload the failing version.

set servoy.ngclient.enableWebResourceOptimizer to False

appears to fix our problem. I can deploy normal Servoy with the Office365-plugin and our Outlook module.
Can't try the outlook integration yet because we are changing strategy to deploy this as a single solution, with different startup forms depending on whether it is started inside Outlook or as a normal Servoy solution.

we are really talking about this right? https://github.com/Servoy/office365/wiki

i don't see a very complex js code purely in the plugin for that so not sure what really is killed by the grouping

but that is all quite old code not sure if it is really looked at or maintained (its not ported to Titanium NGClient)

Yes, it is this one. We have forked it and Juan has done some work for us on it which we are happy to give back to the community.
It would be good to know what your plans are.