My Servoy Application server is running on Windows 2003 (SBS)
I have 2 clients, 1 Windows Vista and 1 MAC.
Using the developer on Windows, I change some global script.
After save script en quit developer, I flush my solution
By the way, the following also occurs when shutdown server en bring up again, so it is not a flush problem.
When I start Servoy client on Windows PC, changes are downloaded and I see the change I made in the global script.
When starting Servoy client on MAC, there is some download, but the functionality I put into the global script is not working.
Because script is not very visible on a client, I made a change on a form in the same solution as where my global script is.
Now after flushing the solution, the changes are visible on MAC (both form and script change).
So it looks like that when form has not been changed, then refresh of the solution on MAC is not working. On Windows it works like expected.
Has someone experienced the same situation?
MAC testing has been done with JAVA 1.5 and also JAVA1.6 beta.
When running developer (both on Windows and Mac) as an application server I don’t see this happening.
I test changes sometimes more than once a day, but again that is running the developer.
I have randomly experienced this before, but have never been able to figure out exactly what causes that problem. The only fix is to fully clear the java cache. See: http://www.servoyguy.com/knowledge_base … java_cache for instructions if you need.
That usually happened in an environment where the Developer is connected directly to the same repository as the Server. If you switch to use a different repository, and then import your solutions over into production when they are ready, that has fixed the problem in my experience.
That usually happened in an environment where the Developer is connected directly to the same repository as the Server.
This is indeed the case.
But I tried also a completely shutdown of the server and start it again (so not just a restart server), and the situation still occurs.
So I would say that it is a problem on the local client and not specific on the server.