From derby-user-return-359-apmail-db-derby-user-archive=db.apache.org@db.apache.org Wed Dec 15 19:56:53 2004 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 3262 invoked from network); 15 Dec 2004 19:56:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Dec 2004 19:56:53 -0000 Received: (qmail 10318 invoked by uid 500); 15 Dec 2004 19:56:52 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 10300 invoked by uid 500); 15 Dec 2004 19:56:51 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 10281 invoked by uid 99); 15 Dec 2004 19:56:51 -0000 Received-SPF: pass (hermes.apache.org: local policy) Received: from i.meepzor.com (HELO Boron.MeepZor.Com) (204.146.167.214) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 15 Dec 2004 11:55:36 -0800 Received: from [9.72.133.64] (dmz-firewall [206.199.198.4]) by Boron.MeepZor.Com (8.12.8/8.12.8) with ESMTP id iBFISOwE012143 for ; Wed, 15 Dec 2004 13:28:25 -0500 Message-ID: <41C08219.5040705@Golux.Com> Date: Wed, 15 Dec 2004 10:27:37 -0800 From: myrnap User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Discussion Subject: Re: OSGi bundle dependency References: <6E58A7C8A2126D44ACBC06D1DA24CFD13FAC18@blv2-exc-01.siq.solutionsiq.com> In-Reply-To: <6E58A7C8A2126D44ACBC06D1DA24CFD13FAC18@blv2-exc-01.siq.solutionsiq.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Jeff Ramsdale wrote: > I was excited to find OSGi support built into Derby and I just had to > drop it into Knopflerfish to start poking around. I was a little set > back when I received an error because Derby couldn't find a java.sql > package. No problem--I hit Google to find a bundle, but to my dismay > I've been unable to find one! > > I'm a little new to OSGi and I don't yet have much experience with > Derby. So I'm wondering how best to make use of this functionality. > Does anyone have experience using Derby as a bundle? If so, how did > you resolve this dependency? Also, do any of you know of uses of Derby > with OSGi? Seems like a perfect match--I'd love to hear how other > people are making use of it... > > Jeff Jeff, The OSGI support was put in place specifically to support the IBM SMF (software management framework - which is an implementation of the OSGI specifications in IBM WebSphere Client Technology) because of a customer request. So it has actually been used in that context. However, support should not be limited to that particular OSGI implementation. The java.sql package is indeed required for the Derby database. It should be there in the environment, or as a separate bundle... Myrna