java webstart error when going to an early build of server

Classic Servoy
1

A couple of times I have upgraded the application server to a newer build, and used the new build in production. When problem were identified with the new build I had to go to a prior build of the application server. After converting to the prior version of the application server my clients are no longer able to log on. They get a message that thier are no licenses. If I go into the Java Webstart advanced preferences and clear the application folder, it fixes the problem and allows Java Webstart to download the older version. It is not convenient to tell all of the users to clear the application folder. Can this be fixed?

John McCann

2

how do you go back?
Just copy/move the install?

The problem is that you use older jars webstart doesn’t convert back to older jars. Only newer onces.

So you need to ‘touch’ the jar file so that the file timestamp is changed to now (so that webstart things the jars are newer)

If you are using linux then you can use touch to do this (the files j2db.jar and js.jar are the most importand once to touch)

on windows there are some tools for this. (you could try google)

3

To upgrade I rename the servoy folder. Do a clean install. Then I copy drivers, beans, plugins, and properties from the old to the new folder.

Next time I have to do it I will figure out how to touch it and report back.

It is useful to know how JAVAWEBSTART knows when to load a new JAR.

Thanks

John McCAnn