OK, so I upgraded to 5.2.1 on the app server. I set it in the web console as in the attachment. It no longer opens up servoy in the existing client, it opens a new client.
[attachment=0]Screen shot 2010-09-28 at 11.04.40 AM.png[/attachment]
you have to pass a method parameter in the deep link or it will spawn a new instance of servoy. However, if it is the first time it is launched, it will not execute the damned method. Subsequent times, it will skip all the login stuff and run the startup method. I suppose it makes some kind of sick sense, but you have to make sure it runs the called method stuff you want whether in the login/auth solutions or in the actual solution; and there is a question about where to put that because before you log in, you can’t access methods in the main solution.
This new security stuff is a pain in the ass. I’m just saying.
Hi Jmcneely,
That the deeplink method doesn’t get triggered when the Smart Client is started first time, was a bug that we found in our testing for the 5.2.2 release and thus is is fixed in 5.2.2 release, which was released yesterday.
The behavior of firing the deeplink method hasn’t changed for a long time (I think it’s been like this since 3.5 and maybe earlier): the deeplink method gets fired after successful login and after the firing of the onOpen method of the solution.
I’m not sure where your comment on the new security stuff is coming form, as it’s completely not related to anything has to do with deeplinking.
Regards,
Paul