You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2009/08/04 10:43:14 UTC

[jira] Resolved: (GERONIMO-4767) Use keywords strategy when filter the jdbc driver in database pools

     [ https://issues.apache.org/jira/browse/GERONIMO-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan resolved GERONIMO-4767.
----------------------------

    Resolution: Fixed

Commit the changes to trunk At revision: 800700. Thanks !

> Use keywords strategy when filter the jdbc driver in database pools
> -------------------------------------------------------------------
>
>                 Key: GERONIMO-4767
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4767
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 2.1.5, 2.2
>            Reporter: Rex Wang
>            Assignee: Rex Wang
>             Fix For: 2.2
>
>         Attachments: GERONIMO-4767-trunk.patch
>
>
> Current strategy is too strict when do filter on the jdbc drivers.
> We set the my sql dependecy filter "mysql/mysql-connector-java//jar", but if user manually copy the driver to <geronimo_home>/repository/org/mysql/...
> the database pool portlet won't find any jars ever. That because the filter mandatoryly requires user to install the jar to <geronimo_home>/repository/mysql/...
> We should improve this behavior more loosely, such as using the keywords.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.