Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 43667 invoked from network); 24 Jun 2010 20:09:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 Jun 2010 20:09:30 -0000 Received: (qmail 92466 invoked by uid 500); 24 Jun 2010 20:09:29 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 92444 invoked by uid 500); 24 Jun 2010 20:09:29 -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 92437 invoked by uid 99); 24 Jun 2010 20:09:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jun 2010 20:09:29 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [32.97.110.160] (HELO e39.co.us.ibm.com) (32.97.110.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jun 2010 20:09:19 +0000 Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id o5OJxfmF021250 for ; Thu, 24 Jun 2010 13:59:41 -0600 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o5OK8tB2114668 for ; Thu, 24 Jun 2010 14:08:55 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id o5OK8sLS015145 for ; Thu, 24 Jun 2010 14:08:54 -0600 Received: from [127.0.0.1] (sig-9-48-101-127.mts.ibm.com [9.48.101.127]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id o5OK8q0K015037 for ; Thu, 24 Jun 2010 14:08:54 -0600 Message-ID: <4C23BB55.1010008@sbcglobal.net> Date: Thu, 24 Jun 2010 13:08:53 -0700 From: Kathey Marsden User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Is there a jvm option or quick way to disable driver auto loading? References: <4C23A9CB.1020103@sbcglobal.net> <4C23B507.80909@oracle.com> In-Reply-To: <4C23B507.80909@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 6/24/2010 12:41 PM, Rick Hillegas wrote: > Hi Kathey, > > I'm not aware of a command line option to disable driver autoloading. > However, driver autoloading should not occur if you remove the > following file from derby.jar and derbyclient.jar: > > META-INF/services/java.sql.Driver > > I'm curious about how this interacts with DERBY-4688. I am sorry that was a typo. It is DERBY-4668. JCC can grab the Derby stored procedure connection just by being in the classpath, so it is their driver that I want to prevent from loading.