Hello,
I am successfully deploying a standalone java application using Java Webstart. I an using the JDBC connector from "mysql-connector-java-5.1.10-bin.jar" to connect to a remote database. The application is intended to run in offline mode and go online only when updates are available. The application runs without problems when the Java Webstart server is online. Problems appear when the server is down. Because the application is started using ./javaws -offline /../myapp.jnlp, having an offline server should not make any difference.
After studying the logs from both client and server i found out that the application is requesting the MySql Driver from the server even if it already has it cached. The request is made when DriverManager.getConnection is executed. I mention that the ClassLoader given as parameter to the getConnection method is the same classloader that loaded the application.
I am successfully deploying a standalone java application using Java Webstart. I an using the JDBC connector from "mysql-connector-java-5.1.10-bin.jar" to connect to a remote database. The application is intended to run in offline mode and go online only when updates are available. The application runs without problems when the Java Webstart server is online. Problems appear when the server is down. Because the application is started using ./javaws -offline /../myapp.jnlp, having an offline server should not make any difference.
After studying the logs from both client and server i found out that the application is requesting the MySql Driver from the server even if it already has it cached. The request is made when DriverManager.getConnection is executed. I mention that the ClassLoader given as parameter to the getConnection method is the same classloader that loaded the application.