Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 47705982B for ; Mon, 16 Apr 2012 18:54:43 +0000 (UTC) Received: (qmail 23954 invoked by uid 500); 16 Apr 2012 18:54:43 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 23862 invoked by uid 500); 16 Apr 2012 18:54:42 -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 23846 invoked by uid 99); 16 Apr 2012 18:54:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2012 18:54:42 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2012 18:54:40 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 747D736E929 for ; Mon, 16 Apr 2012 18:54:19 +0000 (UTC) Date: Mon, 16 Apr 2012 18:54:19 +0000 (UTC) From: "Kim Haase (Updated) (JIRA)" To: derby-dev@db.apache.org Message-ID: <2131597435.29773.1334602459484.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1730323380.32657.1329159059458.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (DERBY-5612) Puzzling documentation about the URL to a database on the classpath MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-5612: ----------------------------- Attachment: DERBY-5612-2.zip DERBY-5612-2.stat DERBY-5612-2.diff I hope we've made more progress here -- attaching DERBY-5612-2.diff, DERBY-5612-2.stat, and DERBY-5612-2.zip, which modifies 5 topics and removes 2: M src/devguide/tdevdeploy39856.dita M src/devguide/derbydev.ditamap D src/devguide/cdevdeploy18716.dita M src/devguide/cdevdvlp17453.dita M src/devguide/cdevdvlp24155.dita M src/devguide/rdevdvlp22102.dita M src/devguide/cdevdvlp40350.dita D src/devguide/cdevdeploy856333.dita Thanks again, Knut -- further edits are welcome. > Puzzling documentation about the URL to a database on the classpath > ------------------------------------------------------------------- > > Key: DERBY-5612 > URL: https://issues.apache.org/jira/browse/DERBY-5612 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.9.0.0 > Reporter: Rick Hillegas > Assignee: Kim Haase > Attachments: DERBY-5612-2.diff, DERBY-5612-2.stat, DERBY-5612-2.zip, DERBY-5612.diff, DERBY-5612.stat, DERBY-5612.zip > > > The "Accessing databases from the classpath" section of the Derby Developer's Guide says that you can access a database on the classpath by putting a forward slash in front of the database name (and then adding other path legs as needed). I don't find that it works this way. I ran the following experiment: > 1) I put a database called nast in the testRun/extin subdirectory of the current directory. > 2) Then I put testRun/extin on the classpath. > 3) Then I tried connecting to the database with various URLs. > The following URLs could not find the database: > connect 'jdbc:derby:/nast;user=KIWI;password=KIWI_password'; > connect 'jdbc:derby:nast;user=KIWI;password=KIWI_password'; > connect 'jdbc:derby:classpath:/nast;user=KIWI;password=KIWI_password'; > But the following URL found the database: > connect 'jdbc:derby:classpath:nast;user=KIWI;password=KIWI_password'; > This is not what I expected from the documentation in the Developer's Guide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira