Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 41245 invoked from network); 3 Mar 2008 14:02:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2008 14:02:00 -0000 Received: (qmail 55349 invoked by uid 500); 3 Mar 2008 14:01:53 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 55296 invoked by uid 500); 3 Mar 2008 14:01:53 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 55285 invoked by uid 99); 3 Mar 2008 14:01:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Mar 2008 06:01:53 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Mar 2008 14:01:26 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 84B7C234C085 for ; Mon, 3 Mar 2008 06:00:50 -0800 (PST) Message-ID: <2097624312.1204552850542.JavaMail.jira@brutus> Date: Mon, 3 Mar 2008 06:00:50 -0800 (PST) From: "Ralf Baumhof (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-3878) Unable to deploy Postgres Datasource from console dialog "Database Pools" because of missing jar files in jar selection listbox. In-Reply-To: <110889957.1204107831223.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574508#action_12574508 ] Ralf Baumhof commented on GERONIMO-3878: ---------------------------------------- Yes, that's right. It works if you donwload the driver directly. The dialog first does not work, if you try a test, it fails. But after this first failure, the dialog is ok. It always comes up with the corret postgres specific settings, and more over, the datasource is ok. The application works. But i'am still confused because of the following: - Why this strange behaviour - only for Postgres? With geronimo 2.0.2 you could download the driver separately, and then use the common libs dialog (now called repository) to deploy it. Then you will see it in the jars listbox. This still works - if you use another database type (like DB2). - This workaround is not suitable for a production system. In production we "NEVER" have a internet connection. People in the production system are used to get a jar, and then they deploy it using the dialoge. So, i could use the dialog of an other system with internet connection to create a plan and advice production to deploy the plan. But this will probably result in editing and changing the plan to the preferences of production systems. And this will result in errors. > Unable to deploy Postgres Datasource from console dialog "Database Pools" because of missing jar files in jar selection listbox. > -------------------------------------------------------------------------------------------------------------------------------- > > Key: GERONIMO-3878 > URL: https://issues.apache.org/jira/browse/GERONIMO-3878 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console > Affects Versions: 2.1 > Environment: Windows XP Professional and Ubuntu > Reporter: Ralf Baumhof > Original Estimate: 120h > Remaining Estimate: 120h > > Trying to deploy a datasource with console dialog "Database Pools". > - Select link "Console Navigation/Services/Database Pools". > - Select link "Using the geronimo database pool wizard". > - Enter some database name like for instance "vesuv" and select as Database Type: "PostgreSQL XA" or "PostgreSQL local". > - Click the Next button. > - Now, on the page where you specify the properties of the database pool, the listbox where you can select the driver jar is empty. If you choose another database type (on the previous dialog page), the list is filled with all entries from repository. The same steps have been made with Geronimo 2.02. There the database could be deployed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.