From dev-return-75190-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Fri Jul 24 03:34:35 2009 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 26196 invoked from network); 24 Jul 2009 03:34:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Jul 2009 03:34:35 -0000 Received: (qmail 61524 invoked by uid 500); 24 Jul 2009 03:35:40 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 61423 invoked by uid 500); 24 Jul 2009 03:35:39 -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 61415 invoked by uid 99); 24 Jul 2009 03:35:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2009 03:35:39 +0000 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; Fri, 24 Jul 2009 03:35:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 38EB5234C04B for ; Thu, 23 Jul 2009 20:35:15 -0700 (PDT) Message-ID: <802199219.1248406515232.JavaMail.jira@brutus> Date: Thu, 23 Jul 2009 20:35:15 -0700 (PDT) From: "Rex Wang (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-4725) MySQL jdbc connector/driver jars don't show up in the database pool wizard In-Reply-To: <363340187.1246456667289.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734889#action_12734889 ] Rex Wang commented on GERONIMO-4725: ------------------------------------ Well, that is not a good user experience. The original intention of the dependency filter is to help user to find the specific jar from a bunch jars in the list. That is, if there is no filter constaint on this gbean, the list box on the portlet will show all the jars(might contain db2, informix... and others jars even not a jdbc driver.), And that is also a bad user experience I think. let the user choose a Driver JAR is because there might many versions of one type of jdbc driver. However, I also agree that the filter is too strict when try to find the jars. maybe we can use some sorts of regular expression. I'd like to open an improvement later. -Rex > MySQL jdbc connector/driver jars don't show up in the database pool wizard > -------------------------------------------------------------------------- > > Key: GERONIMO-4725 > URL: https://issues.apache.org/jira/browse/GERONIMO-4725 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Affects Versions: 2.1.4 > Environment: Geronimo 2.1.4, WindowsXP > Reporter: Jan Snelders > Assignee: Rex Wang > Fix For: 2.1.4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > MySQL connector/driver jars don't show up in the database pool wizard when added to the repository even if you download the 3.x.x driver using the exact same wizard. > Steps to reproduce; > - Start a newly installed geronimo 2.1.4. server (I only tested on WindowsXP) > - login to the web console > - Start adding a connection pool using the 'Geronimo database pool wizard' > - Choose 'MySQL' for 'Database Type' and click on 'Next' to go to the next step > - The multiple select control labeled; 'Driver JAR' is empty at this time, choose 'Download a driver' and install the MySQL Connector /J 3.1.12 > - When done installing the connector the wizard refuses to show the installed connector/driver > - The problem also accures also when mannually adding the latest MySQL connector to the repository (under the group "mysql") > This bug is not present in geronimo 2.1.3 (tested on WindowsXP) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.