Please take a look at the Help Forum where there was a post today from
someone who uses HSQLDB with CrEME (unspecified version).
I guess you should switch to JDK 1.3 and recompile. This _should_ then run
under 1.1. If there are problems, we should be able to fix them.
You can test your findings youself . Just make a copy of the source tree and
try to rename the decompiled interface to something and change the interface
that jdbcConnection implements to the fake interface. See where there is a
compilation problem.
Fred
----- Original Message -----
From: "Sheldon Young" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 19 March 2004 23:44
Subject: RE: [Hsqldb-developers] CrEme 4.0 fails to connect
I'm running 1.7.2 RC3 with the hsqldb.jar included in the lib/ directory. A
rebuild with the target switched to 1.1 and J2SDK 1.4.2_02 results in the
same behaviour. The code is attempting to connect to a local cached
database ("jdbc:hsqldb:testdb"). The org.hsqldb.jdbcDriver class was loaded
fine a few lines before that.
The only thing that comes to mind is that there's a difference in the
Connection interface implemented by jdbcConnection. A decompile of the
Connection class in CreMe looks like this:
interface java.sql.Connection{
public static final int TRANSACTION_NONE;
public static final int TRANSACTION_READ_UNCOMMITTED;
public static final int TRANSACTION_READ_COMMITTED;
public static final int TRANSACTION_REPEATABLE_READ;
public static final int TRANSACTION_SERIALIZABLE;
public abstract void clearWarnings();
throws java/sql/SQLException
public abstract void close();
throws java/sql/SQLException
public abstract void commit();
throws java/sql/SQLException
public abstract java.sql.Statement createStatement();
throws java/sql/SQLException
public abstract boolean getAutoCommit();
throws java/sql/SQLException
public abstract java.lang.String getCatalog();
throws java/sql/SQLException
public abstract java.sql.DatabaseMetaData getMetaData();
throws java/sql/SQLException
public abstract int getTransactionIsolation();
throws java/sql/SQLException
public abstract java.sql.SQLWarning getWarnings();
throws java/sql/SQLException
public abstract boolean isClosed();
throws java/sql/SQLException
public abstract boolean isReadOnly();
throws java/sql/SQLException
public abstract java.lang.String nativeSQL(java.lang.String);
throws java/sql/SQLException
public abstract java.sql.CallableStatement
prepareCall(java.lang.String);
throws java/sql/SQLException
public abstract java.sql.PreparedStatement
prepareStatement(java.lang.String
);
throws java/sql/SQLException
public abstract void rollback();
throws java/sql/SQLException
public abstract void setAutoCommit(boolean);
throws java/sql/SQLException
public abstract void setCatalog(java.lang.String);
throws java/sql/SQLException
public abstract void setReadOnly(boolean);
throws java/sql/SQLException
public abstract void setTransactionIsolation(int);
throws java/sql/SQLException
}
> -----Original Message-----
> From: fredt [SMTP:[EMAIL PROTECTED]
> Sent: Friday, March 19, 2004 3:24 PM
> To: Sheldon Young
> Subject: Re: [Hsqldb-developers] CrEme 4.0 fails to connect
>
> Unable to create a connection to what?
>
> Which version are you using and how have you recompiled the sources?
>
> Fred
>
> ----- Original Message -----
> From: "Sheldon Young" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: 19 March 2004 16:59
> Subject: [Hsqldb-developers] CrEme 4.0 fails to connect
>
>
> The CrEme 4.0 virtual machine for PocketPCs is unable to create a
conection
> because of an incompatible class change error that gets thrown in the
> jdbcConnection constructor. It does not seem to matter if the virtual
> machine is run in Personal Java mode or not.
>
> Anybody have any thoughts?
>
>
> NSIcom Ltd., CrEme(tm) Evaluation Version
> CrE-ME J2ME(tm)
> CrE-ME V4.00 B10.031202 02-Dec-2003
> MemoryLimit=27776Kb
> EBCI(TM) Interpreter ARM-EVC-XSCL V1.05,
> Copyright 1998-2003 by Bytecodes, Inc.
> writeScript
> java.sql.SQLException: General error:
> java.lang.IncompatibleClassChangeError: Unimplemented interface method
> at org.hsqldb.jdbc.jdbcUtil.sqlException()
> at org.hsqldb.jdbc.jdbcConnection.<init>()
> at org.hsqldb.jdbcDriver.getConnection()
> at org.hsqldb.jdbcDriver.connect()>
> at java.sql.DriverManager.getConnection()
> at java.sql.DriverManager.getConnection()
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=ick
> _______________________________________________
> hsqldb-developers mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=ick
_______________________________________________
hsqldb-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
hsqldb-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
