I'm getting the same error myself.  SDK 1.4.1_02

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Sebastian Kloska
Sent: Monday, August 25, 2003 3:08 AM
To: HSQLDB Developers
Subject: [Hsqldb-developers] Build failes under SDK 1.4.X


  Hi

  Tried to build a freshly fetched hsqldb-dev
  with JDK 1.4.2 but it failes with

<snip>
  Rebuilding EchoProperty.class...
  Building for target '1.4'
     (Resultant jar can only be used with Java JREs >= 1.4)
  Running CodeSwitcher...
  Rebuilding CodeSwitcher.class...
  Invoking CodeSwitcher...
  ......
  Generating source file list...
  Compiling 195 source file(s) ...
  org/hsqldb/jdbcParameterMetaData.java:99: cannot resolve symbol
  symbol  : variable colType
  location: class org.hsqldb.Result
         types          = r.colType;
                           ^
  org/hsqldb/jdbcParameterMetaData.java:101: cannot resolve symbol
  symbol  : variable nullability
  location: class org.hsqldb.Result
         nullability    = r.nullability;
                           ^
  org/hsqldb/jdbcParameterMetaData.java:102: cannot resolve symbol
  symbol  : variable isIdentity
  location: class org.hsqldb.Result
         isIdentity     = r.isIdentity;
                           ^
  org/hsqldb/jdbcParameterMetaData.java:103: cannot resolve symbol
  symbol  : variable sClassName
  location: class org.hsqldb.Result
         classNames     = r.sClassName;
                           ^
  org/hsqldb/jdbcParameterMetaData.java:104: cannot resolve symbol
  symbol  : variable paramMode
  location: class org.hsqldb.Result
         modes          = r.paramMode;
                           ^
  org/hsqldb/jdbcCallableStatement.java:248:
org.hsqldb.jdbcCallableStatement should be declared abstract; it does not
   define registerOutParameter(java.lang.String,int) in
org.hsqldb.jdbcCallableStatement
public class jdbcCallableStatement extends jdbcPreparedStatement
        ^
6 errors
</snip>

It actually seems that these variables are not a member of
org.hsqldb.Result but of the inner class ResultMetaData.
If I change 'r.' tp 'r.metaData' it works fine. Although
this kind of external access to a internal class member
seems to be ugly ....


What does JAVA 1.3 do ? Silently resolve the name r.isIdentity
to r.metaData.isIdentity ? (Uuuuhh that's even more spooky..)

Cheers

S.

--
**********************************
Dr. Sebastian Kloska
Head of Bioinformatics
Scienion AG
Volmerstr. 7a
12489 Berlin
phone: +49-(30)-6392-1708
fax:   +49-(30)-6392-1701
http://www.scienion.de
**********************************



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
hsqldb-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers




-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
hsqldb-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

Reply via email to