Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <31479661.1194379971842.JavaMail.jira@brutus>
Date: Tue, 6 Nov 2007 12:12:51 -0800 (PST)
From: "Daniel John Debrunner (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3176) J2ME support for phoneME platform
 disabled in 10.3
In-Reply-To: <7367602.1194360771239.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540544 ] 

Daniel John Debrunner commented on DERBY-3176:
----------------------------------------------

Note that it's also the purpose of the JVMInfo class to decide what Java specification Derby is going to run at, not to report what the actual real environment is.

Thus I don't think this is valid (as in the phoneme case):

CDC_FP_VERSION = javaVersion

Derby runs at CDC/Foundation 1.1, if the phoneME code changes its version to 1.2 with no Derby changes it doesn't mean Derby is running in the CDC/Foundation 1.2 version.

I think these lines

 		case J2SE_13: return J2ME ? "J2ME - JDBC for CDC/FP 1.0" : "J2SE 1.3 - JDBC 2.1";
+		case J2ME_JDK: return "J2ME - JDBC for CDC/FP " + CDC_FP_VERSION;
 		case J2SE_14: return "J2SE 1.4 - JDBC 3.0";

should be

 		case J2SE_14: return J2ME ? "J2ME - JDBC for CDC/FP 1.1"  : "J2SE 1.4 - JDBC 3.0";


> J2ME support for phoneME platform disabled in 10.3
> --------------------------------------------------
>
>                 Key: DERBY-3176
>                 URL: https://issues.apache.org/jira/browse/DERBY-3176
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.3.1.4
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-3176-01-phoneME-aa.diff, derby-3176-01-phoneME-ab.diff
>
>
> Derby 10.2 runs on the phoneME small device platform. However, on that platform Derby 10.3 fails to boot databases, complaining that Derby cannot find an appropriate implementation of DataValueFactory.
> For details on how to install and run the phoneME platform, please see http://blogs.sun.com/wittyman/entry/javadb_on_sun_javame_cdc These are great instructions but I needed to adjust them as follows:
> 1) I had to use 10.2 because 10.3 and the development mainline would not run on this platform
> 2) I needed to to set LD_LIBRARY_PATH so that the vm could find the necessary shared libraries.
> Here is the phoneME startup script which worked for me:
> #! /bin/bash
> #
> # Run an ij script in the phoneME vm
> #
> # $1 is the script to run
> export LD_LIBRARY_PATH=$CDC_HOME/lib
> cd ~/demo/tearoffToPhone/data
> $CDC_HOME/bin/cvm -Xbootclasspath/a:$JSR169_HOME/lib/jsr169.jar \
>   -cp $DERBYJARS/derby.jar:$DERBYJARS/derbytools.jar \
>   -Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource \
>   -Dij.dataSource.databaseName=sample  \
>   -Dij.dataSource.createDatabase=create \
>   org.apache.derby.tools.ij $1

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.