| weiss.matt@gmail.com 2007-11-30, 10:13 pm |
| Hey All,
I have an Installanywhere installer built with InstallAnywhere 2008.
My java application requires that I set up the database as part of the
installation. I am supporting Oracle, Mysql and Microsoft SQL server
2005. I am able to connect successfully to Oracle or Mysql. But when
I try to connect to a MSSQL database using the microsoft jdbc driver
(1.1 or 1.2) I get a java.lang.SecurityException on com/microsoft/
sqlserver/jdbc/SqlServerException.class. The exception message is:
"no manifest section for signature file entry com/microsoft/sqlserver/
jdbc/SqlServerException.class". Note that this is in the context of
the JRE that install anywhere runs, not my application JRE.
Strange enough our application works fine with this driver. I
conjecture that installanywhere is purposefully verifying signed jars,
whereas our applicatioon may not be. Can anyone shed some light on
this problem? Can I tell the JRE NOT to verify signed jars?
What are the legal ramifications of actually extracting the Microsoft
JDBC driver, removing the Signature content from it, and re-jarring
it? Can I legally do this?
Thanks in advance,
Matt
|