Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 18543 invoked from network); 7 Nov 2007 18:07:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Nov 2007 18:07:14 -0000 Received: (qmail 88594 invoked by uid 500); 7 Nov 2007 18:07:01 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 88569 invoked by uid 500); 7 Nov 2007 18:07:01 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 88560 invoked by uid 99); 7 Nov 2007 18:07:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Nov 2007 10:07:01 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Nov 2007 18:07:13 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 94FAF71423B for ; Wed, 7 Nov 2007 10:06:52 -0800 (PST) Message-ID: <10489900.1194458812600.JavaMail.jira@brutus> Date: Wed, 7 Nov 2007 10:06:52 -0800 (PST) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3187) SimpleApp (demo) does not work in a client setting In-Reply-To: <14568020.1194447830788.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540820 ] Myrna van Lunteren commented on DERBY-3187: ------------------------------------------- I tested that code, with IBM's implementation (weme6.1 - which is CDCFoundation 1.1), and it worked fine. I don't think an import statement by itself could cause a ClassDefNotFound, but the DriverManager class is referenced in the demo... I understand it's up to the JVM to delay loading of classes or not. So, to make this safe in all JVMs, I think a separate simple demo for the mobile platform sounds appropriate. > SimpleApp (demo) does not work in a client setting > -------------------------------------------------- > > Key: DERBY-3187 > URL: https://issues.apache.org/jira/browse/DERBY-3187 > Project: Derby > Issue Type: Sub-task > Components: Demos/Scripts > Affects Versions: 10.3.1.4 > Environment: derbyclient (no derby.jar in the classpath) > Reporter: John H. Embretsen > Assignee: John H. Embretsen > > Since J2ME support was added to the simple demo (bin-releases: demo/programs/simple/SimpleApp.java) in DERBY-2216 (first available in 10.3.1.4), the demo has not worked in a pure client setting as described in the documentation (bin-releases: demo/programs/simple/example.html). This is a regression from 10.2.2.0. > $ export CLASSPATH=.:$DERBY_INSTALL/lib/derbyclient.jar > $ cd $DERBY_INSTALL/demo/programs/simple > 10.2.2.0: > $ java SimpleApp derbyclient > SimpleApp starting in derbyclient mode. > Loaded the appropriate driver. > Connected to and created database derbyDB > Created table derbyDB > Inserted 1956 Webster > Inserted 1910 Union > Updated 1956 Webster to 180 Grand > Updated 180 Grand to 300 Lakeshore > Verified the rows > Dropped table derbyDB > Closed result set and statement > Committed transaction and closed connection > SimpleApp finished > 10.3.1.4: > $ java SimpleApp derbyclient > Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/derby/jdbc/EmbeddedSimpleDataSource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.