We're having problems with the latest version of the Excel Driver, when trying to connect to an Excel File. It's strange that we didn't have any problem with the Evaluation version, and the next java exception occurs with the commercial version:
javax.servlet.ServletException: Servlet execution threw an exception
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
root cause
java.lang.NoSuchFieldError: kd
com.hxtt.sql.excel.v.(Unknown Source)
com.hxtt.sql.excel.EmbeddedDriver.connect(Unknown Source)
com.hxtt.global.SQLState.getConnection(Unknown Source)
com.hxtt.sql.HxttDriver.if(Unknown Source)
com.hxtt.sql.HxttDriver.connect(Unknown Source)
java.sql.DriverManager.getConnection(DriverManager.java:512)
java.sql.DriverManager.getConnection(DriverManager.java:171)
adasa.interdir.db.ExcelDB.getExcelDBConnection(ExcelDB.java:126)
adasa.interdir.db.ExcelDB.initDatos(ExcelDB.java:370)
adasa.interdir.db.ExcelDB.(ExcelDB.java:49)
adasa.interdir.files.ValidateMARINE.validarConsistenciaFichero(ValidateMARINE.java:99)
adasa.interdir.files.FileManager.uploadFile(FileManager.java:1612)
adasa.interdir.servlet.UploadFileServlet.service(UploadFileServlet.java:456)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
Here's the excel file we're trying to connect:
http://dd.eionet.europa.eu/GetXls?obj_type=dst&obj_id=2810
Here's the connection code:
public static java.sql.Connection getExcelDBConnection(String filename) throws Exception {
//private static final String excelDBURLPrefix = "jdbc:Excel:///";
String databaseURL = excelDBURLPrefix + filename;
Class.forName("com.hxtt.sql.excel.ExcelDriver").newInstance();
return DriverManager.getConnection(databaseURL, "", "");
}
I repeat this code works fine if I replace the commercial jar version with the evaluation jar version.
Regards...
|
>java.lang.NoSuchFieldError: kd
>com.hxtt.sql.excel.v.(Unknown Source)
Please check your classpath, which should have other older HXTT Package files. You should remove or upgrade those older files.
|
We're thinking that's not the problem. In the same application we're using your Access JDBC driver, I enclose the MANIFEST.MF information ot this driver. Maybe there's a conflict with the two drivers. We had a similar problem at the beginning of the development (a java.lang.IllegalAccessError Exception), but it was resolved using newer versions of the jar files.
Manifest-Version: 1.0
Created-By: HXTT Version Robot
Main-Class: com.hxtt.sql.admin.Admin
Name: com/hxtt/sql/admin/
Specification-Title: HXTT Database Admin
Implementation-Title: com.hxtt.sql.admin
Specification-Vendor: Hongxin Technology & Trade Ltd.
Specification-Version: 0.5 on July 28, 2010
Comment: HXTT Database Admin
Implementation-Version: 0.5 on July 28, 2010
Implementation-Vendor: Hongxin Technology & Trade Ltd.
Implementation-URL: http://www.hxtt.com/access/dbadmin.html
Name: com/hxtt/sql/access/
Specification-Title: HXTT Access JDBC 3.0 Package
Implementation-Title: com.hxtt.sql.access
Specification-Version: 4.0.017 on July 28, 2010
Specification-Vendor: Hongxin Technology & Trade Ltd.
Comment: JDBC 3.0 Package for Microsoft Access
Implementation-Version: 4.0.017 on July 28, 2010
Implementation-Vendor: Hongxin Technology & Trade Ltd.
Implementation-URL: http://www.hxtt.com/access.html
|
>Maybe there's a conflict with the two drivers.
Yeah. You should download the latest HXTT Access JDBC3.0 package too.
|
The fact is that we don't have any problem with the Access Driver (all the functionalities with this driver works fine), and we haven't got the license to download the latest "non-evaluation" version in the Download site nowadays.
Could you send me the latest HXTT Access JDBC3.0 package to my mail address?
|
Main
webmaster@hxtt.com