I’ve created a bean that depends on an external .jar file which I have put in the $SERVOY_HOME/lib directory. It works when I open it in the developer, and I have the solution ready to export for clients.
The problem is that when I open the solution in Servoy (non-developer) the bean dependency .jar doesn’t get downloaded to the client when accessing over a network. It will show up if I open Servoy on the server machine (where the dependency .jar is local) but not over a network.
I have also tried putting the dependency .jar file in the $SERVOY_HOME/beans directory along with my bean .jar, but it still has the same problem.
Please, any advice?
Thanks,
Fred
I don’t know about beans, but when a plugin depends on an external jar you need an extra jnlp file for that (as far as I know). Check out for example the scheduler.jar.jnlp in the plugins directory. The scheduler plugin also depends on an external jar, in that case the quartz.jar.
Maybe that helps…
Patrick,
Thanks for the suggestion, unfortunately it didn’t work.
I think I figured it out though, all of the .jars in the $SERVOY_HOME/beans directory are downloaded to the client on startup. I had put the .jar file my bean depends on in that beans directory after I’d already started the client once and it wasn’t copying the new bean .jar to the client. I had to go into the client machine, delete all of the Java webstart cache files and try it again. Once the cache files were cleared it downloaded everything and is working properly.
I hope this helps someone else.