SQL Server SQLJDBC4 Driver won't connect from Browser.

Question

Hello,
First I hope I have selected the correct Category and Forum for this, please move if required and my apologies.
We have a (Digitally Signed) Java Applet that resides on a HTTPS enabled server usinng a EV Digital Certificate. Having made a simple tweak to the Java's source I rebuilt the project and tested it in Eclipse Luna, all went well with this and a SQL connection
made. Running the jar file via a DOS CLI using java -jar applet.jar also works and a connection is made to the remote SQL server.
However, if I browse to the URL I get a dialog warning me about the SQLJDBC jar file and asks if I am willing to accept the risk, which I am. However, the applet instantly fails while trying to connect and simply dumps "SEVERE: com.microsoft.sqlserver.jdbc.SQLServerDriver"
to the Java console.
This is all the information I get not even a StackTrace, to say I am confused is an understatement and I would be obliged if anyone can help me resolve this.
The same happens on Windows 7 x64, Windows 8.1 x64 regardless of the browser used.
Thanks.

Answer 1

OK, I've tweaked the code and the stacktrace output was being suppressed by the logger, so I now have
Missing Application-Name manifest attribute for: https://redacted/jars/sqljdbc4.jar
Then I get:
java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
    at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
    at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)
    at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
    at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at cut.out.UI.connectSQL(UI.java:691)
    at cut.out.UI.init(UI.java:677)
    at com.sun.deploy.uitoolkit.impl.awt.AWTAppletAdapter.init(Unknown Source)
    at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Which I suspect is a consequence of the missing attribute from the jar file, is the source available for this Jar so I can include this and digitally sign it myself?
Bob