On 6/13/07, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
Mike Jarmy wrote:

>
> FYI -- For anyone else reading this thread, JclMax is a superset of J2ME
> which includes quite a few more classes, but sadly java.sql.* is not
> among them.


What environment are you running in? JCLMax is not any official Java
profile so it may or may not work with Derby. Derby works on
J2ME/CDC/Foundation 1.0/1.1, jdk 1.3, jdk 1.4, jdk 1.5 & jdk6.

If you run

java org.apache.derby.tools.sysinfo

and send the output it will be a help. There is a line that indicates
what Derby thinks the JVM support level is:

E.g. I see this in JDK 1.4.2

--------- Derby Information --------
JRE - JDBC: J2SE 1.4.2 - JDBC 3.0

Dan.




I'm cross-compiling, so I'm actually using two environments.  I'm
*compiling* on a plain old Windows box, but *running* on a QNX machine that
is using IBM's J9 JVM, which uses JclMax as the class library.  I have no
way of directly compiling on the QNX box.

FYI, my test program runs just fine in Windows.  Its QNX that is the problem
(and QNX/J9/JclMax is the environment that my company's product's ship on).

JclMax's packages are as follows.  What I really need, I think, is some way
of telling derby that these are the only java.* packages available.  I'm not
sure whether I need to tell derby this at compile time, or runtime, or both.

   java.io
   java.lang
   java.math
   java.net
   java.security
   java.text
   java.util
   java.lang.ref
   java.lang.reflect
   java.security.acl
   java.security.cert
   java.security.interfaces
   java.security.spec
   java.util.jar
   java.util.zip
   javax.crypto
   javax.microedition
   javax.net
   javax.security
   javax.crypto.interfaces
   javax.crypto.spec
   javax.microedition.io
   javax.microedition.pki
   javax.net.ssl
   javax.security.auth
   javax.security.cert
   javax.security.auth.x500

Here is the sysinfo output from the QNX machine.  It appears that QNX is
claiming that its a subset of 1.4.2, which I guess it is, but apparently a
somewhat non-standard one.

   # /ive/bin/j9 -Xbootclasspath/a:/ive/lib/jdbc.jar -Xmso128K -jcl:max
-noverify -Xmx48M -Xms48M org.apache.derby.tools.sysinfo
   ------------------ Java Information ------------------
   Java Version:    1.4.2 subset
   Java Vendor:     IBM Corporation
   Java home:       /ive
   Java classpath:
/ive/lib/jclMax/classes.zip:/niagara/modules/baja.jar:/ive/lib/prsnlqnx.jar:/ffs0:/ffs0/derby.jar
   OS name:         QNX
   OS architecture: ppc
   OS version:      6.3.2
   Java user name:  tridium
   Java user home:  /
   Java user dir:   /ffs0
   java.specification.name: Java Platform API Specification
   java.specification.version: 1.4
   --------- Derby Information --------
   JRE - JDBC: J2SE 1.4.2 - JDBC 3.0
   [/ffs0/derby.jar] 10.2.2.0 - (???)
   ------------------------------------------------------
   ----------------- Locale Information -----------------
   ------------------------------------------------------

And, though I'm not sure how relevant it is, here is the sysinfo output from
the Windows box.

   D:\code\derby>java -classpath derby.jar org.apache.derby.tools.sysinfo
   ------------------ Java Information ------------------
   Java Version:    1.4.0_01
   Java Vendor:     Sun Microsystems Inc.
   Java home:       D:\niagara\r3dev\tools\jdk14\jre
   Java classpath:  derby.jar
   OS name:         Windows XP
   OS architecture: x86
   OS version:      5.1
   Java user name:  mjarmy
   Java user home:  D:\Documents and Settings\mjarmy
   Java user dir:   D:\code\derby
   java.specification.name: Java Platform API Specification
   java.specification.version: 1.4
   --------- Derby Information --------
   JRE - JDBC: J2SE 1.4 - JDBC 3.0
   [D:\code\derby\derby.jar] 10.2.2.0 - (???)
   ------------------------------------------------------
   ----------------- Locale Information -----------------
   ------------------------------------------------------

Reply via email to