[
https://issues.apache.org/jira/browse/GERONIMO-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577497#action_12577497
]
David Jencks commented on GERONIMO-3905:
----------------------------------------
What algorithm do you propose to choose when there are several different
versions of a driver in the repo?
How do you propose to deal with the case of a multi-jar driver (IIRC db2 has
several required jars)?
My initial response to this suggestion is that it would introduce a lot of very
hard to maintain configuration and code and provide really minimal benefits.
So far I believe I'm the only person maintaining the relevant code and I'm not
willing to maintain more configuration complexity.
AFAIK we only provide the derby driver with geronimo, and in this case you have
to pick system-database not a jar.
> Geronimo Database pool wizard
> -----------------------------
>
> Key: GERONIMO-3905
> URL: https://issues.apache.org/jira/browse/GERONIMO-3905
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: databases
> Affects Versions: 2.1
> Environment: AG 2.1, Windows Xp
> Reporter: Ashish Jain
>
> While creating a datasource from Geronimo Database pool wizard we have the
> following steps:
> 1) Enter the name and type of database
> 2) Select the jars out of the list and other parameters
> 3) Deploy the pool.
> I would like to suggest an improvement in the 2nd step where the user has to
> manually select the jars for the pool. Will it be possible to have the jar
> included automatically once the user selects the database type. This will
> help to avoid the confusion on the selection of jars for each database pool
> type.
> In case the user wants to include a jar with different version(other than
> what is provided with AG), we can provide an edit option to edit the database
> pool configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
