Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 05 Nov 2007 17:58:48 +0100
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: Can't run Derby 10.3 on CDC platform
In-reply-to: <472F3F9F.80000@sun.com>
Sender: Knut.Hatlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <wjo8ve8gr5mf.fsf@khepri41.norway.sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <472F3F9F.80000@sun.com>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (usg-unix-v)

Rick Hillegas <Richard.Hillegas@Sun.COM> writes:

> I am able to run Derby 10.2 on the phoneME implementation of the CDC
> platform. That is, using Derby 10.2 on that platform, I am able to
> successfully create a database and query the system tables. So far so
> good.
>
> However, when I run the same experiment with Derby 10.3, the database
> fails to boot because it can't find an appropriate
> DataValueFactory. This is true whether I use the Derby 10.3 jars,
> current jars built from the mainline, or the classtree built from the
> mainline. I would appreciate clues about what changed in 10.3 which
> would cause this behavior.

Hi Rick,

In Derby 10.3, we dropped Foundation 1.0 support and moved to Foundation
1.1, as far as I remember. Your device doesn't by any chance have a too
old JVM?

-- 
Knut Anders