Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1858204344.1219370084633.JavaMail.jira@brutus>
Date: Thu, 21 Aug 2008 18:54:44 -0700 (PDT)
From: "Lin Sun (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-3469) From console: database pool doesn't
 work well if the name contains a / like jdbc/EmployeeDataSource
In-Reply-To: <1575994.1189619372173.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lin Sun updated GERONIMO-3469:
------------------------------

    Fix Version/s: 2.2
                   2.1.3

> From console: database pool doesn't work well if the name contains a / like jdbc/EmployeeDataSource
> ---------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-3469
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3469
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: databases
>    Affects Versions: 2.0.1
>         Environment: winxp + Sun JDK 1.5
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>             Fix For: 2.1.3, 2.2
>
>         Attachments: G3469.patch
>
>
> 1) If I create a database pool called jdbc/EmployeeDataSource, I won't be able to delete it from the database pool portlet page.   
> 2) Also, while creating a new database pool, it seems not giving the option to have different input boxes for the artifact name and the database pool name.  They are in the same input box.  This was not true for previous releases IIRC.  For example, if I name the database pool jdbc/EmployeeDataSource, the full artifact name will be console.dbpool/jdbc%2FEmployeeDatasource/1.0/rar.  This is undesired and error prune, as I don't want that / in the artifact name.
> Seems fixing No. 2 may fix No. 1.   

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