Shouldn't happen that the trigger element names are empty,

Classic Servoy
1

Since I updated Servoy to 3.5.7 I see the following message in my log:

Shouldn’t happen that the trigger element names are empty, is this called in a script that is triggered by solution startup?

Also I see errors about null pointer exception that are probably related to this message.

Indeed I save a situation that I start a webclient using a startup method, including an argument.

https://online.globis.be/servoy-webclient/ss/s/fds_webshop/m/webshop_login/a/f7fb71a2-b8fb-1234-abcd-087042dd642b

Was there something changed in 3.5.7 (and perhaps also in 4.0) for this kind of startup?

And is it possible to go back to version 3.5.6 or was the repository changed between 3.5.6 and 3.5.7?

Martin

2

Hi Martin,

When do these errors happen ? When you load the solution ?

martinh:
And is it possible to go back to version 3.5.6 or was the repository changed between 3.5.6 and 3.5.7?

Nothing was changed in the repository between those versions. I still have the 3.5.6 installer so if you want to downgrade give me a PM and I will send you an URL.

3

Hi Robert,

The error occurs indeed when starting the URL.

Can it has something to do with version 4.0 that affects also version 3.5.7?

In version 3.5.6 you can’t say that a method has parameters, so you must checkout the arguments array.
In version 4.0 you can say:

function myFunction(myParameter)

So now you can put in coding that a method has a parameter. Could it be something like this?
Because when I look at the coding I have the impression that it is the arguments array that has null value.

Martin

4

Hi Martin,

martinh:
Can it has something to do with version 4.0 that affects also version 3.5.7?

In version 3.5.6 you can’t say that a method has parameters, so you must checkout the arguments array.
In version 4.0 you can say:

function myFunction(myParameter)

So now you can put in coding that a method has a parameter. Could it be something like this?
Because when I look at the coding I have the impression that it is the arguments array that has null value.

I just tested the webclient with passing a parameter in 3.5.7 using your syntax and it all works for me.
Also in Servoy 4 you still need to checkout the arguments for methods. If I remember correctly only custom functions (inside methods) can use arguments in the function name.

5

yes arguments are not yet supported in 4.0.x this is being worked on.

Martin, are you touching the application.getMethodTriggerElementName() or something like that in your startup method?

6

jcompagner:
Martin, are you touching the application.getMethodTriggerElementName() or something like that in your startup method?

No, but it looks like the security is not working anymore like it worked in 3.5.6. See the following topic:

http://forum.servoy.com/viewtopic.php?f=22&t=6900&start=45&st=0&sk=t&sd=a

The last replies in this topic explain more about this case