I logged a bug since we’ve been banging our heads against a wall for a couple of days. Feel free to up vote it or reference it in your own ticket. https://support.servoy.com/browse/SVY-6186
Hi Matt,
Thanks for logging this! I was still investigating if it was a pure servoy issue or something in our code
I voted your case
Robrecht
this error:
Mar 06, 2014 10:36:11 AM com.servoy.j2db.util.Debug error
SEVERE: Cannot sort elements, transitivity is not respected for forms:svy_nav_fr_p_browser_base and svy_nav_lfo_browser
is very weird especially if you only get that in a smart client but not in the developer
(your really for the same solution you also should get that on a real webclient)
Because that message is printed if form1 extends form2 and form2 extends form1 again…
And if you don’t get that in developer but you do get that in the app server then i think there is something wrong with the import
If you do a new export from your developer and you do a import on a clean,fresh install of the app server, do you still get it then?
(if you install a quick demo/tmp app server)
If you still get it, i would like to see the exported solution so that i can have a look right inside that and see if there really is an extends problem suddenly
Else it is somehow a import that merged wrongly (maybe at some point it had a different extends and that isn’t updated quite correctly)
Hi Johan,
I installed 7.4 rc3 on my local machine, and the error is still there…
Smart client fails on these form and again, the webclient works fine
If you want to take a look at the solution please contact me
Robrecht
its very weird that the webclient on an server (not developer right?) doesn’t give that same exception/warning
Because that code is exactly the same. There is no difference between solution code in smart or web.
But if you have a solution that demonstrates this, please make a case and attach the solution to it (you can make it private if you want)
Well, the warning is in the java console which is only there for the smart client
The application server itself doesn’t give any warnings
Maybe it’s caused by other code executed in smart than in web (coded by us…?)
I can show it in the start up of our main solution, but I know from other cases it’s hard for you guys to get it started
Can you talk to Joas about it? He has our solution from 2 months ago and i assume the problem will already be there…
Together with Laurian we found that the bug is caused by ‘Enhanced Security’ set false.
Hopefully this will fix your problem as well Matthew, thanks for the support.
Robrecht