Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <46CEC38A.8050406@sun.com>
Date: Fri, 24 Aug 2007 12:39:54 +0100
From: Alan Burlison <Alan.Burlison@sun.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070423)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: NPE when connecting to database with securityMechanism=8
References: <46CCA045.50406@sun.com> <wjo87inmk4d3.fsf@sun.com>
 <46CD5845.7010000@sun.com> <wjo8y7g2imjz.fsf@sun.com>
 <46CD633A.10203@sun.com> <46CD888A.3030506@sun.com>
 <wjo8tzqqib35.fsf@sun.com>
In-Reply-To: <wjo8tzqqib35.fsf@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Knut Anders Hatlen wrote:

> You shouldn't load the client driver unless your application uses
> jdbc:derby://localhost/mydb. The reason why the client driver seems to
> work in your case, is that the server already has loaded the embedded
> driver. So the code that runs inside the same JVM as the server should
> use jdbc:derby:mydb and not load the client driver, whereas the external
> scripts should load the client driver and use
> jdbc:derby://localhost/mydb.

Unfortunately it's not that simple.  If you use the embedded driver with 
  STRONG_PASSWORD_SUBSTITUTE_SECURITY & securityMechanism=8, you get a 
NPE is you open, close and then reopen the database - which is necessary 
if you want to be sure that the static database properties you set are used.

This all seems as fragile as hell, to be honest...

-- 
Alan Burlison
--