[ 
https://issues.apache.org/jira/browse/GERONIMO-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734027#action_12734027
 ] 

Jürgen Weber commented on GERONIMO-4725:
----------------------------------------

With groupid "mysql" I got the DataSource to work, thanks.

But this should be fixed, how should users know which dependency to use?

And, if there is a fixed dependency for the driver gbean, why should the user  
choose a Driver JAR at all? It would be better if selecting a Database Type 
would show the necessary driver jars:

selecting Database Type "MySQL" would display
"this needs mysql/mysql-connector-java//jar in the repository"

> 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.

Reply via email to